October 2004 - U-Boot

[U-Boot-Users] Testing of Ethernet.
by Prathima_Kolar 25 Oct '04

25 Oct '04

Hello All, Can anyone please tell me how i can test Read and Write to registers on LXT971A if it is not memory mapped. Thanks & Regards, Prathima Kolar. ************************************************************************** This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated. **************************************************************************

3 2

[U-Boot-Users] U-boot for Malta
by calvin 24 Oct '04

24 Oct '04

Hi, I am trying to port u-boot for MALTA(mips) board. The code downloads properly at the appropriate Flash address (0xBFC0000) but then loops back at some point due to memory problems. here is the dump file - > ffffffffbfc00300: 10000090 b ffffffffbfc00544 <romExcHandle> > ffffffffbfc00304: 241a0300 li $k0,768 ffffffffbfc00544 <romExcHandle>: ffffffffbfc00544: 1000ffff b ffffffffbfc00544 <romExcHandle> Other boot loaders works ok. that means hardware is working perfectly fine. Any pointers would be helpful. Thanks and regards, Pooja

2 1

[U-Boot-Users] Switching of LCD controller before reboot?
by Steven Scholz 22 Oct '04

22 Oct '04

Hi there, my i.MX based board does not reboot but hangs when doing "reset" (on u-boot) or "reboot" (on linux) when the internal LCD contoller is enabled. Thus I have to disable the LCD contoller before doing that. Something else: The AT91RM9200DK needs to "shutdown the console to avoid strange chars during reset". So my question is: Where would be the appropriate place for stuff like that? Should we clobber cpu/arm920t/cpu.c with all the processor or board specific reset related stuff? Or would it be better to have something like cpu_init, /* basic cpu dependent setup */ board_init, /* basic board dependent setup */ ... cpu_reset, /* basic cpu dependent reset */ board_reset, /* basic board dependent reset */ or prepare_reset based on defines like CONFIG_BOARD_PRE_RESET or something? Thanks. -- Steven Scholz

3 8

[U-Boot-Users] PATCH: Support for Motorola HiddenDragon board
by Santoso, Yusdi 22 Oct '04

22 Oct '04

Patch to add support fo Motorola HiddenDragon board. Thanks, Yusdi

1 0

[U-Boot-Users] [patch][CVS] Updating for RPXlite_DW
by Sam Song 22 Oct '04

22 Oct '04

