| Hi, I have tried to use BSP 2.0.0 sd image and my own compilation of 2.6.18 kernel. U Boot freaks out after initialization at the first look at my image and the BSP 2.0.0 image. U boot states: Unknown Architecture Linux Kernel Image (gzipped compressed) Data Size: 879298 Bytes = 858.7 kB Load Address: 10000000 Entry Point: 90000000 Verifying Checksum .. OK Unsupported Architecture 0x11 How can I change the architecture value in my kernel and in BSP 2.0.0 and to what values? I am going over my Das U Boot sources and headers. Roman |
 |
 Joined: Sep 14, 2003 Posts: 624 Location: ACT, Australia |
| This is a mismatch between the uboot mkimage and the uboot bootloader on your dev board. You have to change one or the other. You could (_not_ recommended) downgrade your pc-side uboot by building the one off BSP1.0 or earlier. Much better, follow the instructions in http://www.avrfreaks.net/wiki/index.php ... ing_U-boot and get yourself a new, correct version of uboot on your dev board. Make the uboot sources from BSP2.0.0 and load the u-boot.bin to your flash, you‘ll be sorted. This all happened because the Blackfin dev fellas from Analog Devices jumped in ahead of Atmel and reserved the architecture number that the AVR32 originally used before Atmel could reserve it themselves. It won‘t happen again, 0x11 is now officially reserved to be AVR32. -S. |
| |
| Joined: Feb 28, 2007 Posts: 20 Location: Eugene, OR |
| squidgit wrote: Much better, follow the instructions in http://www.avrfreaks.net/wiki/index.php ... ing_U-boot and get yourself a new, correct version of uboot on your dev board. Make the uboot sources from BSP2.0.0 and load the u-boot.bin to your flash, you‘ll be sorted. -S. I followed the instructions and upgraded my Das U Boot. The uboot loads fine and initializes sdram and flash just fine. Now I have U-Boot 1.1.4-avr1 loading and supporting 0x11. However, the kernel either from BSP 2.0.0 or my own compiled 2.6.20 hang up during boot without any error or Aiee messages. What I get is this: Code: 879362 bytes read ## Booting image at 90400000 ... Image Name: Linux-2.6.18-at1 Image Type: AVR32 Linux Kernel Image (gzip compressed) Data Size: 879298 Bytes = 858.7 kB Load Address: 10000000 Entry Point: 90000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK Starting kernel at 90000000 (params at 107c0040)... and in case of the BSP 2.0.0 the lcd shows avr32 and ...booting messages. My kernel excludes lcd support and the screen is blank. |
| squidgit |
| |
| Joined: Sep 14, 2003 Posts: 624 Location: ACT, Australia |
| The boot is probably actually continuing, just directing its output to a non-existent terminal. At the uboot prompt type printenv and look for the bootargs line. It should contain console=ttyS0 *not* console=ttyUS0. If it contains the wrong one, type askenv bootargs and type in the old bootargs but with this one parameter changed. -S. |
| romank@randrlabs.com |
| |
| Joined: Feb 28, 2007 Posts: 20 Location: Eugene, OR |
| squidgit wrote: The boot is probably actually continuing, just directing its output to a non-existent terminal. You were dead on. Once I did setenv bootargs with the proper string, the magic happened. I am editing u-boot-1.1.4/include/configs/atstk1002.h specifically Code: #define CONFIG_BOOTARGS "console=ttyUS0 root=/dev/mmcblk0p1 fbmem=600k" to #define CONFIG_BOOTARGS "console=ttyS0 root=/dev/mmcblk0p1 fbmem=600k" I am also in the process of building the crosscompiler toolchain. I am in the middle of fixing the links of uClibs. I think that I have it down, but I won‘t know until further test compiles. Thanks for the pointer, Roman |
| squidgit |
| |
| Joined: Sep 14, 2003 Posts: 624 Location: ACT, Australia |
| no probs, donno exactly why the u-boot in BSP2.0.0 ships with the incorrect bootargs, probably just an oversight. Hopefully fixed by BSP(2.0.0++) -S. |
| hce |
| |
| Joined: Jan 07, 2003 Posts: 480 Location: Trondheim, Norway |
| U-boot in Linux BSP 2.0 should have correct bootargs. But if you upgraded u-boot from an earlier BSP release you need to clear out the environment area, or do a full chip erase with avr32program. |
| squidgit |
| |
| Joined: Sep 14, 2003 Posts: 624 Location: ACT, Australia |
| Ah yup, I only saw the Code: +#define CONFIG_BOOTARGS in atstk1002-add-daughterboard-support.patch, not the subsequent + "console=ttyUS0 root=/dev/mmcblk0p1 fbmem=600k" Code: - "console=ttyUS0 root=/dev/mmcblk0p1 fbmem=600k" [...] + "console=ttyS0 root=/dev/mmcblk0p1 fbmem=600k@" stringify(CFG_LCD_BASE) +#else +#define CONFIG_BOOTARGS + "console=ttyS0 root=/dev/mmcblk0p1 fbmem=600k" +#endif in atstk1000-add-lcd-and-spi-to-config.patch. Mia culpa -S. |
聯(lián)系客服
