Re: [U-Boot] U-Boot 2009.11.1 USB Issue and Building U-Boot 2013.07
Dear Chuck Wical, On 09/03/2013 10:53 PM, Chuck Wical wrote: First I am fairly new to U-Boot but over the last 2 weeks I have been going through the README files and anything else I can find that would help resolve the issue I have. Here is a recap: Currently the project I am working on was setup with U-Boot 2009-11-01 and works just fine with one exception. I was asked to find a solution where our field support engineers could recover if a firmware update failed causing our board to no longer boot. Basically it cycles through RomBOOT and U-Boot. As I looked through the environment variables and commands I came across the USB subsystem and found I could use fatload. With our system there are three files I need to load from USB, these are uImage, etc.jff2 and rootfs.ext2.gz.uboot. you could also use fatload on mmc. Do you have some mmc in your device? I found if I used tftp these files transferred correctly and the board would boot with the new files. I thought the solution was found and I could simply setup the same files using USB through environment variables. The script worked but the problem was when it tried to load rootfs into RAM it would cause a CPU reset and RomBOOT to start. At first I thought there was something wrong with the script so I tried to load the file by typing it the command but got the same result. I tested the 2009.11.1 release on my 9263ek here and can confirm, that the usb support there is really buggy. It doesn't support current storage devices, seems to behave differently every time I access the device (timeouts, ...). I managed however to load a 16MiB file via usb storage successfully. Command: usb start fatload usb 0 $(loadaddr) rootfs.ext2.gz.uboot where loadaddr is the same address used by tftp. That's in general correct. My first question is, is there a solution for this issue using U-Boot 2009.11.1? This version builds currently within our project. As these are my first steps with 2009.11.1 and usb storage I can't say it. You could backport current usb stack to have better support. On the other hand porting your board forward isn't that hard. Second question is I downloaded U-Boot 2013.07 but noticed huge change in the build process. I figured out the patches I need along with the AT91 configuration for our board. We are using the arm926ej6 processor with a board similar to at91sam9260ek. When I try to build I get the hardware.h:49:3 error: #error Unsupported AT91 processor message. When I HAve a look at 9260ek config, it is still in current releases and builds at least. I rarely test the built on real hardware, at the moment I only have an sam9263ek handy. look at the header file I see where it fails but I don't understand why since I do have a matching define. For some reason hardware.h is not seeing this define and I am stumped as to why. So any suggestions on how to solve or figure this out would be appreciated. If you plan to integrate your patches into mainline, we could help to adopt them where needed. Best regards Andreas Bießmann ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-Boot 2009.11.1 USB Issue and Building U-Boot 2013.07
Hello Andreas, Thanks for the reply! Dear Chuck Wical, On 09/03/2013 10:53 PM, Chuck Wical wrote: First I am fairly new to U-Boot but over the last 2 weeks I have been going through the README files and anything else I can find that would help resolve the issue I have. Here is a recap: Currently the project I am working on was setup with U-Boot 2009-11-01 and works just fine with one exception. I was asked to find a solution where our field support engineers could recover if a firmware update failed causing our board to no longer boot. Basically it cycles through RomBOOT and U-Boot. As I looked through the environment variables and commands I came across the USB subsystem and found I could use fatload. With our system there are three files I need to load from USB, these are uImage, etc.jff2 and rootfs.ext2.gz.uboot. you could also use fatload on mmc. Do you have some mmc in your device? We do have mmc slots available on the board but U-Boot is not configured to use mmc. I don't know why that is as it would have made perfect sense to do so. In the meantime, I am trying to figure out how to enable mmc but running into a little difficulty. To put it simply, I just do not know where to enable it or where to look. I will keep trying but a little guidance would be very much appreciated. I found if I used tftp these files transferred correctly and the board would boot with the new files. I thought the solution was found and I could simply setup the same files using USB through environment variables. The script worked but the problem was when it tried to load rootfs into RAM it would cause a CPU reset and RomBOOT to start. At first I thought there was something wrong with the script so I tried to load the file by typing it the command but got the same result. I tested the 2009.11.1 release on my 9263ek here and can confirm, that the usb support there is really buggy. It doesn't support current storage devices, seems to behave differently every time I access the device (timeouts, ...). I managed however to load a 16MiB file via usb storage successfully. The size of file I am trying to load is 7MiB but with your comments above it makes me wonder if a timeout is occurring thus forcing the reboot. Command: usb start fatload usb 0 $(loadaddr) rootfs.ext2.gz.uboot where loadaddr is the same address used by tftp. That's in general correct. My first question is, is there a solution for this issue using U-Boot 2009.11.1? This version builds currently within our project. As these are my first steps with 2009.11.1 and usb storage I can't say it. You could backport current usb stack to have better support. On the other hand porting your board forward isn't that hard. Second question is I downloaded U-Boot 2013.07 but noticed huge change in the build process. I figured out the patches I need along with the AT91 configuration for our board. We are using the arm926ej6 processor with a board similar to at91sam9260ek. When I try to build I get the hardware.h:49:3 error: #error Unsupported AT91 processor message. When I HAve a look at 9260ek config, it is still in current releases and builds at least. I rarely test the built on real hardware, at the moment I only have an sam9263ek handy. I will take a look and yes, we are using real hardware and I do not have access to a sam9263ek either. look at the header file I see where it fails but I don't understand why since I do have a matching define. For some reason hardware.h is not seeing this define and I am stumped as to why. So any suggestions on how to solve or figure this out would be appreciated. If you plan to integrate your patches into mainline, we could help to adopt them where needed. I have no plans to incorporate the patches into mainline as they seem very specific to our board and configuration. Best regards Andreas Bießmann Cheers Chuck Wical ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-Boot 2009.11.1 USB Issue and Building U-Boot 2013.07
Dear Chuck Wical usb start fatload usb 0 $(loadaddr) rootfs.ext2.gz.uboot where loadaddr is the same address used by tftp. Your load address 0 is wrong. On AT91 systems addresses greater than 0x2010 should be used (RAM location). Regards jens ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-Boot 2009.11.1 USB Issue and Building U-Boot 2013.07
Dear Chuck, please always keep the mailing list on Cc: And please don't top post / full quote. Thanks. In message 005001cea968$9eaa58e0$dbff0aa0$@amanomcgann.com you wrote: Thank you for the reply! Yes the same loadaddr is used for both tftp and fatload as follows: loadaddr=0x2100 OK. I'm not sure what you mean by a complete console log so a little direction would be helpful so I can provide what you are asking for. I Please copy all input and all output of your system into a file and include this with your posting. For example, you coul use the script command, or your terminal emulator may have a logging feature, or you could simply use copy paste. can tell you when I run the commands manually I get the same result each time. I have attached a txt file that shows what happens when I run the command. At the bottom of the file I included the environment variables. If you look at the variable usbgetrootfs this is the command being run. I cannot see any such attachment. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de When the bosses talk about improving productivity, they are never talking about themselves. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-Boot 2009.11.1 USB Issue and Building U-Boot 2013.07
Wolfgang, please always keep the mailing list on Cc: My apologies but in my line of work I have to be careful about reply all so there are times I hit reply automatically. And please don't top post / full quote. Thanks. Again, my apologies since I keep all emails in thread form here at work for reference. I will do my best to not top post on these forms. I cannot see any such attachment. I failed to attached the file. It is now attached. It is just a copy paste but yes, GtkTerm does have a method to save the screen. It's probably easier to just copy and paste. And before anything is said about what is used for a console it simply works the best for my application. Chuck Wical Embedded Software Engineer Amano McGann, Inc. 651 Taft Street, NE Minneapolis, MN 55413 Tel: 612-331-2020 Fax: 612-331-5187 chuck.wi...@amanomcgann.com loadaddr=0x2100 U-Boot usb start (Re)start USB... USB: scanning bus for devices... 2 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found U-Boot usb info 1: Hub, USB Revision 1.10 - OHCI Root Hub - Class: Hub - PacketSize: 8 Configurations: 1 - Vendor: 0x Product 0x Version 0.0 Configuration: 1 - Interfaces: 1 Self Powered 0mA Interface: 0 - Alternate Setting 0, Endpoints: 1 - Class Hub - Endpoint 1 In Interrupt MaxPacket 2 Interval 255ms 2: Mass Storage, USB Revision 2.0 - USB Flash Disk 9D785E10 - Class: (from Interface) Mass Storage - PacketSize: 64 Configurations: 1 - Vendor: 0x058f Product 0x6387 Version 1.2 Configuration: 1 - Interfaces: 1 Bus Powered 100mA Interface: 0 - Alternate Setting 0, Endpoints: 2 - Class Mass Storage, Transp. SCSI, Bulk only - Endpoint 1 Out Bulk MaxPacket 64 - Endpoint 2 In Bulk MaxPacket 64 U-Boot usb storage Device 0: Vendor: USB Rev: 8.07 Prod: Flash Disk Type: Removable Hard Disk Capacity: 241.0 MB = 0.2 GB (493568 x 512) U-Boot fatload usb 0 $(loadaddr) rootfs.ext2.gz.uboot reading rootfs.ext2.gz.uboot ..RomBOOT U-Boot 2009.11.1 (Aug 27 2013 - 13:43:57) DRAM: 64 MB NAND: 256 MiB In:serial Out: serial Err: serial Net: macb0 macb0: Starting autonegotiation... macb0: Autonegotiation complete macb0: link up, 100Mbps full-duplex (lpa: 0x45e1) Hit any key to stop autoboot: 0 U-Boot Environment Variables autoload=no\0 \ console=quiet\0 \ dbgconsole=console=ttyS0,115200\0 \ ethaddr=00:01:02:03:04:05\0 \ loadaddr=0x2100\0 \ ramdiskaddr=0x2140\0 \ ubootaddr=0x2\0 \ ubootsize=0xE\0 \ kerneladdr=0x10\0 \ kernelsize=0x40\0 \ etcaddr=0x50\0 \ etcsize=0x10\0 \ rootfsaddr=0x60\0 \ rootfssize=0x100\0 \ nandload=nand read.jffs2 $(loadaddr) $(kerneladdr) $(kernelsize); nand read.jffs2 $(ramdiskaddr) $(rootfsaddr) $(rootfssize)\0 \ flashuboot=tftp $(loadaddr) u-boot.bin; nand erase $(ubootaddr) $(ubootsize); nand write.jffs2 $(loadaddr) $(ubootaddr) $(ubootsize)\0 \ flashkernel=tftp $(loadaddr) uImage; nand erase $(kerneladdr) $(kernelsize); nand write.jffs2 $(loadaddr) $(kerneladdr) $(kernelsize)\0 \ flashetc=tftp $(loadaddr) etc.jffs2; nand erase $(etcaddr) $(etcsize); nand write.jffs2 $(loadaddr) $(etcaddr) $(etcsize)\0 \ flashrootfs=tftp $(loadaddr) rootfs.ext2.gz.uboot; nand erase $(rootfsaddr) $(rootfssize); nand write.jffs2 $(loadaddr) $(rootfsaddr) $(rootfssize)\0 \ flashall=run flashkernel; run flashetc; run flashrootfs\0 \ usbgetkernel=fatload usb 0 $(loadaddr) uImage\0 \ usbkernel= nand erase $(kerneladdr) $(kernelsize); nand write.jffs2 $(loadaddr) $(kerneladdr) $(kernelsize)\0 \ usbgetetc=fatload usb 0 $(loadaddr) etc.jffs2\0 \ usbetc=nand erase $(etcaddr) $(etcsize); nand write.jffs2 $(loadaddr) $(etcaddr) $(etcsize)\0 \ usbgetrootfs=fatload usb 0 $(loadaddr) rootfs.ext2.gz.uboot\0 \ usbrootfs=nand erase $(rootfsaddr) $(rootfssize); nand write.jffs2 $(loadaddr) $(rootfsaddr) $(rootfssize)\0 \ usbflash=run usbgetkernel usbkernel usbgetetc usbetc usbgetrootfs usbrootfs\0 \ memboot=bootm $(loadaddr) $(ramdiskaddr)\0___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] U-Boot 2009.11.1 USB Issue and Building U-Boot 2013.07
First I am fairly new to U-Boot but over the last 2 weeks I have been going through the README files and anything else I can find that would help resolve the issue I have. Here is a recap: Currently the project I am working on was setup with U-Boot 2009-11-01 and works just fine with one exception. I was asked to find a solution where our field support engineers could recover if a firmware update failed causing our board to no longer boot. Basically it cycles through RomBOOT and U-Boot. As I looked through the environment variables and commands I came across the USB subsystem and found I could use fatload. With our system there are three files I need to load from USB, these are uImage, etc.jff2 and rootfs.ext2.gz.uboot. I found if I used tftp these files transferred correctly and the board would boot with the new files. I thought the solution was found and I could simply setup the same files using USB through environment variables. The script worked but the problem was when it tried to load rootfs into RAM it would cause a CPU reset and RomBOOT to start. At first I thought there was something wrong with the script so I tried to load the file by typing it the command but got the same result. Command: usb start fatload usb 0 $(loadaddr) rootfs.ext2.gz.uboot where loadaddr is the same address used by tftp. My first question is, is there a solution for this issue using U-Boot 2009.11.1? This version builds currently within our project. Second question is I downloaded U-Boot 2013.07 but noticed huge change in the build process. I figured out the patches I need along with the AT91 configuration for our board. We are using the arm926ej6 processor with a board similar to at91sam9260ek. When I try to build I get the hardware.h:49:3 error: #error Unsupported AT91 processor message. When I look at the header file I see where it fails but I don't understand why since I do have a matching define. For some reason hardware.h is not seeing this define and I am stumped as to why. So any suggestions on how to solve or figure this out would be appreciated. Thanks! Chuck ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-Boot 2009.11.1 USB Issue and Building U-Boot 2013.07
Dear Chuck, In message 002b01cea8e7$b14fc5b0$13ef5110$@amanomcgann.com you wrote: I found if I used tftp these files transferred correctly and the board would boot with the new files. I thought the solution was found and I could simply setup the same files using USB through environment variables. The script worked but the problem was when it tried to load rootfs into RAM it would cause a CPU reset and RomBOOT to start. At first I thought there was something wrong with the script so I tried to load the file by typing it the command but got the same result. Are you using the same load address in RAM with both the tftp and the fatload commands? Can you provide a complete console log of both the working and the crashing cases? Command: usb start fatload usb 0 $(loadaddr) rootfs.ext2.gz.uboot where loadaddr is the same address used by tftp. Please show the complete commands, and all output. My first question is, is there a solution for this issue using U-Boot 2009.11.1? This version builds currently within our project. We need to understand the problem beforeanybody could answer that... Second question is I downloaded U-Boot 2013.07 but noticed huge change in the build process. I figured out the patches I need along with the AT91 configuration for our board. We are using the arm926ej6 processor with a board similar to at91sam9260ek. When I try to build I get the hardware.h:49:3 error: #error Unsupported AT91 processor message. When I look at the header file I see where it fails but I don't understand why since I do have a matching define. For some reason hardware.h is not seeing this define and I am stumped as to why. So any suggestions on how to solve or figure this out would be appreciated. Well, 2009.11 is indeed extremely old. With such an out-of-tree port you are essentially lost. Adapting the old patches to current mainline is more or less the same effort as starting from scratch (and probably even more so). Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de Crash programs fail because they are based on the theory that, with nine women pregnant, you can get a baby a month. - Wernher von Braun ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