Hi list, I found sth was broken on my previous patch which I did on Oct. 11 because there were some conflicts in it. I don't know why cvs diff did it like that. So I redid the patch against CVS and test it on RPXlite DW board fully. Pls apply this patch. Wolfgang, if I confuse you again with my patch, pls forgive me again. To make RPXlite DW board close to system deployment, PREBOOT and AUTOBOOT function was added. CHANGELOG: * Patch by Sam Song, 22 October 2004: - Add PREBOOT/AUTOBOOT support for RPXlite_DW board ===== Best regards, Sam _________________________________________________________ Do You Yahoo!? 150万曲MP3疯狂搜，带您闯入音乐殿堂 http://music.yisou.com/ 美女明星应有尽有，搜遍美图、艳图和酷图 http://image.yisou.com 1G就是1000兆，雅虎电邮自助扩容！ http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_… Index: board/RPXlite_dw/README =================================================================== RCS file: /cvsroot/u-boot/u-boot/board/RPXlite_dw/README,v retrieving revision 1.1 diff -p -u -r1.1 README --- board/RPXlite_dw/README 9 Jun 2004 21:04:49 -0000 1.1 +++ board/RPXlite_dw/README 22 Oct 2004 01:17:22 -0000 @@ -2,11 +2,11 @@ After following the step of Yoo. Jonghoon and Wolfgang Denk, I ported u-boot on RPXlite DW version board: RPXlite_DW or LITE_DW. -There are three differences between the Yoo-ported RPXlite and the RPXlite_DW. +There are at least three differences between the Yoo-ported RPXlite and the RPXlite_DW. -Board(in U-BOOT) version(in EmbeddedPlanet) CPU SDRAM FLASH +Board(in U-Boot) version(in EmbeddedPlanet) CPU SDRAM FLASH RPXlite RPXlite CW 850 16MB 4MB -RPXlite_DW RPXlite DW 823e 64MB 16MB +RPXlite_DW RPXlite DW(EP 823 H1 DW) 823e 64MB 16MB This fireware is specially coded for EmbeddedPlanet Co. Software Development Platform(RPXlite DW),which has a NEC NL6448BC20-08 LCD panel. @@ -17,6 +17,7 @@ It has the following three features: The default setting is 48MHz.To get a 64MHz u-boot,just add '64' in make command,like +make distclean make RPXlite_DW_64_config make all @@ -28,19 +29,21 @@ didn't use EEPROM for ENV is that Planet home.Because of the possibility of using two firewares on this board,I didn't 'disturb' EEPROM.To get NVRAM support,you may use the following build command: +make distclean make RPXlite_DW_NVRAM_config make all 3. LCD panel support -To support the Platform better,I added LCD panel(NL6448BC20-08) function.But bewear of -the fact that once you build this support and program it to FLASH,you should make sure -you put workable kernel and ramdisk at the right place in FLASH or through NFS. -Otherwise, you must erase this fireware manually via BDI2000 or ICE tools.So this -function is used for deployment and demo only.Pls look before you leap. +To support the Platform better,I added LCD panel(NL6448BC20-08) function. +For the convenience of debug, CONFIG_PERBOOT was supported. So you just +perss ENTER if you want to get a serial console in boot downcounting. +Then you can switch to LCD and serial console freely just typing +'run lcd' or 'run ser'. They are only vaild when CONFIG_LCD was enabled. To get a LCD support u-boot,you can do the following: +make distclean make RPXlite_DW_LCD_config make all @@ -68,7 +71,7 @@ make RPXlite_DW_64_LCD_config The boot process by "make RPXlite_DW_config" could be: -U-Boot 1.1.1 (Jun 8 2004 - 11:16:30) +U-Boot 1.1.2 (Oct 22 2004 - 08:15:50) CPU: PPC823EZTnnB2 at 48 MHz: 16 kB I-Cache 8 kB D-Cache Board: RPXlite_DW @@ -80,10 +83,72 @@ In: serial Out: serial Err: serial Net: SCC ETHERNET +Hit any key to stop autoboot: 6 + +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +A word on the U-Boot enviroment variable setting and usage : + +In the beginning, you could just need very simple defult environment variable setting, +like[include/configs/RPXlite.h] : + +#define CONFIG_BOOTCOMMAND \ + "bootp; " \ + "setenv bootargs root=/dev/nfs rw nfsroot=$(serverip):$(rootpath) " \ + "ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname)::off; " \ + "bootm" + +This is enough for kernel NFS test. But as debug process goes on, you would expect +to save some time on environment variable setting and u-boot/kernel updating. +So the default environment variable setting would become more complicated. Just like +the one I did in include/configs/RPXlite_DW.h. + +Two u-boot commands, ku and uu, should be careful to use. They were designed to update +kernel and u-boot image file respectively. You must tftp your image to default address +'100000' and then use them correctly. Yeah, you can create your own command to do this +job. :-) The example u-boot image updating process could be : + +u-boot>t 100000 RPXlite_DW_LCD.bin +Using SCC ETHERNET device +TFTP from server 172.16.115.6; our IP address is 172.16.115.7 +Filename 'RPXlite_DW_LCD.bin'. +Load address: 0x100000 +Loading: ############################# +done +Bytes transferred = 144700 (2353c hex) +u-boot>run uu +Un-Protect Flash Sectors 0-4 in Bank # 1 +Erase Flash Sectors 0-4 in Bank # 1 +.... done +Copy to Flash... done +ff000000: 27051956 552d426f 6f742031 2e312e32 '..VU-Boot 1.1.2 +ff000010: 20284175 67203239 20323030 34202d20 (Aug 29 2004 - +ff000020: 31353a32 303a3238 29000000 00000000 15:20:28)....... +ff000030: 00000000 00000000 00000000 00000000 ................ +ff000040: 00000000 00000000 00000000 00000000 ................ +ff000050: 00000000 00000000 00000000 00000000 ................ +ff000060: 00000000 00000000 00000000 00000000 ................ +ff000070: 00000000 00000000 00000000 00000000 ................ +ff000080: 00000000 00000000 00000000 00000000 ................ +ff000090: 00000000 00000000 00000000 00000000 ................ +ff0000a0: 00000000 00000000 00000000 00000000 ................ +ff0000b0: 00000000 00000000 00000000 00000000 ................ +ff0000c0: 00000000 00000000 00000000 00000000 ................ +ff0000d0: 00000000 00000000 00000000 00000000 ................ +ff0000e0: 00000000 00000000 00000000 00000000 ................ +ff0000f0: 00000000 00000000 00000000 00000000 ................ +u-boot updating finished u-boot> +Also for environment updating, 'run eu' could let you erase OLD default environment variable +and then use the working u-boot environment setting. + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Finally, if you want to keep the serial port to possible debug on spot for deployment, you +just need to enable 'DEPLOYMENT' in RPXlite_DW.h as 'DEBUG' does. Only the special string +defined by CONFIG_AUTOBOOT_STOP_STR like 'st' can stop the autoboot. + I'd like to extend my heartfelt gratitute to kind people for helping me work it out. I would particually thank Wolfgang Denk for his nice help. @@ -93,4 +158,4 @@ Sam Song, samsongshu(a)yahoo.com.cn Institute of Electrical Machinery and Controls Shanghai University -June 8,2004 +October 22, 2004 Index: include/configs/RPXlite_DW.h =================================================================== RCS file: /cvsroot/u-boot/u-boot/include/configs/RPXlite_DW.h,v retrieving revision 1.3 diff -p -u -r1.3 RPXlite_DW.h --- include/configs/RPXlite_DW.h 9 Oct 2004 22:45:00 -0000 1.3 +++ include/configs/RPXlite_DW.h 22 Oct 2004 01:17:35 -0000 @@ -45,6 +45,7 @@ */ /* #define DEBUG 1 */ +/* #define DEPLOYMENT 1 */ #undef CONFIG_MPC860 #define CONFIG_MPC823 1 /* This is a MPC823e CPU. */ @@ -59,19 +60,32 @@ #undef CONFIG_8xx_CONS_NONE #define CONFIG_BAUDRATE 9600 /* console default baudrate = 9600bps */ -#ifdef CONFIG_LCD -#define CONFIG_BOOTDELAY 12 /* autoboot after 12 seconds */ +#ifdef DEBUG +#define CONFIG_BOOTDELAY -1 /* autoboot disabled */ #else -#define CONFIG_BOOTDELAY -1 /* autoboot disabled */ +#define CONFIG_BOOTDELAY 6 /* autoboot after 6 seconds */ +#define CONFIG_BOOTDELAY 6 /* autoboot after 6 seconds */ + +#ifdef DEPLOYMENT +#define CONFIG_BOOT_RETRY_TIME -1 +#define CONFIG_AUTOBOOT_KEYED +#define CONFIG_AUTOBOOT_PROMPT "autoboot in %d seconds (stop with 'st')...\n" +#define CONFIG_AUTOBOOT_STOP_STR "st" +#define CONFIG_ZERO_BOOTDELAY_CHECK +#define CONFIG_RESET_TO_RETRY 1 +#define CONFIG_BOOT_RETRY_MIN 1 +#endif #endif +/* pre-boot commands */ +#define CONFIG_PREBOOT "setenv stdout serial;setenv stdin serial" + #undef CONFIG_BOOTARGS #define CONFIG_EXTRA_ENV_SETTINGS \ "netdev=eth0\0" \ - "nfsargs=setenv bootargs console=ttyS0,9600 root=/dev/nfs rw " \ - "nfsroot=$(serverip):$(rootpath)\0" \ - "ramargs=setenv bootargs console=tty0 console=ttyS0,9600 " \ - "root=/dev/ram rw\0" \ + "nfsargs=setenv bootargs console=tty0 console=ttyS0,9600 " \ + "root=/dev/nfs rw nfsroot=$(serverip):$(rootpath)\0" \ + "ramargs=setenv bootargs console=tty0 root=/dev/ram rw\0" \ "addip=setenv bootargs $(bootargs) " \ "ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask)" \ ":$(hostname):$(netdev):off panic=1\0" \ @@ -82,8 +96,18 @@ "net_nfs=tftp 200000 $(bootfile);run nfsargs addip;bootm\0" \ "gatewayip=172.16.115.254\0" \ "netmask=255.255.255.0\0" \ - "kernel_addr=ff080000\0" \ + "kernel_addr=ff040000\0" \ "ramdisk_addr=ff200000\0" \ + "ku=era $(kernel_addr) ff1fffff;cp.b 100000 $(kernel_addr) " \ + "$(filesize);md $(kernel_addr);" \ + "echo kernel updating finished\0" \ + "uu=protect off 1:0-5;era 1:0-5;cp.b 100000 ff000000 " \ + "$(filesize);md ff000000;" \ + "echo u-boot updating finished\0" \ + "eu=protect off 1:6;era 1:6;reset\0" \ + "lcd=setenv stdout lcd;setenv stdin lcd\0" \ + "ser=setenv stdout serial;setenv stdin serial\0" \ + "verify=no" \ "" #define CONFIG_BOOTCOMMAND "run flash_self"

