August 2005 - U-Boot

[U-Boot-Users] About creating patch for U-boot
by Stage Iup - Fabrice & Frederic 25 Aug '05

25 Aug '05

Hi i'm actually using U-Boot 1.1.2 on an AT91RM9200 based board and if changed few files to use an LXT971A Phy component instead of using the Phy Davicom component. So i would like to create a .patch file to put all my modifications on U-Boot 1.1.3. Can someone indicates me how can i do it? -- With regards Frédéric Kwiatkowski -- IFOTEC Tél : 04 76 67 53 53

2 1

[U-Boot-Users] Software watchdog on mpc8247
by Mike Rapoport 25 Aug '05

25 Aug '05

Hello, I have a custom board with mpc8247 processor. I'd like to use it's internal watchdog capability in u-boot (and linux). I've tried to use the folliwing defines in my board config file (include/configs/my_board.h): #define CONFIG_WATCHDOG 1 #if defined(CONFIG_WATCHDOG) #define CFG_SYPCR (SYPCR_SWTC|SYPCR_BMT|SYPCR_PBME|SYPCR_LBME|\ SYPCR_SWRI|SYPCR_SWP|SYPCR_SWE) #else #define CFG_SYPCR (SYPCR_SWTC|SYPCR_BMT|SYPCR_PBME|SYPCR_LBME|\ SYPCR_SWRI|SYPCR_SWP) #endif /* CONFIG_WATCHDOG */ but the board does not boot when the watchdog is enabled. I use u-boot 1.1.3 release. -- Sincerely yours, Mike Rapoport

3 7

[U-Boot-Users] Hello World application - Resets the CPU
by Swapnil Ashok Narkhede 25 Aug '05

25 Aug '05

I am working on pxa255 processor on Accelent board. Being ARM architecture, i downloaded the hello_world.bin using TFTP at 0x0c100000. The entry point is also same for ARM.But when i try to execute $ go 0x0c100000 Hello World! This is a test. i get the following output >## Starting application at 0x0C100000 >pc : [<0c140388>] lr : [<a30077cc>] >sp : a2f9fe40 ip : ffffffff fp : 00000000 >r10: 00000000 r9 : 00000000 r8 : a2f9ffdc >r7 : 00000000 r6 : 00000007 r5 : a2fe02e4 r4 : 0c100000 >r3 : 40100000 r2 : 00000001 r1 : a2fe02e4 r0 : e59ff014 >Flags: nZCv IRQs off FIQs off Mode SVC_32 >Resetting CPU ... > >resetting ... and the cpu resets. Please guide me what could be the reason for this. 2>Sorry for being stupid in previous posts. But, where do i find the Netiquette for this mailing list. Regards, Swapnil Narkhede Mob:- 0432025023 Email:- s3092131(a)student.rmit.edu.au School of Computer Science and Information Technology RMIT University, Melbourne

3 2

Re: [U-Boot-Users] AT91RM9200 Errata (Was: CSB637 support - big bug..)
by Anders Larsen 25 Aug '05

25 Aug '05

"Patrick .." <oc3an(a)gmx.net> schreibt: >On another note, is there any reason you chose a master clock divisor of 4 >instead of 3 for the CSB637? Hi, like I already said: "I got the clock values from linux 2.6.12 board-csb637.c" I didn't choose them myself. >I have looked over the data sheets for all relevant devices (SDRAM, >StrataFlash) and they definitely support at least 60Mhz (what divider 3 >gives). Feel free to change it, then (but please make sure to update arch/arm/mach-at91rm9200/board-csb637.c accordingly, otherwise at least the serial interfaces will not work). Cheers Anders P.S.: PLEASE keep the list CC'ed.

4 8

Re: [U-Boot-Users] AT91RM9200 - Flash stored initrd
by Mirco Fuchs 24 Aug '05

24 Aug '05

>>>>>Is there a simple solution to this problem? does the ram disk need >>>>to > be >>>>maually decompressed first? I had the same problem and solved it by copying the ramdisk to a sdram location before booting the kernel. >>> >>> Unfortunately yes - the 2.6 kernel is unable to handle an initrd >>> in flash (this is a FAQ, by the way). >> Regards Mirco _________________________________________________________________________ Mit der Gruppen-SMS von WEB.DE FreeMail können Sie eine SMS an alle Freunde gleichzeitig schicken: http://freemail.web.de/features/?mc=021179

1 0

Re: [U-Boot-Users] AT91RM9200 Errata (Was: CSB637 support - big bug..)
by Anders Larsen 24 Aug '05

24 Aug '05

"Patrick .." <oc3an(a)gmx.net> schreibt: >U-Boot hangs when i don't write the register in two steps. Errata #82 is >the right one - it's quite tricky to interpret correctly. I ended up with >the sequence i used from reading this errata and a fair bit of trial & >error. Strange - the original code runs on three different boards here without problems (and others are using it, too). > >Error: unrecognized/unsupported machine ID (r1 = 0x00000106). >Available machine support: >ID (hex) NAME >00000288 Cogent CSB637 I've long since fixed that - see the refreshed patch I sent a few minutes ago. Cheers Anders P.S.: - Please keep the list CC'ed - Please do not top post/full quote

2 1

Re: [U-Boot-Users] AT91RM9200 Errata (Was: CSB637 support - big bug..)
by Anders Larsen 24 Aug '05

24 Aug '05

"Patrick .." <oc3an(a)gmx.net> schreibt: >I applied your patches to the 1.1.3 version of U-Boot - they all apply >fine >except for the main csb637 patch, which complains about patching a >Makefile >and MAKEALL. Hi, that's probably due to other boards having been added in the meantime. >This is not the main problem however, > >In the AT91RM9200 initialisation code, PMC_MCKR is written incorrectly. >This register *MUST* be written in two separate steps (see the errata >sheet >for the AT91RM9200 for more details). You're referring to Errata #28, right? Reading the text it seems you're right; however, this is not special to the CSB637 board - the code in question (cpu/arm920t/at91rm9200/lowlevel_init.S) was _not_ touched by my patch. >In my case i write 0x201, followed by 0x202. OK, please provide a patch to lowlevel_init.S then. >Also, it is safe to use a divisor of 3 for the Master Clock, this gives >61.44MHz from a core of 184.32Mhz which is fine for the CSB637 (master >clock >limit is 80MHz), users should see a decent improvement in performance by >doing this as it will increase the SDRAM bandwidth by a substantial >amount. Well, I got the clock values from linux 2.6.12 board-csb637.c; does Linux still boot correctly with your change? Cheers Anders CC'ed to the list, since this is relevant to ALL at91rm9200 users

