[U-Boot] AT91RM9200 boots from NOR Flash or not
I want to use the u-boot-1.3.4 with the patch from AT91 for my custom board based on AT91RM9200 with 32MB SDRAM (MT48LC8M16A2) and 8MB flash (AT49BV6416-70TI). I am directly flashing the image to flash location at 0x1000 (beginning of the flash). But I am not able to see anything on my debug port. I want to know if I am doing something wrong. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] AT91RM9200 boots from NOR Flash or not
I am using JTAG port with SAM-ICE. Regards Raj Nikumbh From: Drasko DRASKOVIC [mailto:drasko.drasko...@gmail.com] Sent: Friday, February 19, 2010 5:41 PM To: Nikumbh, Raj (IE10) Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] AT91RM9200 boots from NOR Flash or not On Fri, Feb 19, 2010 at 11:30 AM, Nikumbh, Raj (IE10) wrote: I want to use the u-boot-1.3.4 with the patch from AT91 for my custom board based on AT91RM9200 with 32MB SDRAM (MT48LC8M16A2) and 8MB flash (AT49BV6416-70TI). I am directly flashing the image to flash location at 0x1000 (beginning of the flash). But I am not able to see anything on my debug port. Which debug port? ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] AT91RM9200 boots from NOR Flash or not
Yeah I did pull it down at the startup. And I meant the same DBGU pins. Regards Raj Nikumbh From: Maxim Podbereznyi [mailto:lisar...@gmail.com] Sent: Friday, February 19, 2010 7:41 PM To: Nikumbh, Raj (IE10) Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] AT91RM9200 boots from NOR Flash or not Did you pull BMS pin to GND? Do you mean DBGU pins by "debug port"? 2010/2/19 Nikumbh, Raj (IE10) I want to use the u-boot-1.3.4 with the patch from AT91 for my custom board based on AT91RM9200 with 32MB SDRAM (MT48LC8M16A2) and 8MB flash (AT49BV6416-70TI). I am directly flashing the image to flash location at 0x1000 (beginning of the flash). But I am not able to see anything on my debug port. I want to know if I am doing something wrong. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] AT91RM9200 boots from NOR Flash or not
Hi, I have compiled u-boot-latest with ELDK 4.1 for AT91RM9200EK board (as I have kept the memory configurations and crystals similar to the board).I am getting something on the hyper terminal now. My hyperterminal configuration 115200-8-N-1 Given below is the snapshot as it comes. U B-oo t02900. 8F(be2 20201- 1 :1041:)5 I2C: ready DRAM: !!BM Please let me know if somebody faced a similar situation or any pointers to get out of this problem. Regards Raj Nikumbh -Original Message- From: Eric Bénard [mailto:e...@eukrea.com] Sent: Saturday, February 20, 2010 6:52 PM To: Nikumbh, Raj (IE10) Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] AT91RM9200 boots from NOR Flash or not Hi, Le 20/02/2010 08:25, Maxim Podbereznyi a écrit : > OK, then can you explain what software do you flash? Does rm9200 u-boot > setup PLL? Because if it is not then you will never see anything at DBGU > pins. Another problem can be with your RC filters for PLL. Did you use the > same quartz as in the Atmel design? If not then you must calculate RC > filters and change them on your board. > > BTW, if your SDRAM does not work then u-boot will never start :) > > 2010/2/19 Nikumbh, Raj (IE10) > >> Yeah I did pull it down at the startup. And I meant the same DBGU pins. >> the board support in board/eukrea/cpuat91 was working fine last time I tested it and this board is close to your configuration (AT91RM9200 + NOR Flash 16bits width) so maybe you can try it (you may just need to update SDRAM geometry and timings and SMC timings for your NOR flash). Eric ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Support for SMSC Phy LAN8700C
I would like to know if there is any version of u-boot that supports SMSC PHY LAN8700C. I have interfaced it with AT91RM9200 (MII interface). If u-boot supports then I will go over to that particular version. Regards Raj Nikumbh ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] trying to bring linux-2.6.32.3 from RAM?
The load address actually doesn't matter. You can tftp your uImage anywhere in RAM and then just give a bootm command. It will get the kernel and booting would happen fine. Though as I see in your bootargs you don't define a filesystem so kernel might hang there. Anyways you should be able to boot the kernel. Hope this helps. -Original Message- From: u-boot-boun...@lists.denx.de [mailto:u-boot-boun...@lists.denx.de] On Behalf Of ogara Sent: Thursday, April 29, 2010 2:49 AM To: u-boot@lists.denx.de Subject: Re: [U-Boot] trying to bring linux-2.6.32.3 from RAM? I understand your point. My memory alignment was off. So now I get: ## Booting kernel from Legacy Image at ... Image Name: Linux-2.6.32.3 Created: 2010-04-28 18:44:34 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size:3131956 Bytes = 3 MB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK ERROR: can't get kernel image! As I said before this file works of hard drive no problem (I just did binary comparison and file matches). Rick Ball wrote: > > Yes, but I think you need to load at address 0 instead of 0x8000, just > like I load at 0x8000 instead of 0x80008000. My kernel is also > compiled to start at an offset of 0x8000, just like yours, but I think the > image has 0x8000 of reserved space at the beginning (so you load it to 0, > but it starts executing at 0x8000). > > I don't think the bootargs are even coming into play - you're executing a > bad instruction at 0x8008 because you loaded the kernel at 0x8000 instead > of 0 (so you're trying to execute the uninitialized reserved space). > > Try changing your tftp command to load at 0 instead of 0x8000, and I think > it should boot. > > Rick > > -Original Message- > From: u-boot-boun...@lists.denx.de [mailto:u-boot-boun...@lists.denx.de] > On Behalf Of ogara > Sent: Wednesday, April 28, 2010 3:26 PM > To: u-boot@lists.denx.de > Subject: Re: [U-Boot] trying to bring linux-2.6.32.3 from RAM? > > > Rick, > I have custom board with DRAM starting at 0x - 0x2000 so I > could not load it to 0x8000 since I do not have that much memory. I > noticed in your report that the load address is 0x8000 but the kernel > image was built with: > Load Address: 80008000 > Entry Point: 80008000. > I was wondering what does your bootm command line looks like and if yours > bootargs look like mine? > Ogi > > > Rick Ball wrote: >> >> I think you want to load the kernel to memory at 0x, even >> though the u-boot load address is set to 0x8000 - my kernel, which I >> load to memory at 0x8000 because that's where my SDRAM is, looks like >> this: >> >> Load address: 0x8000 >> Loading: >> # >> >> # >> >> # >> >> # >> >> # >> >> # >> ## >> done >> Bytes transferred = 2128612 (207ae4 hex) ## Booting kernel from Legacy >> Image at 8000 ... >>Image Name: Linux-2.6.29-rc3-omap1 >>Image Type: ARM Linux Kernel Image (uncompressed) >>Data Size:2128548 Bytes = 2 MB >>Load Address: 80008000 >>Entry Point: 80008000 >>Verifying Checksum ... OK >>Loading Kernel Image ... OK >> OK >> >> Starting kernel ... >> >> Uncompressing >> Linux... >> done, booting the kernel. >> >> >> Rick >> >> -Original Message- >> From: u-boot-boun...@lists.denx.de >> [mailto:u-boot-boun...@lists.denx.de] >> On Behalf Of Marek Vasut >> Sent: Wednesday, April 28, 2010 2:35 PM >> To: u-boot@lists.denx.de >> Cc: ogara >> Subject: Re: [U-Boot] trying to bring linux-2.6.32.3 from RAM? >> >> Dne St 28. dubna 2010 20:50:35 ogara napsal(a): >>> Hi All, >>> I am trying to bring linux from RAM. I have compiled the kernel and >>> created uImage. I bring the image over tftp into the memory and then >>> execute bootm memaddress. Unfortunately here is the output from my >>> command line: >>> >>> tftp 0x8000 ipaddress:uImage >>> Using egiga0 device >>> TFTP from server ipaddress; our IP address is ipaddress; sending >>> through gateway ipaddress Filename 'uImage'. >>> Load address: 0x8000 >>> Loading: >>> # >>> >>> # >>> >>> # >>> ### >>> done >>>
