Hi All,
I am using buildroot to create a cpio image. Following is the output.
Starting kernel ...
Uncompressing
Linux
Linux version 2.6.24.4-default ([EMAIL PROTECTED]) (gcc version 4.2.1) #57 Tue
Apr 1
Hi Tiju,
> and then it hangs. We are writing the kernel image directly to the ram to
> 3300 via JTAG.
Writing kernel to RAM using JTAG is only a workaround ! I think it would be
better to fix whatever problems you currently have like (if at all you
have any) with memory
timing etc - ensure th
Hi Herald,
The environment variables are as follows:
DPB2440 # printenv
bootargs=root=ramfs devfs=mount console=ttyS0,115200
bootcmd=bootm
bootdelay=3
baudrate=115200
bootfile="uImage.bin"
stdin=serial
stdout=serial
stderr=serial
Thankyou,
Best Regards,
Tiju
Bollywood, fun, friendship,
Hi Herald,
>> We changed the memory clock to a lower frequency(90MHz to 67MHz) and
>> the the "Bad Data CRC" error has gone. Thanks alot.
>ok, this most likely means that you have some problems with your
>hardware design, probably exceeding the maximum permitted capacitive bus
>load.
>well, how do
Hi Tiju,
On Mon, Apr 07, 2008 at 09:09:36PM +0530, Tiju wrote:
> >Please see my other e-mail response about this. I still believe there
> >might be some wrong memory / bus / core clock timing and or voltage
> >issues.
>
> We changed the memory clock to a lower frequency(90MHz to 67MHz) and
>
Hi Harald,
>Please see my other e-mail response about this. I still believe there
>might be some wrong memory / bus / core clock timing and or voltage
>issues.
We changed the memory clock to a lower frequency(90MHz to 67MHz) and the the
"Bad Data CRC" error has gone. Thanks alot.
Our settings
Hi Jerry,
>This is indicating you have major link / memory map / coding issue(s).
>vmlinux should be around 1MB, not 25MB! linux.bin should be around the
>same size as vmlinux. Having linux.bin grow to be 3GB indicates it has
>major holes in it that objdump is filling with "fill" values.
Loa
Tiju wrote:
> Hi Harald,
>
> The serial issues were solved. As u said, the problem was with the
> RTS/CTS. I disabled all the hardware control signals and some
> modifications with the relocation section in the start..S and it started
> working.
>
> Now the issue is with the kernel CRC32 check
On Mon, Apr 07, 2008 at 02:31:10PM +0530, Tiju wrote:
> Hi Harald,
>
> The serial issues were solved. As u said, the problem was with the
> RTS/CTS. I disabled all the hardware control signals and some
> modifications with the relocation section in the start.S and it
> started working.
great.
>
Hi Harald,
The serial issues were solved. As u said, the problem was with the RTS/CTS. I
disabled all the hardware control signals and some modifications with the
relocation section in the start.S and it started working.
Now the issue is with the kernel CRC32 check. I compiled a kernel with the
Hi Leon,
> We have seen both illegal instructions and crc errors for kernel > 4
> MB on PowerPC.
Even when the kernel size is 1.09 MB the same BAD CRC error occurs.
Is it the error with the kernel or the uboot itself. If so what could be the
problem?
Output is as follows.
U-Boot 1.3.2 (Apr 7
Hello,
On Sun, Apr 6, 2008 at 11:03 AM, Tiju <[EMAIL PROTECTED]> wrote:
We have seen both illegal instructions and crc errors for kernel > 4
MB on PowerPC.
I have to reproduce this, but we suspect the 4 MB boundary. This was
for an old u-boot.
Regards,
--
Leon
Hi all,
Afteruboot comes up, I get stuck with the booting of linux kernel. The RAMrange
is from 0x3000-0x3800. Following are the steps I do toget the
uImage.bin.
$ arm-linux-objcopy -O binary -R .note -R .comment -S vmlinux linux.bin
$ gzip -9 linux.bin
$../u-boot-1.3.2/tools/mkimage -A
Hi all,
After uboot comes up, I get stuck with the booting of linux kernel. The RAM
range is from 0x3000-0x3800. Following are the steps I do to get the
uImage.bin.
$ arm-linux-objcopy -O binary -R .note -R ..comment -S vmlinux linux.bin
$ gzip -9 linux.bin
$ ../u-boot-1.3.2/tools/mkima
14 matches
Mail list logo