3 4

[U-Boot-Users] [PATCH] fix make dependencies for at91rm9200 and ks8695 cpus
by Steven Scholz 24 Aug '05

24 Aug '05

Hi there, please apply the attached patch. Without this patch lowlevel_init.s is _not_ rebuild when board config file (or other important include files) is changed! -- Steven diff --git a/CHANGELOG b/CHANGELOG --- a/CHANGELOG +++ b/CHANGELOG @@ -2,6 +2,9 @@ Changes for U-Boot 1.1.4: ====================================================================== +* Fix make dependencies for at91rm9200 and ks8695 cpus + Patch by Steven Scholz, 23 Aug 2005 + * Add esd cpci5200 and pf5200 boards Patch by Reinhard Arlt, 22 Aug 2005 diff --git a/cpu/arm920t/at91rm9200/Makefile b/cpu/arm920t/at91rm9200/Makefile --- a/cpu/arm920t/at91rm9200/Makefile +++ b/cpu/arm920t/at91rm9200/Makefile @@ -35,8 +35,8 @@ $(LIB): $(OBJS) $(SOBJS) ######################################################################### -.depend: Makefile $(OBJS:.o=.c) - $(CC) -M $(CFLAGS) $(OBJS:.o=.c) > $@ +.depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) + $(CC) -M $(CFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ sinclude .depend diff --git a/cpu/arm920t/ks8695/Makefile b/cpu/arm920t/ks8695/Makefile --- a/cpu/arm920t/ks8695/Makefile +++ b/cpu/arm920t/ks8695/Makefile @@ -35,8 +35,8 @@ $(LIB): $(OBJS) $(SOBJS) ######################################################################### -.depend: Makefile $(OBJS:.o=.c) - $(CC) -M $(CFLAGS) $(OBJS:.o=.c) > $@ +.depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) + $(CC) -M $(CFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ sinclude .depend

2 3

RE: [U-Boot-Users] AT91RM9200 and external clock instead of crystal?
by Martin Krause 24 Aug '05

24 Aug '05

Hi Steven u-boot-users-admin(a)lists.sourceforge.net wrote on : > Hi there, > > I wonder if I am the only one using an external clock oscillator > (16MHz) as main clock instead of a crystal with Atmel's AT91RM9200. Sorry, we use an 18.4320 MHz quartz crystal (and a 32.768 KHz quartz crystal as slow clock). Regards, Martin

1 0

[U-Boot-Users] AT91RM9200 and external clock instead of crystal?
by Steven Scholz 24 Aug '05

24 Aug '05

Hi there, I wonder if I am the only one using an external clock oscillator (16MHz) as main clock instead of a crystal with Atmel's AT91RM9200. Cause I am having huge problems with the bits MCKRDY, LOCKA and LOCKB in PMC_SR I'd love hear of other trying the same. BTW: Could some please just do a "md.l fffffc68 1" just afetr U-Boot started and send me the output ... Thanks a million, -- Steven

1 0

RE: [U-Boot-Users] AT91RM9200 Errata (Was: CSB637 support - big bug..)
by Martin Krause 24 Aug '05

24 Aug '05

Hi Steven, Steven Scholz wrote on : > Martin, > > > A clock rate > 180 MHz could be problematic. According errata 42 > > (AC Characteristics: PLL Frequency Limitation), in AT91RM9200 errata > > sheet (doc6015) the PLL is limited to 180 MHz. We already had > > problems with this bug (with about 10%-15% of the CPUs). After > > configuring the PLL for 179 MHz no errors occour any mor (before we > > used 207 MHz). > > Which errors and problems did you encounter? The Linux kernel (2.4.27 linuxarm tree from Denx) did not run stable on the affected boards. We see sporadic failures and core dumps. Regards, Martin

1 0

Re: [U-Boot-Users] Re: MIPS LE build problems
by Wolfgang Denk 24 Aug '05

24 Aug '05

In message <4304D3FD.7080107(a)smiths-aerospace.com> you wrote: > > As noted in other email in this thread, executing the above code won't > work. What about simply compiling a file containing: > > constant int data = 0x01234567; > > objdumping the data section, and looking (grepping) to see if the data > section has 0x12345678 or 0x78563412? Doesn't work as objdump will be user friendly and always print the "correct" value, i. e. 0x01234567. But the idea is good. The attached test script works with the tool chains available to me. Can others please test this, too? Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de Many aligators will be slain, but the swamp will remain.

4 6

RE: [U-Boot-Users] AT91RM9200 Errata (Was: CSB637 support - big bug..)
by Martin Krause 24 Aug '05

24 Aug '05

Hi, Anders Larsen wrote on : > "Patrick .." <oc3an(a)gmx.net> schreibt: > > Also, it is safe to use a divisor of 3 for the Master Clock, this > > gives > > 61.44MHz from a core of 184.32Mhz which is fine for the CSB637 > > (master clock limit is 80MHz), users should see a decent > > improvement in performance by doing this as it will increase the > > SDRAM bandwidth by a substantial amount. > > Well, I got the clock values from linux 2.6.12 board-csb637.c; > does Linux still boot correctly with your change? I already posted this on the list, but a little reminder won't hurt :) A clock rate > 180 MHz could be problematic. According errata 42 (AC Characteristics: PLL Frequency Limitation), in AT91RM9200 errata sheet (doc6015) the PLL is limited to 180 MHz. We already had problems with this bug (with about 10%-15% of the CPUs). After configuring the PLL for 179 MHz no errors occour any mor (before we used 207 MHz). Regards, Martin

3 2

[U-Boot-Users] RFC: U-Boot Environment support in SystemAce Compact FLASH
by Keith J Outwater 23 Aug '05

23 Aug '05

