Re: [U-Boot] Debugging why my kernel won't start

Dear Rogan Dawes, In message <4c6c0b33.8090...@dawes.za.net> you wrote: > > Well, I thought that was the point of the "mkimage" header, with the > Load Address and Entry Point fields. Although, of course, you'll never These fields are only relevant for executable images, not for data like ramdisk

Re: [U-Boot] Debugging why my kernel won't start

On 2010/08/18 5:33 PM, Wolfgang Denk wrote: > Dear Rogan Dawes, > > Your kernel may not be able to pick up a ramdisk image in flash. > > Mainline ARM cannot do that, for example. > > [Patches to support that have been submitted, but rejected.] > >> Surely that should be Ok? Besides, U-boot is s

Re: [U-Boot] Debugging why my kernel won't start

Dear Rogan Dawes, In message <4c6bf138.20...@dawes.za.net> you wrote: > > > Try copying the raw ramdisk image (i. e. without the U-Boot header) to > > RAM, and try that one, i. e. something like > > > > => cp.b ff9a0040 0160 ...size... > > ... > > => bootm ff82 160 > > Un

Re: [U-Boot] Debugging why my kernel won't start

On 2010/08/18 12:54 PM, Wolfgang Denk wrote: > Dear Rogan Dawes, > > In message <4c6bac5a.6060...@dawes.za.net> you wrote: >> >> Thanks for the suggestion. It did make a slight difference in the boot >> logs. bootcmd uses the default (in flash) location for the ramdisk, > > Actually it's a pretty

Re: [U-Boot] Debugging why my kernel won't start

Dear Rogan Dawes, In message <4c6bac5a.6060...@dawes.za.net> you wrote: > > Thanks for the suggestion. It did make a slight difference in the boot > logs. bootcmd uses the default (in flash) location for the ramdisk, Actually it's a pretty significant difference, as for the first time you actuall

Re: [U-Boot] Debugging why my kernel won't start

On 2010/08/18 7:51 AM, Wolfgang Denk wrote: > Dear Rogan Dawes, > > In message <4c6b08f1.9000...@dawes.za.net> you wrote: >> >> The ramdisk is located at ff9a (in flash). Its image header >> relocates it to 0080: > > Try to copy the ramdisk to RAM, and pass the Linux kernl an address in >

Re: [U-Boot] Debugging why my kernel won't start

Dear Rogan Dawes, In message <4c6b08f1.9000...@dawes.za.net> you wrote: > > The ramdisk is located at ff9a (in flash). Its image header > relocates it to 0080: Try to copy the ramdisk to RAM, and pass the Linux kernl an address in RAM. Try it. Best regards, Wolfgang Denk -- DENX Soft

Re: [U-Boot] Debugging why my kernel won't start

On 2010/08/18 12:04 AM, Wolfgang Denk wrote: > Dear Rogan Dawes, > > In message <4c6b051a.5050...@dawes.za.net> you wrote: >> >> For some reason, the kernel didn't seem to think it had been given the >> ramdisk parameter. At least, I get the following error message: > > Where is the ramdisk locat

Re: [U-Boot] Debugging why my kernel won't start

Dear Rogan Dawes, In message <4c6b051a.5050...@dawes.za.net> you wrote: > > For some reason, the kernel didn't seem to think it had been given the > ramdisk parameter. At least, I get the following error message: Where is the ramdisk located? Make sure it is loaded into RAM (not flash!). Best r

Re: [U-Boot] Debugging why my kernel won't start

On 2010/08/17 11:20 PM, Wolfgang Denk wrote: > Dear Rogan Dawes, > > In message <4c6aec70.40...@dawes.za.net> you wrote: >> >> No, but mistaken in thinking that the machid was in decimal, when it is >> really in hex. >> >> Now to figure out why the CRC calculations are different, and I'll have >>

Re: [U-Boot] Debugging why my kernel won't start

Dear Rogan Dawes, In message <4c6aec70.40...@dawes.za.net> you wrote: > > No, but mistaken in thinking that the machid was in decimal, when it is > really in hex. > > Now to figure out why the CRC calculations are different, and I'll have > a fully functioning u-boot! For a test you could as ell

Re: [U-Boot] Debugging why my kernel won't start

Dear Rogan Dawes, In message <4c6ae955.1060...@dawes.za.net> you wrote: > > I'm not passing the second parameter at this stage, because the ramdisk > is failing the CRC32 check for some reason. It may be that the CRC32 > calculation has changed between 1.1.1 which was the base for the vendor > u-b

Re: [U-Boot] Debugging why my kernel won't start

On 2010/08/17 9:56 PM, Rogan Dawes wrote: > > Am I mistaken in expecting the machid environment variable trick to work? > > Thanks > > Rogan No, but mistaken in thinking that the machid was in decimal, when it is really in hex. Now to figure out why the CRC calculations are different, and I'll

Re: [U-Boot] Debugging why my kernel won't start

On 2010/08/17 5:38 PM, Albert ARIBAUD wrote: > Ok, so u-boot is now out of the way of the linux image load area. > >> Now to figure out why I'm not getting any further than this. (And why >> the vendor ramdisk is giving me CRC errors). > > What is the actual command you use for booting your kern

Re: [U-Boot] Debugging why my kernel won't start

