-- ======================================================================== Yuli Barcohen | Phone +972-9-765-1788 | Software Project Leader yuli@arabellasw.com | Fax +972-9-765-7494 | Arabella Software, Israel ======================================================================== --__--__-- Message: 3 Date: Wed, 17 Nov 2004 21:14:31 +0800 From: Rodel Miguel rodelfmiguel@gmail.com Reply-To: Rodel Miguel rodelfmiguel@gmail.com To: u-boot-users@lists.sourceforge.net Subject: [U-Boot-Users] UART Initialization Problem (ns16550 on arm920t) Hi, I am porting u-boot 1.1.1 on a new board. The board is arm920t based and it's UART port is compatible with ns16550.c so I changed the serial driver (serial.c) on the cpu/arm920t directory with the serial driver + ns16650 module available in the drivers directory. I am using bdi2k for debugging and I have initialized the UART port on the bdi2k config. The problem is that when the initialization routine in armboot_start calls serial_init of the ns16550, there are no messages, i.e. no prompt, on my serial console. When I remove the serial_init on the list of initialization functions of armboot_start, a prompt appears. I can successfully type help, and do other stuff. Whenever I try to remove the initialization routine on my BDI2k configuration and put back the serial_init function on the initialization list, I am not getting any messages on my serial console. What could be the cause of this problem? The initialization routine on the bdi2k and serial_init are almost the same (i tried to make the sequence and the values exactly the same but I get the same result) but there are no messages displayed on my console. =( Thank you very much for your help. Best Regards, Rodel Miguel --__--__-- Message: 4 To: omkar.pandit@softdel.com Cc: "U-Boot" u-boot-users@lists.sourceforge.net From: Wolfgang Denk wd@denx.de Subject: Re: [U-Boot-Users] U-Boot for CSB226 Date: Wed, 17 Nov 2004 15:07:06 +0100 In message MKEKJHBADLJFOFFEPDGIGEOLCFAA.omkar.pandit@softdel.com you wrote: > > I have a few queries. Please RTFM before posting. > 1. I want to put U-Boot-1.1.1 on CSB226 board in RAM and use it as a > boot loader for Linux. I do not want to erase the original > micromonitor code in Flash, so I need to put the U-Boot in RAM using > TFTP of micromonitor. What changes should I make to the configration > file of CSB226 to make this possible. This is a FAQ; please see http://www.denx.de/twiki/bin/view/DULG/CanUBootBeConfiguredSuchThatItCanBeSt artedInRAM Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de : ... and it's got weird formatting - Notepad, Write, Works 3 can't : decipher it, and it's too big to go in DOS Edit. Help! Install an operating system. :-) -- Tom Christiansen --__--__-- Message: 5 To: Matej Kupljen matej.kupljen@ultra.si Cc: U-Boot u-boot-users@lists.sourceforge.net From: Wolfgang Denk wd@denx.de Subject: Re: [U-Boot-Users] U-Boot for CSB226 Date: Wed, 17 Nov 2004 15:44:23 +0100 In message 1100701734.2357.28.camel@mbmatejdebian.ultra.si you wrote: > > > This is a FAQ; please see > > http://www.denx.de/twiki/bin/view/DULG/CanUBootBeConfiguredSuchThatI > > tCanBeStartedInRAM > > Just one comment, maybe: The FAQ tries to answer FAQ's, obviously, and thus must be a bit generic. ... > 5) set the breakpoint at that address in the terminal connected to > the BDI2000: > # rm 15 <address_of_fucntion> > (You can also use the mon command in the gdb console) > 6) Select connect target in the Insight menu > 7) Now set the breakpoints as you wish and debug the target downloaded > to the RAM. First, this may work fior you, but it will not work for me. It does not work on PowerPC, and it does not work on MIPS for example. And it does not work if you have configured your BDI200 as recommended, i. e. that it works with a mostly virgin CPU. > Of course this assumes, that your BDI configuration file has setup > memory controller correctly and you can access the RAM. > > Any comments? Yes, This is one of the many things you can do if you know what you are doing. If you don't have a clue it will just cause more problems and questions. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de A day without sunshine is like night. --__--__-- Message: 6 From: "flab" zsuly@hotmail.com To: u-boot-users@lists.sourceforge.net Date: Thu, 18 Nov 2004 00:00:06 +0800 Subject: [U-Boot-Users] sdram byte ordinary erron after relocation Hello everyone, I am porting U-Boot to my ppc850 board, and my program crashes after relocation to ram. I used an SDRAM driver which works normally in VxWorks. But when I call the relocate_code() funtion, there is an error of byte ordinary. If I write a number to memory, the higher 16 bits exchange position with lower 16 bits. For an example, if I write 0x2705,1956 to sdram, then I get 0x1956,2705 when I read the memory address. But I can read or write flash correctly. I read chapter 13.2.3 of the guild file. There is an argument related to my problem. >Argument: >But my board ran fine with bootloader XYZ and/or operating system ABC. >Answer: >Double-check your configuration that you claim runs properly... >Are you sure the SDRAM is initialized using the same init sequence and values? >Are you sure the memory controlling registers are set the same? Are you >sure your other configuration uses caches and/or DMA? If it doesn't, it isn't a valid comparison. I checked these issues, and I am sure that the init sequence and memory controlling registers are as same as the VxWorks'. But also, BDI2000 can read or write memory exactly with same init sequence. The only difference is my VxWorks system didn't use DMA function. At first, I am doubltful of wrong endian mode. Then I checked correlated register. MSR register is 0x1002 and DC_CST register is 0. I think it should be right. This problem puzzled me so much, and any clue given to me will be apreciated! Best regards, Kenny Lew --__--__-- Message: 7 Date: Wed, 17 Nov 2004 20:02:39 +0100 From: Massimiliano Cialdi cialdi@firenze.net To: u-boot-users@lists.sourceforge.net Organization: starfleet Subject: [U-Boot-Users] get_timer documentation We use coldfire 5282 We need to know what is the parameter and return value of get_timer() we wnat to use get_timer() to calculate time intervals in millisecond. something like: .... a = get_timer(0); /* do something */ b = get_timer(0); .... in this case what is the measure unit of b-a? How can I obtain millisicends? thanks -- Massimiliano Cialdi cialdi@firenze.net m.cialdi@oksys.it --__--__-- Message: 8 To: Massimiliano Cialdi cialdi@firenze.net Cc: u-boot-users@lists.sourceforge.net From: Wolfgang Denk wd@denx.de Subject: Re: [U-Boot-Users] get_timer documentation Date: Wed, 17 Nov 2004 21:19:16 +0100 In message 20041117200239.2c48dc54.cialdi@firenze.net you wrote: > We use coldfire 5282 > > We need to know what is the parameter and return value of get_timer() Maybe having a short look in the source code brings some ideas? > we wnat to use get_timer() to calculate time intervals in millisecond. Yea, that's what it's intended for. > something like: > > .... > a = get_timer(0); > /* do something */ > b = get_timer(0); > .... > > in this case what is the measure unit of b-a? milliseconds. And why not simply: a = get_timer(0); /* do something */ millisecs = get_timer(a); ??? > How can I obtain millisicends? I don't know. What's a sicend? Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de An expert is a person who avoids the small errors while sweeping on to the grand fallacy. --__--__-- _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users End of U-Boot-Users Digest