Hello all - I have completed the initial port of U-Boot to a custom PPC405/VirtexII Pro FPGA board and I am starting to look at ways to store the U-Boot environment in the CF card used for FPGA configuration by the Xilinx SystemAce. As it stands now, there is DOS FAT read support in U-Boot but no write support, so that would have to be added if the environment was to be stored as a DOS file on the CF card. Another option might be to partition the CF card so as to leave a few sectors unused and use low-level sector read/write routines to store the environment directly to the CF card. This solution seems straightforward, but seems somehow inelegant. I am leaning toward the approach of adding DOS FAT write support and adjusting the initial U-Boot environment to provide sufficient stack space to run the DOS filesystem code during initial boot. Does this seem reasonable? Does anyone know where the original DOS filesystem code came from? Keith

4 5

[U-Boot-Users] CSB637 support
by Patrick .. 23 Aug '05

23 Aug '05

Hi, I have searched long and hard on the lists and have found much discussion about csb637 support, but i am unable to find the actual patch. Is someone able to point me in the right direction please? Thanks, -Patrick -- 5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail +++ GMX - die erste Adresse f�r Mail, Message, More +++

3 3

RE: [U-Boot-Users] [PATCH] cfi_flash.c patches
by Woodruff, Richard 23 Aug '05

23 Aug '05

