 |
| Author |
Message |
|
|
 Posted: Apr 22, 2008 - 01:16 PM |
|
Joined: Apr 18, 2008
Posts: 2
|
|
Hi,
I've built a filesystem for my STK1000 using buildroot. However when I tried to boot it from SD card I received the 'Unsupported Architecture 0x11' message.
After a bit of reading it seems that I have BSP v1.0 and I'll need to upgrade my u-boot version to a BSP2.0 compatible one, is that correct?
I do not have a JTAGmkII and read in http://www.avrfreaks.net/wiki/index.php ... ing_U-boot
that I needed to build the BSP2.0 flash upgrade utility.
I got myself a BSP 2.0 CD image.
However in the directory builds/stk1000 I noticed the file 'u-boot-upgrade-1.1.4-at1-from-bsp-1.0.uimg'.
Is this the image I want to use or should I go ahead and build the flash upgrade utility from 'software/flash-upgrade'?
In either case I end up with a 'uimg' file, how do i deploy this? Do I load it from the U-Boot prompt, or is this a SD card image?
Sorry for the very basic questions, I'm just worried that I'll brick my board.
Thanks |
|
|
| |
|
|
|
|
|
|
Posted: Apr 23, 2008 - 06:34 AM |
|
Joined: Sep 14, 2003
Posts: 4228
Location: Queanbeyan, Australia
|
|
ISTR the version actually shipped on BSP2.0 didn't work; you should build it yourself.
Once you've got the .uimg file then this just needs to be somewhere that uboot can find it; eg SD card, in flash, over a network etc. Probably the most failsafe method is just to copy it to your SD card's root directory.
Note it isn't an SD image, don't try and do any dd'ing, just a regular cut and paste will be fine.
The idea is that uboot boots this file thinking it's a Linux kernel so anywhere you'd normally put your kernels' uImage file, you can put this upgrader instead.
-S. |
_________________
Blag: http://www.niasdigital.com/blag
|
| |
|
|
|
|
|
|
Posted: Apr 23, 2008 - 05:29 PM |
|
Joined: Apr 18, 2008
Posts: 2
|
|
Thanks Squidgit,
I built u-boot-1.3.1.atmel.1 and built a flash-upgrade.uimg file which I put on my SD card (after renaming the file to uImage).
Unfortunately the 'Unsupported Architecture 0x11' message still appears.
I guess this makes sense because the u-boot image I built probably has the arch ID set to 0x11. A quick grep showed that in the u-boot source in include/image.h IH_CPU_AVR32 is set to 17 (decimal).
I read in a previous thread that you have generated uImages in the past with ID=0x10, did you do this by changing the image.h file or can you pass in an ID during building?
BTW, is there an easy way (using hexedit?) to check the architecture ID of the generated u-boot.bin?
Many thanks for your help. |
|
|
| |
|
|
|
|
|
|
|
FAQ
Search
Register
Log in to check your private messages
Log in
Maximize
RSS