1 0

[U-Boot-Users] question about net/net.c
by Robin Getz 22 Oct '04

22 Oct '04

I had a question about the latest version of net/net.c scenario is as follows. 1. u-boot initiates a tftp transfer 2. u-boot sets a flag "NetArpWaitPacketMAC = 1" 3. u-boot sends ARP Request on network to find the MAC address of tftp server 4. server is a little slow, and u-boot has not yet received the ARP so, u-boot sends ARP Request on network to find the MAC address of tftp server 5. tftp server responds back to first request with it's MAC address, and u-boot sees this, and accepts it. 6. u-boot sets the flag "NetArpWaitPacketMAC = 0" as it got the ARP reply 7. tftp server responds back to second request with it's MAC address, and u-boot sees this, and accepts it. At this point as u-boot is not waiting (NetArpWaitPacketMAC is 0) for ARP reply breaks out of the switch that handles ARP reply. But this break is not to return from the complete handler and thus falls into RARP handler code. 8. u-boot prints out "invalid RARP header". This can be observed in net\net.c "NetReceive" function. =============================================== void NetReceive(volatile uchar * inpkt, int len) { [snip/snip] switch (x) { case PROT_ARP: switch (ntohs(arp->ar_op)) { case ARPOP_REQUEST: /* reply with our IP address */ return; case ARPOP_REPLY: /* arp reply */ /* are we waiting for a reply */ if (!NetArpWaitPacketIP || !NetArpWaitPacketMAC) break; return; default: return; } case PROT_RARP: break; ================================================== am I missing something or shouldn't there be a break; above the 'case PROT_RARP:' to handle this? Thanks -Robin

3 2

[U-Boot-Users] Sending patch
by Santoso, Yusdi 21 Oct '04

21 Oct '04

Hi all, I'm planning to send a patch to add Motorola HiddenDragon board support, but I do not have access to CVS in my work place. Can I send a patch agains the latest stable (1.1.1) version? Or the latest snapshot in the FTP (2004-08-18) ? Thanks, Yusdi

2 1

[U-Boot-Users] Debugging u-boot using an EPI Majic JTAG
by Christian Kapeller 21 Oct '04

21 Oct '04

Hi! I'm trying to debug u-boot 1.1.1 using a EPI Majic JTAG probe for arm processors on an PXA255. I load the compiled elf-binary down using the JTAG, and try to run it. I get immediately a "Hardware instruction breakpoint" message. Other binaries run without problems using the JTAG. Also when i flash u-boot it works. Has anyone of you used a EPI Majic to debug u-boot successfully? Here are the logs: --snip-- EPI Symbolic Assembly Level Debug Monitor, version V6.9.7 - Linux(x86) Copyright (c) 1987-2000 by Embedded Performance Inc. - All Rights Reserved. Processing register file: /home/chrkap/tinylinux/edta21/bin/arm/spaces.rd Processing register file: /home/chrkap/tinylinux/edta21/bin/arm/pxa250.rd Processing register file: /home/chrkap/tinylinux/edta21/bin/arm/80200.rd Processing register file: /home/chrkap/tinylinux/edta21/bin/arm/majic.rd Reading command history from: '/home/chrkap/tinylinux/edta21/bin/startedb.hst' Establishing communications with remote target via 192.168.0.2... Connection verified Target System: EPI Majic Probe, Version: 3.2.6, S/N 0310H016 Hardware Rev: a0:3:3:10 Target CPU: PXA21x/PXA25x/PXA26x Ethernet: at address 00:80:CF:00:17:FA IP address: 192.168.0.2, Subnet mask: 255.255.255.0 Trace Buffer: 0 frames Profiler: Not Installed Connected via: Ethernet UDP/IP Device name: 192.168.0.2 Target Endian: little Start Address: 00000000: EPI-OS (HIF): on Reset Mode: capture Reading commands from /home/chrkap/tinylinux/edta21/bin/startice.cmd MON> +q // Enter quiet mode Reading startice.cmd file Notification from the target: Target power detected on VREF Auto JTAG detection process detected 1 TAP JTAG connection established Reading dbpxa250.cmd Executing One Time Setup Commands Executing Target Init Commands 48000008: 26F226F2 4800000c: 3FF4A441 48000010: 00007FF0 48000004: 00010018 a0000000: 00000000 00000000 00000000 00000000 a0000010: 00000000 00000000 00000000 00000000 a0000020: 00000000 00000000 00000000 00000000 a0000030: 00000000 00000000 00000000 00000000 a0000040: 00000000 00000000 00000000 00000000 a0000050: 00000000 00000000 00000000 00000000 a0000060: 00000000 00000000 00000000 00000000 a0000070: 00000000 00000000 00000000 00000000 a0000080: 00000000 00000000 00000000 00000000 a0000090: 00000000 00000000 00000000 00000000 a00000a0: 00000000 00000000 00000000 00000000 a00000b0: 00000000 00000000 00000000 00000000 a00000c0: 00000000 00000000 00000000 00000000 a00000d0: 00000000 00000000 00000000 00000000 a00000e0: 00000000 00000000 00000000 00000000 a00000f0: 00000000 00000000 00000000 00000000 Finished reading dbpxa250.cmd Finished reading startice.cmd MON> l /home/chrkap/u-boot/u-boot loading /home/chrkap/u-boot/u-boot section .text from a3f80000 to a3f93cd7 section .rodata from a3f93cd8 to a3f941cb section .rodata. from a3f941cc to a3f9840a section .data from a3f9840c to a3f98d17 section .u_boot_ from a3f98d18 to a3f991c7 section .bss from a3f991c8 to a3f9d70b Entry address set (pc): a3f80000 $a: a3f80000: ea000012 B 0xA3F80050 ; $a MON> g Hardware instruction breakpoint 0000000c: e59ff014 LDR pc,0x28 MON> --snap--

1 0

Re: [U-Boot-Users] CFI driver
by Sam Song 21 Oct '04

21 Oct '04

Wed, 20 Oct 2004 14:26:11 York Sun <yorksun(a)freescale.com> wrote: > Another issue is the CFI driver might not work for > all CFI compatible flash. For example, Micro > MT28F640J3. Micro uses status register instead > of DQ# polling. Somehow, we still need board > specific driver. Yeah. CFI driver still need to fix to support more cfi flash. In my experience, CFI driver support Intel FLASH better than AMD ones. I also use special flash driver for AMD flash on RPXlite_DW. I once tested it for Brad Kemp but no success. ===== Best regards, Sam _________________________________________________________ Do You Yahoo!? 150万曲MP3疯狂搜，带您闯入音乐殿堂 http://music.yisou.com/ 美女明星应有尽有，搜遍美图、艳图和酷图 http://image.yisou.com 1G就是1000兆，雅虎电邮自助扩容！ http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_…

1 0

Re: [U-Boot-Users] CFI driver
by Sam Song 21 Oct '04

21 Oct '04

Wed, 20 Oct 2004 14:26:11 York Sun <yorksun(a)freescale.com> wrote: > Another issue is the CFI driver might not work for > all CFI compatible flash. For example, Micro > MT28F640J3. Micro uses status register instead > of DQ# polling. Somehow, we still need board > specific driver. Yeah. CFI driver still need to fix to support more cfi flash. In my experience, CFI driver support Intel FLASH better than AMD ones. I also use special flash driver for AMD flash on RPXlite_DW. I once tested it for Brad Kemp but no success. ===== Best regards, Sam _________________________________________________________ Do You Yahoo!? 150万曲MP3疯狂搜，带您闯入音乐殿堂 http://music.yisou.com/ 美女明星应有尽有，搜遍美图、艳图和酷图 http://image.yisou.com 1G就是1000兆，雅虎电邮自助扩容！ http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_…

1 0