On 07.04.2013, at 19:54, Alexander Graf wrote:
On 07.04.2013, at 18:16, G. Heim wrote:
Hi Alex,
Thanks again. I think I understand what you write. I found an armada-370-mirabox.dts in .../arch/arm/boot/dts of the linux-3.9 tree and it was already compiled to an armada-370-mirabox.dtb. There were also others (armada-370-db, armada-370-rd) but I did not try those. I copied armada-370-mirabox.dtb to the same partition on my sdcard where uImage is, and then I booted. Unfortuately it did not do anything more than before. This is what I tried:
Marvell>> set bootcmd 'usb start; fatload usb 1 0x6400000 uImage; bootm 0x6400000 - armada-370-mirabox.dtb'
This should error out I would have assumed. Hrm.
Marvell>> boot
This was what happened:
reading uImage
3460464 bytes read ## Booting kernel from Legacy Image at 06400000 ... Image Name: Linux-3.9.0-rc5 Created: 2013-04-07 10:10:29 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3460400 Bytes = 3.3 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK
Starting kernel ...
... and nothing more.
Then I tried:
Marvell>> usb start (Re)start USB... USB: Active port: invalid port number 2, switching to port 0 Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 4 USB Device(s) found Waiting for storage device(s) to settle before scanning... scanning bus for storage devices... Device NOT ready Request Sense returned 02 3A 00 2 Storage Device(s) found Marvell>> fatload usb 1 0x6400000 uImage reading uImage
3460464 bytes read Marvell>> fatload usb 1 0xc000000 armada-370-mirabox.dtb
I'd assume that 0xc0000000 is out of RAM, no?
reading armada-370-mirabox.dtb
5727 bytes read Marvell>> bootm 0x6400000 - 0xc000000 ## Booting kernel from Legacy Image at 06400000 ... Image Name: Linux-3.9.0-rc5 Created: 2013-04-07 10:10:29 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3460400 Bytes = 3.3 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK
Starting kernel ...
... and nothing more.
Then I tried (because maybe I had the addresses in the wrong order):
Marvell>> fatload usb 1 0x6400000 uImage reading uImage
3460464 bytes read Marvell>> fatload usb 1 0x5000000 armada-370-mirabox.dtb
That looks more sensible. At which physical offset does RAM start on this machine?
mada-370-mirabox.dtb reading armada-370-mirabox.dtb
5727 bytes read Marvell>> bootm 0x6400000 - 0x5000000 ## Booting kernel from Legacy Image at 06400000 ... Image Name: Linux-3.9.0-rc5 Created: 2013-04-07 10:10:29 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3460400 Bytes = 3.3 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK
Starting kernel ...
... and nothing more.
Obviously I am missing something. Maybe my mirabox has an old Uboot? It says:
BootROM 1.08 Booting from NAND flash DDR3 Training Sequence - Ver 2.1.6 DDR3 Training Sequence - Number of DIMMs detected: 1 DDR3 Training Sequence - Ended Successfully BootROM: Image checksum verification PASSED
__ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** LOADER **
U-Boot 2009.08 (Sep 16 2012 - 22:50:06)Marvell version: 1.1.2 NQ
This does sound quite old, yeah. Can you update your u-boot version to something more recent? There's a good chance Linux never gets to see the dtb...
http://www.spinics.net/lists/arm-kernel/msg234398.html Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org