Tolunay, Several Intel chips do provide hardware level protection locks which get cleared at reset. It is useful to use this hardware feature at boot to help protect flash sectors from upper level code during normal operation. The u-boot software lock is nice, but doesn't extend beyond u-boot code while the hardware lock does. The difference in behavior between chips is the issue here. Perhaps it is better to add another compile time flag which allows the hardware features to be used on such chips. Your point is one _hardware_ features behavior should be valued over another's. Having them both via flags is probably the way to go. Regards, Richard W. > -----Original Message----- > From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users- > admin(a)lists.sourceforge.net] On Behalf Of Tolunay Orkun > Sent: Friday, August 19, 2005 1:37 PM > To: Sangmoon Kim > Cc: u-boot; Wolfgang Denk > Subject: Re: [U-Boot-Users] [PATCH] cfi_flash.c patches > > Dear Sangmoon, > > I've examined your patch for clearing the protection of flash sectors > automatically during flash init. As a matter of fact a similar patch was > also proposed by someone else and I had commented on it as well. > > I think this is wrong approach. These sectors are protected for a reason > (to prevent accidental writes - forgetting to enable protection). > > You should enable CFG_FLASH_PROTECTION in your board config file. If you > don't do this U-Boot will do software protection of sectors (which is > really for those flash chips with no hardware protection capability) and > "protect off" will not issue unlock commands as you may have witnessed. > > CFG_FLASH_PROTECTION will enable the "protect off" command to disable > protection properly on these sectors as it should. > > IMHO, No patch is needed here! Perhaps we need to add a couple of > comment lines in README (DULG?) for documentation purposes. Wolfgang, > can you comment here. > > Best regards, > Tolunay > > Sangmoon Kim wrote: > > Hi, > > The two patches attached are for drivers/cfi_flash.c. > > > > cfi_flash-protect.patch adds CFG_FLASH_PROTECT_CLEAR > > because for some flash memories(such as 28F320C3) > > all banks are protected after reset. > > > > cfi_flash-buffer.patch makes write_buff not to call > > flash_write_cfibuffer if buffer_size is1. > > Because for flash memories with buffer_size 1, > > buffer write is not supported. > > > > Regards, > > Sangmoon Kim > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > U-Boot-Users mailing list > U-Boot-Users(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/u-boot-users

3 2

[U-Boot-Users] fatload problems with CF
by Keith J Outwater 23 Aug '05

23 Aug '05

Hello all - I am having a strange problem with the fatload command. I am able to do a 'fatls' on a CD card connected to a SystemACE controller but when I try to load a file on any partition using 'fatload', the FAT code is calling the SystemACE specific sector read routine with a block count of zero. I am using a U-Boot snapshot from CVS that is about a month old. Thanks! Keith

1 0

[U-Boot-Users] About CS8900A's MAC address
by mail2jarod 23 Aug '05

23 Aug '05

Hi all, I am porting u-boot-1.1.3 to a Samsung S3C44B0X based board that I bought several months ago. It consists of a CS8900A as its ethernet controller. When I write a configuration header file (include/configs/jx44b0.h) for the board, I find that I don't know the CS8900A's MAC address. I wonder how to figure it out. Sorry for my poor English. Any advice should be appreciated. Regards, Jarod Wang

1 0

[U-Boot-Users] Using "cu" for tranferring files
by Swapnil Ashok Narkhede 23 Aug '05

23 Aug '05

I did try to use "cu" for tranferring the files. But i can see the monitor command prompt and not enter any input. This problem is related to the flow control, i reckon, and so i try to figure out how do i set it. I have used the settings as mentioned in the DULG manual for setting up "cu". hardflow is set to false. but still i cannot input any values. Is there any other way of setting the hardware and software flow control to none. How do i get this working. Regards, Swapnil Narkhede Mob:- 0432025023 Email:- s3092131(a)student.rmit.edu.au School of Computer Science and Information Technology RMIT University, Melbourne

1 0

[U-Boot-Users] regarding uboot
by prabha.j＠tcs.com 23 Aug '05

23 Aug '05

Sir, My name is prabha. I have some questions regarding the uboot. I hope u will help me in this regard. 1.Actually i have a target as intel board with P4 machine and having 830 as intel chip set. I searched whether uboot supports this architecture. I came to know that uboot supports very few intel boards. Now the question is how to bring up this board using uboot and how to get the toolchain for this board. Will uboot supports this architecture or not. 2. I am using p4 as my host m/c and untarred uboot1.1.3 and when i gave make sc520_cdp_config it gives Configuring for sc520_cdp board... and after this if i give make it gives error as make 'make[1]: Entering directory `/root/praba/u-boot-1.1.3/tools' make[1]: `.depend' is up to date. make[1]: Leaving directory `/root/praba/u-boot-1.1.3/tools' make[1]: Entering directory `/root/praba/u-boot-1.1.3/examples' make[1]: `.depend' is up to date. make[1]: Leaving directory `/root/praba/u-boot-1.1.3/examples' make[1]: Entering directory `/root/praba/u-boot-1.1.3/post' make[1]: `.depend' is up to date. make[1]: Leaving directory `/root/praba/u-boot-1.1.3/post' make[1]: Entering directory `/root/praba/u-boot-1.1.3/post/cpu' make[1]: `.depend' is up to date. make[1]: Leaving directory `/root/praba/u-boot-1.1.3/post/cpu' make -C tools all make[1]: Entering directory `/root/praba/u-boot-1.1.3/tools' gcc -g -Wall -pedantic -idirafter ../include -DTEXT_BASE=0x387c0000 -DUSE_HOSTCC -O -c envcrc.c gcc -g -idirafter ../include -DTEXT_BASE=0x387c0000 -DUSE_HOSTCC -c environment.c gcc -Wall -pedantic -idirafter ../include -DTEXT_BASE=0x387c0000 -DUSE_HOSTCC -O -o envcrc envcrc.o crc32.o environment.o make[1]: Leaving directory `/root/praba/u-boot-1.1.3/tools' make -C examples all make[1]: Entering directory `/root/praba/u-boot-1.1.3/examples' gcc -g -Os -D__KERNEL__ -DTEXT_BASE=0x387c0000 -I/root/praba/u-boot-1.1.3/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc/i386-redhat-linux/3.4.2/include -pipe -DCONFIG_I386 -D__I386__ -march=i386 -Werror -Wall -Wstrict-prototypes -c -o 82559_eeprom.o 82559_eeprom.c 82559_eeprom.c: In function `memcpy': 82559_eeprom.c:57: warning: use of cast expressions as lvalues is deprecated 82559_eeprom.c:57: warning: use of cast expressions as lvalues is deprecated make[1]: *** [82559_eeprom.o] Error 1 make[1]: Leaving directory `/root/praba/u-boot-1.1.3/examples' make: *** [examples] Error 2 Now the question is that should i have to build toolchain for this or not. Since this is a intel board i thought it will take the same gcc which host machine have and do the necessary steps. But i think it is not the case. I didn't do any changes in the Makefile. Please help me in this regard. Regards Prabha J. Tata Consultancy Services Limited Mailto: prabha.j(a)tcs.com Website: http://www.tcs.com Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

1 0

[U-Boot-Users] Boot x86 target from flash, with the image and file system on the x86 host.
by batsayan.das＠tcs.com 23 Aug '05

23 Aug '05

I am exploring the nfs boot of Fedora 3 for x86 platform. I have two x86 m/c. One(host) is loaded with FC3 . The other (target) has only blank IDE flash dive. My plan is : 1.Prepare kernel image "at the host for the target". (Pls note that host and target both are x86. ) 2.Prepare file system "at the host for the target". 3.NFS mount the kernel image and the file system at host. 4.Connect the flash to the host burn the flash with kernel image 5.Connect the flash to the target and power on the target. 6.The target will, download the image from the host; mounts file sys and boots. The flash should have some boot loader like u-boot along with the kernel image. I am not sure whether bootloader + kernel image can be mixed together and put into the flash. The other solution may be to put only the bootloader onto the flash. When the target is powered on with the IDE flash, the (boot loader+ kernel image) OR (the boot loader) should start up the x86 platform. Pls note that the kernel image, file system etc are kept on the host system by nfs mount. Any pointer to the above will be of great help. Thanks, Das Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

1 0

[U-Boot-Users] debugging U-boot with GDB on a Au1550
by Cliff Brake 22 Aug '05

22 Aug '05

I have U-boot running on a Au1550 platform. I have verified that re-location to RAM works but the system is crashing somewhere in board_init_r. I would like to debug this with GDB and a BDI2000, but am running into a few issues. U-boot for this platform is linked to 0xbfc00000 (the ROM reset vector). This is not what I am used to as most ARM platforms are linked to the RAM location. After U-boot is relocated to RAM, how do I tell GDB what the new link address is (0x80fdc000 in this case)? Thanks, Cliff -- ======================= Cliff Brake http://bec-systems.com

2 3

Re: Re: [U-Boot-Users] loads command cannot transfer srec file
by Swapnil Ashok Narkhede 22 Aug '05

22 Aug '05

I am now using Kermit for the serial communication. But still i am having the same problem. When i use loads 40000 i get the output as ## Ready for S-Record download ... and then the system seems to do nothing. When i use loadb ##Ready for binary (kermit) download to 0xA0800000 at 115200 bps.. and then the system seems to do nothing. Please guide me what could be the reason for this -----Original Message----- From: Wolfgang Denk <wd(a)denx.de> To: "Swapnil Ashok Narkhede" <S3092131(a)student.rmit.edu.au> Date: Mon, 22 Aug 2005 14:06:27 +0200 Subject: Re: [U-Boot-Users] loads command cannot transfer srec file In message <1124704021.89a455bcS3092131(a)student.rmit.edu.au> you wrote: > > I am using Windows Hyper Terminal for serial communication with the Accelen > t board having pxa255 processor. Please use shorter lines. Your text is nearly unreadable. > I am getting the monitor command prompt. I have to download hello_world.sre > c onto the flash. > When i use loads 40004 i get > ## Ready for S-Record download ... > and then the system seems to do nothing. This is to be expected. Please read the manual (DULG) how to use S-Record download. Note that Windows Hyperterminal is *not* listed as supported tool for this purpose. > I cannot specify the path of the file to be downloaded. This is then a problem with Hyperterminal. Use the recommended tools instead. > 1>>Please let me know what could be the problem with this and where is the You're using the wrong tools. > default path for file download set. There is no default path. It's up to the terminal program to select and send the appropriate file. > 2>>I downloaded the hello_world.bin through the JTAG pin we have made and > tried to run hello_world application using > go 40004 Hello World! This is a test and i get number of junk characters li > ke which i think could be because of some undefined instruction what shou > ld be done in this case. Debug the problem. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de grep me no patterns and I'll tell you no lines. Regards, Swapnil Narkhede Mob:- 0432025023 Email:- s3092131(a)student.rmit.edu.au School of Computer Science and Information Technology RMIT University, Melbourne

2 1

[U-Boot-Users] U-Boot interpreter syntax change?
by Keith J Outwater 22 Aug '05

22 Aug '05

Hello - I was recently porting some old U-Boot scripts to my new board and I was having a problem with the kernel command line. Instead of getting substitutions for things like $(ipaddr), I was seeing, literally, $(ipaddr) in the kernel command line as reported by the kernel. I also saw a similar problem with the U-Boot tftpboot command. This: Ant2> setenv load_kernel tftp $(loadaddr) $(kernel_image); Ant2> run load_kernel Gives this output from U-Boot: Ant2> run load_kernel TFTP from server 192.168.0.100; our IP address is 192.168.0.10 Filename '$(kernel_image)'. While this: Ant2> setenv load_kernel tftp $loadaddr $kernel_image Ant2> run load_kernel Gives this: Ant2> run load_kernel TFTP from server 192.168.0.100; our IP address is 192.168.0.10 Filename 'kernel.uImage'. Which works. I checked the DULG, and the guide indicates that the first form shown above is correct. Have things changed or do I have something misconfigured? Any ideas? Thanks, Keith

2 2

[U-Boot-Users] test variable existence in hush
by Andreas Engel 22 Aug '05

22 Aug '05

Hi, can anyone confirm that this is a bug in the hush shell: both test -n "$foo" && echo yes and test -z "$foo" && echo yes result in nothing echoed if foo is not defined. If, on the other hand, foo is defined to a string containing blanks, both commands will echo yes. Is there another way to check the existence of a variable? Regards, Andreas Engel

2 2

[U-Boot-Users] loads command cannot transfer srec file
by Swapnil Ashok Narkhede 22 Aug '05

22 Aug '05

Hi, I am using Windows Hyper Terminal for serial communication with the Accelent board having pxa255 processor. I am getting the monitor command prompt. I have to download hello_world.srec onto the flash. When i use loads 40004 i get ## Ready for S-Record download ... and then the system seems to do nothing. I cannot specify the path of the file to be downloaded. 1>>Please let me know what could be the problem with this and where is the default path for file download set. 2>>I downloaded the hello_world.bin through the JTAG pin we have made and tried to run hello_world application using go 40004 Hello World! This is a test and i get number of junk characters like which i think could be because of some undefined instruction what should be done in this case. Regards, Swapnil Narkhede Mob:- 0432025023 Email:- s3092131(a)student.rmit.edu.au School of Computer Science and Information Technology RMIT University, Melbourne

2 1

RE: [U-Boot-Users] Any default audio card driver in U-boot?
by Martin Krause 22 Aug '05

22 Aug '05

Hi, u-boot-users-admin(a)lists.sourceforge.net wrote on Monday, August 22, 2005 5:42 AM: > Dear all, > I'm searching for some example for audio card driver for U-boot? > But it seems most drivers in drivers/ are for ethernet card. Can > anyone tell me where I can find it in u-boot? Thanks a lot!~ We implemented some _very_ basic sound commands (play a beep, play square wave, play a microsoft .wav file) to test our hardware with it. Perhaps you will find this usefull. Please look at: http://source.denx.net/cgi-bin/gitweb.cgi?p=u-boot.git;a=commit;h=6617aae9b… The commands are implemented in board/tqm5200/cmd_stk52xx.c Regards, Martin TQ-Systems GmbH Mühlstraße 2, Gut Delling, 82229 Seefeld Tel. +49 (8153) 93 08-157, Fax +49 (8153) 93 08-7157 martin.krause(a)tqs.de www.tq-group.com

2 1

[U-Boot-Users] (no subject)
by 刘辉 22 Aug '05

22 Aug '05

Hi all: i want to build up a linux system with JFFS2. Is there any document show what shell i do in uboot to support JFFS2? thanks! 　　　　　　　　liuhuicumt(a)tom.com 　　　　　　　　　　2005-08-22

1 0

[U-Boot-Users] BDI config file for AMCC Bamboo
by Rolf Offermanns 22 Aug '05

22 Aug '05

Hi All! I would like to try u-boot on the AMCC Bamboo board but I am not able to get the flashes working with the BDI2000. I found a config file on the denx ftp site but unfortunately the [FLASH] section is missing. Does someone have a working config file *with* flash support? Sorry for being slightly offtopic. Thanks, -Rolf -- Rolf Offermanns <roffermanns(a)sysgo.com> SYSGO AG Tel.: +49-6136-9948-0 Am Pfaffenstein 14 Fax: +49-6136-9948-10 55270 Klein-Winternheim http://www.sysgo.com

2 1

[U-Boot-Users] Any default audio card driver in U-boot?
by boku 22 Aug '05

22 Aug '05

Dear all, I'm searching for some example for audio card driver for U-boot? But it seems most drivers in drivers/ are for ethernet card. Can anyone tell me where I can find it in u-boot? Thanks a lot!~ Regards,

3 2

RE: [U-Boot-Users] [PATCH] cfi_flash.c patches
by Woodruff, Richard 19 Aug '05

19 Aug '05

> I do not know of any Intel flash that would unlock sectors on "Reset". > Can you be specific? Even so it is not relevant to the problem of this > specific flash which does 100% opposite (intentionally and for a very > good reason) 28F256L18. If I issue lock commands they take and further writes are not allowed with out an unlock sequence. If I power cycle the board all previous lock information is no longer there. > I do know early Intel flash would unlock all flashs sectors as you > unlock one so all previous locks would have to be redone. U-Boot has > code to fix this. I think you are confusing with this type of Intel flash. I think this is something else also. I'll scan the rest of your comments in a bit. Regards, Richard W.

1 0

[U-Boot-Users] How to install U-Boot into IntegratorAP?
by boku 19 Aug '05

19 Aug '05

Dear experts, I've compiled U-Boot and wanna try if it works on the target board. I got the ARM RVDS and Multi-ICE. How can I use it to install the U-boot to flash memory and see if the compiled u-boot functions okay? Thank you!~ Best Wishes, Boku

2 1

[U-Boot-Users] Au1x00 PCMCIA support
by Matej Kupljen 18 Aug '05

18 Aug '05

Hi Is anybody working on a AMD Alchemy Au1x00 PCMCIA support, especially Au1200? If not, I'll start it and would like to know if there is anybody interested in this. BR, Matej

2 5

[U-Boot-Users] Never-ending loop in flash_init (compiler bug???)
by llandre 18 Aug '05

18 Aug '05

I have a problem with the function flash_init in the file board/scb9328/flash.c. It seems the compiler ( 3.3.3 (DENX ELDK 3.1 3.3.3-8) )does not compile it correctly. The for loop near line 124 results in a never-ending loop (see also this picture http://www.dave-tech.it/download/misc/tmp/flash_init-loop.bmp). Any hints? llandre DAVE Electronics System House - R&D Department web: http://www.dave-tech.it email: r&d2(a)dave-tech.it

1 0

[U-Boot-Users] Script based testing?
by Charles J Gillan 17 Aug '05

17 Aug '05

We are planning to write some Perl scripts to automate our testing and we will use the U-Boot shell via the serial interface. This is appealing because, for example, we can put tests into lengthy repeat loops and run them automatically to stress our board. We will use some of our own custom commands that we added to the build for the FPGAs on our board but it seems to us very likely that this script based testing has probably been done before by many U-Boot users for the "common" commands that are in the build. I am aware of the Kermit scripts in the tools/scripts directory but they perform only a few commands. I checked the mail archive at SourceForge but found nothing relevant, so I am raising this on the list myself. Are there any existing scripts (Perl or any other language) for U-Boot command line testing and that are in the public domain already ? Thanks, Charles. ---------------------------------------------------------------------------- -------- Dr Charles J Gillan The Institute of Electronics, Communications and Information Technology (ECIT), Queen's University Belfast, Titanic Quarter Queen's Road, Queen's Island, Belfast, BT3 9DT Northern Ireland, UK Tel: +44 (0) 2890 971847 Fax: +44 (0) 2890 971702 ---------------------------------------------------------------------------- --------

2 1

[U-Boot-Users] RPXClassic?
by Travis B. Sawyer 17 Aug '05

17 Aug '05

Greetings: I see that the RPXClassic (E.P. CLLF BW31) is an abandoned board. I have access to a couple of these little gems, but all have the PlanetCore bootloader. Does anyone have a little howto kicking around on replacing the bootloader with Das U-Boot. I hacked my way through one, and ended up having to use the BDI, but if someone has a proceedure, it would help me out a lot. I'm planning on putting a couple of these to use for some model railroad automation (Read: not important, but fun). TIA, Travis

2 2

[U-Boot-Users] Monitor Command Prompt displayed but system hangs
by Swapnil Ashok Narkhede 17 Aug '05

17 Aug '05

I am a beginner in embedded software development. I am working on porting U-BOOT for pxa255 processor on Accelent board. I want to get the Monitor command prompt through serial communication to my machine so that i can use the monitor commands to check the system status. We are booting from the FLASH and not from the RAM. I am able to get the Monitor command prompt but the system seems to be hanged, i cannot input any command. What could be the reason for this? I am held up with this problem for quite some time. Eagerly awaiting reply. Regards, Swapnil Narkhede Mob:- 0432025023 Email:- s3092131(a)student.rmit.edu.au School of Computer Science and Information Technology RMIT University, Melbourne

2 1

[U-Boot-Users] Monitor command prompt displayed but system hangs
by Swapnil Ashok Narkhede 17 Aug '05

17 Aug '05

Hello! I am a beginner in embedded software development. I am working on porting U-BOOT for pxa255 processor on Accelent board. I want to get the Monitor command prompt through serial communication to my machine so that i can use the monitor commands to check the system status. We are booting from FLASH and not from RAM I am able to get the Monitor command prompt but the system seems to be hanged, i cannot input any command. What could be the reason for this? I am held up with this problem for quite some time. Eagerly awaiting reply. Regards, Swapnil Narkhede Mob:- 0432025023 Email:- s3092131(a)student.rmit.edu.au School of Computer Science and Information Technology RMIT University, Melbourne

1 0

[U-Boot-Users] what happened?
by lixidong＠EmersonNetwork.com.cn 17 Aug '05

17 Aug '05

make[1]: *** Warning: File `.depend' has modification time in the future (2008-03-19 02:56:50 > 2005-08-17 18:20:52) make[1]: `.depend' is up to date. make[1]: warning: Clock skew detected. Your build may be incomplete.

3 2

[U-Boot-Users] U-Boot for M9328MX1ADS/M9328MXLADS Ver 2.0 board
by llandre 17 Aug '05

17 Aug '05

Hi all, I have on my desktop a M9328MX1ADS/M9328MXLADS Ver 2.0. This board is equipped with two Am29PDL127H63VKI Flash memories. I'm a little bit confused about which configuration I should use for this board. IIUC mx1ads configuration is used for the 1.0 version of the board that is equipped with synchronous flash memories, so mx1fs2 is the right configuration. Is it correct? Thanks in advance, llandre DAVE Electronics System House - R&D Department web: http://www.dave-tech.it email: r&d2(a)dave-tech.it

1 1

[U-Boot-Users] U-Boot Developer's Information
by Wolfgang Denk 17 Aug '05

17 Aug '05

Hello everybody. the number of contributions to the U-Boot project has been continuously growing, and for some time I've been looking for more efficient ways to deal with all the patches and submissions. The current development cycle with a central CVS repository at SourceForge has a couple of problems: * SF is slow, and it takes sometimes pretty long until check-ins are visible to the public. If the CVS server at SF is down, the whole U-Boot development stalls. * CVS is cumbersome to use when it comes to handling branches. So far we avoided branches in U-Boot completely, with the result that several interesting contributions were blocked for a long time to avoid de-stabilization of the only branch we had - often so long until the patches were not applicable any more. Many other patches and contributions got delayed because of this for a long time, too. * Every new commit to the only branch needed at least a certain amount of testing, so preparing the tree for a "release" was always pretty challenging. This resulted in long delays between releases, which in turn caused many people to use old code as base for new work which called for trouble later. U-Boot Version 1.1.3, which was released on August 14, 2005, was the last release following this old development cycle. Big changes are coming. U-Boot Source Repository: ========================= Starting immediately, we use git (see http://git.or.cz/) as software configuration management (SCM) tool for U-Boot development. Please see http://source.denx.net/en/Documents/GitDocs for some introductory information for git. The "master repository" for U-Boot is available from rsync://source.denx.net/git/u-boot.git or http://source.denx.net/git/u-boot.git The CVS repository at SourceForge will be kept in sync with the git tree, but there is no guarantee how long I will do this, so it's use is deprecated. Use git, or feel free to use one of the 'porcelains' like cogito on top of git. [FYI: SourceForge considers it "not an immediate priority" to host and support git based repositories.] Submitting Patches: =================== >From now on I will also try to enforce stricter rules on contributed code. Please read the following carefully when you are working with U-Boot and want to send your modifications back to the public source tree: (1) Comply with the coding standards: All contributions to U-Boot must conform to the Linux kernel coding style; see the file "Documentation/CodingStyle" in your Linux kernel source directory. Please note that U-Boot is implemented in C (and to some small parts in Assembler); no C++ is used, so please do not use C++ style comments (//) in your code. Please also comply with the following formatting rules: - remove any trailing white space - use TAB characters for indentation, not spaces - make sure NOT to use DOS '\r\n' line feeds - do not use more than 2 consecutive empty lines in source files - do not add trailing empty lines to source files Submissions which do not conform to the standards will be rejected with a request to reformat the changes. (2) Make separate commits for logically separate changes. Unless your patch is really trivial, you should not be sending out a patch that was generated between your working tree and your local commit head. Instead, always make a commit with complete commit message and generate a series of patches from your repository. It is a good discipline. Describe the technical details of the change(s). If your description starts to get long, that's a sign that you probably need to split up your commit to finer grained pieces. Make sure to update the CHANGELOG file appropriately. Don't forget to register yourself in the MAINTAINERS file if you add new processor or board support. (3) Use branches for sets of modifications that belong together logically. If you're adding support for a new processor or a new board or a bigger new feature (like re-writing all code that deals with NAND flash) then we strongly recommend to keep all this work in a separate branch. This may not be strictly necessary for your own work, but it will make your own life easier in the long term, and if you ever intend to allow direct pulling from your tree this will be mandatory. See http://source.denx.net/en/view/Documents/GitAdvancedUse#Linux_subsystem_mai… for some excellent advice. (4) Always send plain patches only. Do not send complete source files or tarballs with sources or tarballs with patches. Do not send compressed or encoded files. Anything that cannot be applied directly as a patch may be rejected. (5) Generate your patch using git/cogito out of your commits. git diff tools generate unidiff which is the preferred format. You do not have to be afraid to use -M option to "git diff" or "git format-patch", if your patch involves file renames. The receiving end can handle them just fine. Please make sure your patch does not include any extra files which do not belong in a patch submission. Make sure to review your patch after generating it, to ensure accuracy. Before sending out, please make sure it cleanly applies to the "master" branch head. (6) Sending your patches. People on the U-Boot mailing list needs to be able to read and comment on the changes you are submitting. It is important for a developer to be able to "quote" your changes, using standard e-mail tools, so that they may comment on specific portions of your code. For this reason, all patches should be submitting e-mail "inline". WARNING: Be wary of your MUAs word-wrap corrupting your patch. Do not cut-n-paste your patch. Plain text(!) MIME attachments are acceptable, too. Remember that there is a size limit of 40 kB for postings on the mailing list. If you find yourself running into this limit this is an indication that you probably need to split up your commit into smaller pieces. It is common convention to prefix your subject line with [PATCH]. This lets people easily distinguish patches from other e-mail discussions. "git format-patch" command follows the best current practice to format the body of an e-mail message. At the beginning of the patch should come your commit message, ending with the Signed-off-by: lines, and a line that consists of three dashes, followed by the diffstat information and the patch itself. If you are forwarding a patch from somebody else, optionally, at the beginning of the e-mail message just before the commit message starts, you can put a "From: " line to name that person. You often want to add additional explanation about the patch, other than the commit message itself. Place such "cover letter" material between the three dash lines and the diffstat. Never send compressed or encoded messages. Do not let your e-mail client send quoted-printable. Many popular e-mail applications will not always transmit a MIME attachment as plain text, making it impossible to comment on your code. A MIME attachment also takes a bit more time to process. This does not decrease the likelihood of your MIME-attached change being accepted, but it makes it more likely that it will be postponed. Exception: If your mailer is mangling patches then someone may ask you to re-send them using MIME. NEVER SEND HTML MESSAGES TO THE LIST. NEVER!!! Note that your maintainer is subscribed to the U-Boot mailing list so there is no need to put him on separate Cc: (7) Sign your work To improve tracking of who did what, we've borrowed the "sign-off" procedure from the Linux kernel project on patches that are being emailed around. Although U-Boot is a lot smaller project it is a good discipline to follow it. The sign-off is a simple line at the end of the explanation for the patch, which certifies that you wrote it or otherwise have the right to pass it on as a open-source patch (more precisely: as Free Software under GPL). The rules are pretty simple: if you can certify the below: Developer's Certificate of Origin 1.1 By making a contribution to this project, I certify that: (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it. (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved. then you just add a line saying Signed-off-by: Random J Developer <random(a)developer.example.org> Releases: ========= Our intention is to produce "releases" of U-Boot much more frequently now. We will use the following numbering scheme for U-Boot releases: version.patchlevel.sublevel Releases where "sublevel" is zero will be called "stable". The previous release was 1.1.3, and we're working on 1.1.4 now, so the next "stable" release might be called "1.2.0". That's it for now. Hope you git along with all this Great New Stuff :-) Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de By the way, ALL software projects are done by iterative prototyping. Some companies call their prototypes "releases", that's all.

6 10

[U-Boot-Users] PATCH: add STx XTc
by Dan Malek 16 Aug '05

16 Aug '05

Hi Wolfgang. Here is a patch against the current CVS tree that adds support for the new Silicon Turnkey eXpress XTc 87x/88x board. Thanks. -- Dan

4 9

[U-Boot-Users] [PATCH] Fix JFFS2 command return values
by Andreas Engel 16 Aug '05

16 Aug '05

CHANGELOG entry: * Patch by Andreas Engel, 15 July 2005 fixed return values of the jffs2 commands so we can use them to, e.g., check the existence of a file with "if ls foo; then this; else that; fi" in the hush shell

2 3

[U-Boot-Users] PATCH : add MX21ads
by Tomko 16 Aug '05

16 Aug '05

Hi Wolfgang. Here is the patch adds support for mx21ads on u-boot 1.1.3. Regards, TOM

1 0

[U-Boot-Users] CFI, saveenv Flash no Erased
by Scott McNutt 15 Aug '05

15 Aug '05

Hi All, First, my thanks to the CFI developers -- great job! With the erase and cp commands, the CFI flash driver seems just fine. However, when I execute saveenv (env is in flash), I observe "Flash not Erased". I'm using AMDLV065D on a Nios-II board with the latest cfi_flash.c (rev 1.18). In routine flash_write_cfiword (cfi_flash.c, line 1146), flag == 0, indicating that the flash is not "(sufficiently) erased": flag = ((cptr.cp[0] & cword.c) == cword.c); Adding a delay of about 500 msec corrects the problem, and I was able to trace the bits changing (eventually) to 0xff with some hack code. This is the first time I've worked with the CFI code, so I'm looking for some guidance from someone familiar with the code on how to track down the problem/potential solution & where I should focus my attention. Thanks, --Scott

3 3

[U-Boot-Users] PATCH: Add sandburst metrobox board support [2/3]
by Travis B. Sawyer 15 Aug '05

15 Aug '05

[Note: My previous submission was rejected due to size] This patch adds the Sandburst Metrobox and Sandburst Karef Boards. Both are PPC440GX based, direct peripheral bus connected compact flash, dallas rtc, write protected eeprom (strappings and ethernet MAC address). EMAC 2 is the management ethernet interface, EMAC 3 goes to a board to board connector. These boards are reference designs for the Sandburst HiBEAM chipset. See http://www.sandburst.com for more board information (predominately marketing speak). This patch is against source forge cvs 12July2005, at approximately 0900 EDT. CHANGELOG: * Patch by Travis B. Sawyer, 12 Jul 2005: Add Sandburst Metrobox and Sandburst Karef board support packages. Second serial port on 440GX now defined as a system device. Add 'Short Etch' code for Cicada PHY within 440gx_enet.c Best regards, Travis Sawyer

2 1

[U-Boot-Users] PATCH: Add sandburst metrobox board support [1/3]
by Travis B. Sawyer 15 Aug '05

15 Aug '05

[Note: My previous submission was rejected due to size] This patch adds the Sandburst Metrobox and Sandburst Karef Boards. Both are PPC440GX based, direct peripheral bus connected compact flash, dallas rtc, write protected eeprom (strappings and ethernet MAC address). EMAC 2 is the management ethernet interface, EMAC 3 goes to a board to board connector. These boards are reference designs for the Sandburst HiBEAM chipset. See http://www.sandburst.com for more board information (predominately marketing speak). This patch is against source forge cvs 12July2005, at approximately 0900 EDT. CHANGELOG: * Patch by Travis B. Sawyer, 12 Jul 2005: Add Sandburst Metrobox and Sandburst Karef board support packages. Second serial port on 440GX now defined as a system device. Add 'Short Etch' code for Cicada PHY within 440gx_enet.c Best regards, Travis Sawyer

2 1

[U-Boot-Users] PATCH: Add Sandburst board support packages [2/2]
by Travis B. Sawyer 15 Aug '05

15 Aug '05

Patch to add me as the maintainer for the Sandburst Metrobox and Karef boards. CHANGELOG: * Patch by Travis B. Sawyer, 12Jul2005: Update Maintainers file for Metrobox and karef boards. Best Regards, Travis Sawyer

2 1

[U-Boot-Users] PATCH: Fix ppc 440 timer freq.
by Travis B. Sawyer 15 Aug '05

15 Aug '05

This patch fixes 440 timer frequency (move from 10ms to 1 ms), as found by Andrew Wozniak. Changelog * Patch by Travis Sawyer, 05 Apr 2005: - Change timer frequency for ppc 440 from 10 ms to 1 ms. Problem found by Andrew Wozniak. Andy, thank you for pointing this out. Best Regards, Travis diff -purN u-boot/cpu/ppc4xx/interrupts.c u-boot_modified/cpu/ppc4xx/interrupts.c --- u-boot/cpu/ppc4xx/interrupts.c 2004-03-14 10:20:56.000000000 -0500 +++ u-boot_modified/cpu/ppc4xx/interrupts.c 2005-04-05 19:56:27.793079640 -0400 @@ -134,7 +134,7 @@ int interrupt_init_cpu (unsigned *decrem mtspr( dec, 0 ); /* Prevent exception after TSR clear*/ mtspr( decar, 0 ); /* clear reload */ mtspr( tsr, 0x08000000 ); /* clear DEC status */ - val = gd->bd->bi_intfreq/100; /* 10 msec */ + val = gd->bd->bi_intfreq/1000; /* 1 msec */ mtspr( decar, val ); /* Set auto-reload value */ mtspr( dec, val ); /* Set inital val */ #else

2 1

[U-Boot-Users] MPC8280 USB console
by KokHow Teh 15 Aug '05

15 Aug '05

Hi; I am trying to bring up the USB controller on PQ2FADS-ZU with MPC8280 onboard. I have finished with the initialization and transaction routines but not the ones neccessary for usbtty to work. The u-boot-1.1.2 source tree that I am using is a release version that is definitely not from the top of the CVS. I notice that the usbtty is only implemented for the SX1 board in drivers/usbdcore_omap1510.c. Is omap1550 the name of the usb controller in arm925t core of the card? Some questions pertaining to USB requirements for usbtty to work. Sorry if this is more of usb-related rather than u-boot related. (1) The USB connector on PQ2FADS-ZU is a Type-A connector. Would this work as a console port? (2) What type of usb connections is neccessary for usbtty to work? I mean, is host PC running usb-host or usb-function and PQ2FADS-ZU running usb-host or usb-function? (3) What type of cable should I use? I assume a Type-A-to-Type-A PC-to-PC USB cable would work? How about a USB2.0 Link cable? www.usbcable.com Thanks for any input. Regards, TEH

3 2