Le 17/08/2010 13:42, Rogan Dawes a écrit : > On 2010/08/17 1:19 PM, Rogan Dawes wrote: >> I'll try with a higher value, and see what happens. >> > > So, I tried with TEXT_BASE=f1, and I got a bit further: > > DNS323B1> bootm FF82 > ## Booting kernel from Legacy Image at ff82 ... >

Re: [U-Boot] Debugging why my kernel won't start

On 2010/08/17 1:19 PM, Rogan Dawes wrote: > I'll try with a higher value, and see what happens. > So, I tried with TEXT_BASE=f1, and I got a bit further: DNS323B1> bootm FF82 ## Booting kernel from Legacy Image at ff82 ... Image Name: Linux-2.6.12.6-arm1 Image Type: ARM Lin

Re: [U-Boot] Debugging why my kernel won't start

On 2010/08/17 12:41 PM, Albert ARIBAUD wrote: >> I had a debug statement in the loop, printing out the above at each >> iteration. Since it never completed the loop, copying/moving the entire >> kernel (609564 bytes remaining), I think it is safe to assume that it >> never got to the point of tryin

Re: [U-Boot] Debugging why my kernel won't start

Le 17/08/2010 12:21, Rogan Dawes a écrit : > On 2010/08/17 12:10 PM, Albert ARIBAUD wrote: >> (quick note to Wolfgang: yes, there is RAM at 0x8000 on these >> machines. All orion5x based machines have RAM start at 0, and u-boot >> makes sure SDRAM is set up this way) >> >> Rogan, >> >> You cann

Re: [U-Boot] Debugging why my kernel won't start

On 2010/08/17 12:10 PM, Albert ARIBAUD wrote: > (quick note to Wolfgang: yes, there is RAM at 0x8000 on these > machines. All orion5x based machines have RAM start at 0, and u-boot > makes sure SDRAM is set up this way) > > Rogan, > > You cannot tell from your log output that memmove never

Re: [U-Boot] Debugging why my kernel won't start

Le 16/08/2010 22:15, Rogan Dawes a écrit : > On 2010/08/16 9:24 AM, Rogan Dawes wrote: >> Hi folks, >> >> I'm trying to get mainline u-boot working on my DNS323 (Orion5x based). >> Until I am confident in the config, I'm using a chainloaded approach, >> wrapping my featureful u-boot in an image fil

Re: [U-Boot] Debugging why my kernel won't start

On 2010/08/17 12:03 AM, Wolfgang Denk wrote: > Dear Rogan Dawes, > > In message <4c69a8da.8020...@dawes.za.net> you wrote: >> >>> Are you absolutely sure that you have RAM in your system at 0x8000? >>> I doubt that your Load Address/Entry Point settings are correct. >> >> This is the default kerne

Re: [U-Boot] Debugging why my kernel won't start

Dear Rogan Dawes, In message <4c69a8da.8020...@dawes.za.net> you wrote: > > > Are you absolutely sure that you have RAM in your system at 0x8000? > > I doubt that your Load Address/Entry Point settings are correct. > > This is the default kernel that was shipped with the device, and so > those ar

Re: [U-Boot] Debugging why my kernel won't start

On 2010/08/16 10:29 PM, Wolfgang Denk wrote: > Dear Rogan Dawes, > > In message<4c699c6e.2010...@dawes.za.net> you wrote: >> >>> DNS323B1> bootm FF82 >>> ## Booting kernel from Legacy Image at ff82 ... >>> Image Name: Linux-2.6.12.6-arm1 >>> Image Type: ARM Linux Kernel

Re: [U-Boot] Debugging why my kernel won't start

Dear Rogan Dawes, In message <4c699c6e.2010...@dawes.za.net> you wrote: > > > DNS323B1> bootm FF82 > > ## Booting kernel from Legacy Image at ff82 ... > > Image Name: Linux-2.6.12.6-arm1 > > Image Type: ARM Linux Kernel Image (uncompressed) > > Data Size:1490204 Byt

Re: [U-Boot] Debugging why my kernel won't start

On 2010/08/16 9:24 AM, Rogan Dawes wrote: > Hi folks, > > I'm trying to get mainline u-boot working on my DNS323 (Orion5x based). > Until I am confident in the config, I'm using a chainloaded approach, > wrapping my featureful u-boot in an image file: > > $ mkimage -A arm -O u-boot -T kernel -C non

Re: [U-Boot] Debugging why my kernel won't start

On 2010/08/16 10:34 AM, Gérald Kerma wrote: > Dear Rogan, > > I've you set the uboot env machid to the correct value ? > setenv machid > just replace HexValue with the correct MACH_TYPE. > > You must then see something like : > Using machid 0xa76 from environment > after kernel loaded by uboot. > >

Re: [U-Boot] Debugging why my kernel won't start

Dear Rogan, I've you set the uboot env machid to the correct value ? setenv machid just replace HexValue with the correct MACH_TYPE. You must then see something like : Using machid 0xa76 from environment after kernel loaded by uboot. Best regards, Le 16/08/2010 09:24, Rogan Dawes a écrit : > H

[U-Boot] Debugging why my kernel won't start

Hi folks, I'm trying to get mainline u-boot working on my DNS323 (Orion5x based). Until I am confident in the config, I'm using a chainloaded approach, wrapping my featureful u-boot in an image file: $ mkimage -A arm -O u-boot -T kernel -C none -a 0x300 -e 0x300 -n "UBoot dns323" -d u-