Re: [U-Boot] reloacting uboot
On Tuesday 25 August 2009 02:11:36 pm Wolfgang Denk wrote: Dear E Robertson, In message 200908251403.20809.e.robertson@gmail.com you wrote: I am using the at91sam9263 device from which the bootstrap code load u-boot to the desired ram address. However, I would like to re-relocate this at the different address based on memory availability. Can / or should this be done? Yes, it can be done, and it should be done. The fact that we don't do it so far is due to the fact that the guys who did the original ARM code found this too complicated (even though they had a working example in the PowerPC code) and not worth the effort. We're suffering since from this misconception. But there is no reason why you would have to copy the code again - just copy it to the correct address right from the beginning, like we do in PowerPC. I don't follow: Yes, but no reason to do so? On the 9263, it's copied once to ram at boot. Are you saying their is no reason to copy it again? If so, yes, in most cases that would be true but I would like to move it again after that initial relocation. Since I've already specified my start address, I wasn't sure about. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] reloacting uboot
Hi All, I am using the at91sam9263 device from which the bootstrap code load u-boot to the desired ram address. However, I would like to re-relocate this at the different address based on memory availability. Can / or should this be done? ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] reloacting uboot
On Tuesday 25 August 2009 02:11:36 pm Wolfgang Denk wrote: Dear E Robertson, In message 200908251403.20809.e.robertson@gmail.com you wrote: I am using the at91sam9263 device from which the bootstrap code load u-boot to the desired ram address. However, I would like to re-relocate this at the different address based on memory availability. Can / or should this be done? Yes, it can be done, and it should be done. The fact that we don't do it so far is due to the fact that the guys who did the original ARM code found this too complicated (even though they had a working example in the PowerPC code) and not worth the effort. We're suffering since from this misconception. But there is no reason why you would have to copy the code again - just copy it to the correct address right from the beginning, like we do in PowerPC. By the way, my reason for doing this is that i want to maintain a proportional memory space available so if I increase the ram size I would like to relocate the boot loader without doing a separate build. Make sense? ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] nand read
Hi, Does mtd has to be enabled/setup for nand read to work? I'm trying to do a I keep getting a read error when trying to read even the first block. NAND read: device 0 offset 0x0, size 0x2 NAND read from offset 0 failed -74 131072 bytes read: ERROR ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] nand read
Spoken too quickly user error. On Thu, Aug 20, 2009 at 11:13 AM, E Robertsone.robertson@gmail.com wrote: Hi, Does mtd has to be enabled/setup for nand read to work? I'm trying to do a I keep getting a read error when trying to read even the first block. NAND read: device 0 offset 0x0, size 0x2 NAND read from offset 0 failed -74 131072 bytes read: ERROR ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] u-boot yaffs2 usage question
Is their a suggestion for the list where this question should be asked, if not here? Thanks. On Sun, Jul 26, 2009 at 10:25 AM, E Robertsone.robertson@gmail.com wrote: Hi All, First, I've never used this filesystem before so excuse my ignorance. I've added support in uboot but it seems to be failing at mount. The default mount point according to the source is /flash. Does that mean that I have to have a /flash directory in my filesystem? if I try other mount (namely /) it doesn't seem to like that either. I've got jffs2 to work file with the same arrangement. I've created a yffs2 filesystem on a nand device (nand0 ) using mtd where the first 80M I made yafs2. I also created several directories including /flash but it did not mount that either. Some errors are below: I've added a few extra printfs to see where I'm going. yls yaffs_StartUp Version 2: 2.6.17 NAME: NULL (NAND 256MiB 3,3V 8-bit), Yffs2? 1 , blocks 2048 yaffs_initialise yaffs: Mounting /flash yaffsfs_FindDevice yaffs: Could not allocate Tnodes Error mounting /flash, return value: -12 yaffsfs_FindDevice opendir failed ymount / yaffs_StartUp Version 2: 2.6.17 NAME: NULL, Yffs2? 1 , blocks 2048 yaffs_initialise yaffs: Mounting / yaffsfs_FindDevice Error mounting /, return value: -19 mtdparts ---mtdparts_init--- last_ids : nand0=nand0 env_ids : nand0=nand0 last_parts: mtdparts=nand0:819...@0(NK),-(DATA) env_parts : mtdparts=nand0:819...@0(NK),-(DATA) last_partition : nand0,0 env_partition : nand0,0 ---list_partitions--- device nand0 nand0, # parts = 2 #: name size offset mask_flags 0: NK 0x0500 0x 0 1: DATA 0x0b00 0x0500 0 --- mtd_part_info: partition number 0 for device nand0 (nand0) active partition: nand0,0 - (NK) 0x0500 @ 0x defaults: mtdids : nand0=nand0 mtdparts: mtdparts=nand0:819...@0(NK),-(DATA) ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] u-boot yaffs2 usage question
Hi All, First, I've never used this filesystem before so excuse my ignorance. I've added support in uboot but it seems to be failing at mount. The default mount point according to the source is /flash. Does that mean that I have to have a /flash directory in my filesystem? if I try other mount (namely /) it doesn't seem to like that either. I've got jffs2 to work file with the same arrangement. I've created a yffs2 filesystem on a nand device (nand0 ) using mtd where the first 80M I made yafs2. I also created several directories including /flash but it did not mount that either. Some errors are below: I've added a few extra printfs to see where I'm going. yls yaffs_StartUp Version 2: 2.6.17 NAME: NULL (NAND 256MiB 3,3V 8-bit), Yffs2? 1 , blocks 2048 yaffs_initialise yaffs: Mounting /flash yaffsfs_FindDevice yaffs: Could not allocate Tnodes Error mounting /flash, return value: -12 yaffsfs_FindDevice opendir failed ymount / yaffs_StartUp Version 2: 2.6.17 NAME: NULL, Yffs2? 1 , blocks 2048 yaffs_initialise yaffs: Mounting / yaffsfs_FindDevice Error mounting /, return value: -19 mtdparts ---mtdparts_init--- last_ids : nand0=nand0 env_ids : nand0=nand0 last_parts: mtdparts=nand0:819...@0(NK),-(DATA) env_parts : mtdparts=nand0:819...@0(NK),-(DATA) last_partition : nand0,0 env_partition : nand0,0 ---list_partitions--- device nand0 nand0, # parts = 2 #: namesizeoffset mask_flags 0: NK 0x0500 0x 0 1: DATA0x0b00 0x0500 0 --- mtd_part_info: partition number 0 for device nand0 (nand0) active partition: nand0,0 - (NK) 0x0500 @ 0x defaults: mtdids : nand0=nand0 mtdparts: mtdparts=nand0:819...@0(NK),-(DATA) ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] unable to see jffs2 partition
Hi all, I've been trying unsuccessfully to see my jffs2 partition I've created by the mtdtools under linux. If their a known issue with this? Is their a size limit? Maybe the way it's created? I do not have a problem with this partition from linux but also never looked at it from the u-boot. I can change partitions but ls shows partition is empty when their are files. ... #define CONFIG_CMD_JFFS21 /** JFFS2 Support */ #define CONFIG_CMD_MTDPARTS 1 #define CONFIG_JFFS2_CMDLINE1 #undef CONFIG_CMD_FLASH #define CONFIG_JFFS2_NAND 1 #define CONFIG_JFFS2_DEVnand0 #define CONFIG_JFFS2_PART_OFFSET0x0 #define CONFIG_JFFS2_PART_SIZE 0x500 #define MTDPARTS_DEFAULTmtdparts=nand:80M(IMGS),-(DATA) #define MTDIDS_DEFAULT nand0=nand ... Thanks, E! ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] unable to see jffs2 partition
On Thursday 23 July 2009 04:57:19 pm E Robertson wrote: Hi all, I've been trying unsuccessfully to see my jffs2 partition I've created by the mtdtools under linux. If their a known issue with this? Is their a size limit? Maybe the way it's created? I do not have a problem with this partition from linux but also never looked at it from the u-boot. I can change partitions but ls shows partition is empty when their are files. ... #define CONFIG_CMD_JFFS21 /** JFFS2 Support */ #define CONFIG_CMD_MTDPARTS 1 #define CONFIG_JFFS2_CMDLINE1 #undef CONFIG_CMD_FLASH #define CONFIG_JFFS2_NAND 1 #define CONFIG_JFFS2_DEVnand0 #define CONFIG_JFFS2_PART_OFFSET0x0 #define CONFIG_JFFS2_PART_SIZE 0x500 #define MTDPARTS_DEFAULTmtdparts=nand:80M(IMGS),-(DATA) #define MTDIDS_DEFAULT nand0=nand ... Thanks, E! Forget to add I'm using 03.09 git source on SAM9263 SoC. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] loading via jtag
On Thursday 02 July 2009 03:57:38 pm Frank Svendsbøe wrote: On Thu, Jul 2, 2009 at 3:32 PM, E Robertsone.robertson@gmail.com wrote: On Thursday 02 July 2009 02:22:16 am Frank Svendsbøe wrote: On Thu, Jul 2, 2009 at 6:10 AM, E Robertsone.robertson@gmail.com wrote: Hi All, Has anyone used the JTAG like the BDI2000 to load u-boot onto a at91sam9263? I've done it on other boards but some some reason the code will not execute from on board SDRAM. To avoid initializing the external memory via jtag, I use the bootstrap code to do the setup then load u-boot and run it. For reason(s) I haven't figured out yet, the code will not external memory. Has anyone done this before and can provide some help? Thanks. How come you want to execute it from RAM? Is the board without flash? Could you instead replace the bootstrap loader with U-Boot? It the SDRAM controller is already setup, I guess you must recode U-Boot and tell it not to touch/re-initialize the memory controller... Btw, look at http://www.denx.de/wiki/view/DULG/CanUBootBeConfiguredSuchThatItCanBeSta rte dInRAM - Frank In this case, I believe things are a bit different. U-boot is not relocated because the bootstrap already does this and the bootstrap does all the init needed to set up ram (among other things). I'm tracking a problem which is why I'm trying to run it from ram. I've done quite a bit of modifications to the point where I believe this should work, but apparently I may have overlooked something. Ok. The BDI makes it possible to debug U-Boot so that you can pinpoint where the problem occur. Have you tried that yet, and what exactly is the problem you observe? Try to be more specific, then some of the Gurus here may be able to help you. Good luck! - Frank Thanks. I finally figured out what the problem is. I have s signal integrity problem on my SDRAM bus. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] loading via jtag
On Thursday 02 July 2009 02:22:16 am Frank Svendsbøe wrote: On Thu, Jul 2, 2009 at 6:10 AM, E Robertsone.robertson@gmail.com wrote: Hi All, Has anyone used the JTAG like the BDI2000 to load u-boot onto a at91sam9263? I've done it on other boards but some some reason the code will not execute from on board SDRAM. To avoid initializing the external memory via jtag, I use the bootstrap code to do the setup then load u-boot and run it. For reason(s) I haven't figured out yet, the code will not external memory. Has anyone done this before and can provide some help? Thanks. How come you want to execute it from RAM? Is the board without flash? Could you instead replace the bootstrap loader with U-Boot? It the SDRAM controller is already setup, I guess you must recode U-Boot and tell it not to touch/re-initialize the memory controller... Btw, look at http://www.denx.de/wiki/view/DULG/CanUBootBeConfiguredSuchThatItCanBeStarte dInRAM - Frank In this case, I believe things are a bit different. U-boot is not relocated because the bootstrap already does this and the bootstrap does all the init needed to set up ram (among other things). I'm tracking a problem which is why I'm trying to run it from ram. I've done quite a bit of modifications to the point where I believe this should work, but apparently I may have overlooked something. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] loading via jtag
Hi All, Has anyone used the JTAG like the BDI2000 to load u-boot onto a at91sam9263? I've done it on other boards but some some reason the code will not execute from on board SDRAM. To avoid initializing the external memory via jtag, I use the bootstrap code to do the setup then load u-boot and run it. For reason(s) I haven't figured out yet, the code will not external memory. Has anyone done this before and can provide some help? Thanks. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] udelay/udelay_masked problems
Hi all, Is their a problem using udelay in board_init functions? When I do this on my at91, arm926ejs board, it seems to be in an endless loop. I thought this was a timer issue but I only have this problem with board init and not in the drivers. Does anyone have any ideas? Is timer_init a arch specific call or should it be board specific for arm? ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] CONFIG_SERVERIP
Hi all, In the current git source, I have the serverip config set but tftp complains about serverip not being set. I didn't see any changes to the source here. Am I missing something? printenv baudrate=115200 ipaddr=192.168.0.200 serverip=192.168.0.100 gatewayip=192.168.0.1 netmask=255.255.255.0 hostname=Vincy ethaddr=00:07:A6:00:6A:E6 bootdelay=5 bootargs= bootcmd= ethact=macb0 Environment size: 247/16380 bytes OmniTouch tftp link up, 100Mbps full-duplex (lpa: 0x41e1) *** ERROR: `serverip' not set ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] At91 mass storage device
On Thu, Mar 12, 2009 at 5:50 PM, Remy Bohmer li...@bohmer.net wrote: Hello, Please don't top post. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? (see http://www.netmeister.org/news/learn2quote.html) I'm aware of the top post irritant, nonetheless I employ some discretion on short emails. Don't worry, I wouldn't repeat it :). 2009/3/12 E Robertson e.robertson@gmail.com: I'm using git source from a few weeks back, sometime early part of last month. Have those changes merged or are they somewhere else? Okay, you are quite up-to-date, so you are not using an ancient version :-), it worked in versions like 2008.10 (if PLLB is configured properly, bootstrap code did it wrong, see also cpu/arm926ejs/at91/usb.c of git), maybe there is some regression here. Unfortunately I do not have the hardware so I cannot verify it, or debug it... Besides, there are still USB sticks that do not work at all, have you tried a different stick already? Strange, in the logging I see that it only seems to communicate with the roothub only, it never communicates to the device at all, so my first guess would be the PLLB not running, but that was repaired somewhere early this year in a recent git... Maybe you can verify if it is running and all peripheral clocks are available? I revisit these and it looked like my UHP power wasn't enabled. I thought I did this in the Bootstrap code but apparently not: at91_sys_write(AT91_PMC_PCER, (1 AT91SAM9263_ID_PIOA) | (1AT91SAM9263_ID_UHP)); /* Enable VBus on UHP ports */ at91_set_gpio_output(AT91_PIN_PA21, 1); at91_set_gpio_output(AT91_PIN_PA24, 1); One thing I never understood is that after a power cycle with a usb memory stick plugged in, I always have to start and restart the usb probe to recognize the storage device. This happened in a previous version of u-boot (like 1.2.0) and it's also the case with the current source. Is their a reason for that? Perhaps an inadequate peripheral reset? ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] At91 mass storage device
On Fri, Mar 13, 2009 at 11:19 AM, E Robertson e.robertson@gmail.com wrote: On Thu, Mar 12, 2009 at 5:50 PM, Remy Bohmer li...@bohmer.net wrote: ... One thing I never understood is that after a power cycle with a usb memory stick plugged in, I always have to start and restart the usb probe to recognize the storage device. This happened in a previous version of u-boot (like 1.2.0) and it's also the case with the current source. Is their a reason for that? Perhaps an inadequate peripheral reset? I decided to do some digging and I see the not responding error reported below. I added a wait of 2ms to the *dl_reverse_done_list(ohci_t *ohci) loop. I'm not sure how this affects everything else. However, although I did not get the no response error, I did get the STALL PID error. (Re)start USB... USB: INFO: aligned ghcca 27f79c00 scanning bus for devices... INFO: submit_control_msg INFO: Root-Hub: adr: 0 cmd(8): 0680 0100 0040 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0500 0001 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0680 0100 0012 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0680 0200 0009 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0680 0200 0019 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0900 0001 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0680 0300 00ff INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0680 0301 0409 00ff INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 06a0 2900 0004 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 06a0 2900 0009 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 00a0 0004 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0323 0008 0001 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0323 0008 0002 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 00a3 0001 0004 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 00a3 0001 0004 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0123 0010 0001 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0323 0004 0001 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 00a3 0001 0004 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0123 0014 0001 INFO: submit_control_msg ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0123 0001 0001 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 00a3 0002 0004 2 USB Device(s) found scanning bus for storage devices... i=0 i=1 i=2 0 Storage Device(s) found usb start (Re)start USB... USB: INFO: aligned ghcca 27f79c00 scanning bus for devices... INFO: submit_control_msg INFO: Root-Hub: adr: 0 cmd(8): 0680 0100 0040 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0500 0001 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0680 0100 0012 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0680 0200 0009 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0680 0200 0019 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0900 0001 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0680 0300 00ff INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0680 0301 0409 00ff INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 06a0 2900 0004 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 06a0 2900 0009 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 00a0 0004 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0323 0008 0001 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0323 0008 0002 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 00a3 0001 0004 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 00a3 0001 0004 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0123 0010 0001 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0323 0004 0001 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 00a3 0001 0004 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0123 0014 0001 INFO: submit_control_msg INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0323 0004 0001 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 00a3 0001 0004 INFO: submit_control_msg INFO: Root-Hub: adr: 1 cmd(8): 0123 0014 0001 INFO: submit_control_msg INFO: submit_control_msg INFO: submit_control_msg INFO: submit_control_msg INFO: submit_control_msg INFO: submit_control_msg
[U-Boot] At91 mass storage device
Hi, I've got a problem recognizing a USB mass storage device on the at91sam9263ek. I'm not familiar with this interface and I'm hoping someone might be able to shed some light on it. I enable debug hoping something might catch my eyes but so far nothing. At one point I was unable to reset the port; DEBUG: roothub.a: 02001202 POTPGT=2 NOCP NPS NDP=2 DEBUG: roothub.b: PPCM= DR= DEBUG: roothub.status: DEBUG: roothub.portstatus [0] = 0x00120301 PRSC PESC LSDA PPS CCS DEBUG: roothub.portstatus [1] = 0x0100 PPS DEBUG: RET(rh) URB:[ bfd] dev: 1,ep: 0-I,type:CTRL,len:0/4 stat:0x0 cannot reset port 1!? However, most of the time I get the results below. Does anyone have any ideas? INFO: submit_control_msg DEBUG: SUB URB:[ 23f] dev: 1,ep: 0-O,type:CTRL,len:0/0 stat:0x8000 DEBUG: SUB(rh) URB:[ 245] dev: 1,ep: 0-O,type:CTRL,len:0/0 stat:0x8000 INFO: Root-Hub: adr: 1 cmd(8): 0323 0008 0001 INFO: WR:portstatus[0]0x100 DEBUG: roothub.a: 02001202 POTPGT=2 NOCP NPS NDP=2 DEBUG: roothub.b: PPCM= DR= DEBUG: roothub.status: DEBUG: roothub.portstatus [0] = 0x0100 PPS DEBUG: roothub.portstatus [1] = 0x0100 PPS DEBUG: RET(rh) URB:[ 2b7] dev: 1,ep: 0-O,type:CTRL,len:0/0 stat:0x0 INFO: submit_control_msg DEBUG: SUB URB:[ 2c2] dev: 1,ep: 0-O,type:CTRL,len:0/0 stat:0x8000 DEBUG: SUB(rh) URB:[ 2c9] dev: 1,ep: 0-O,type:CTRL,len:0/0 stat:0x8000 INFO: Root-Hub: adr: 1 cmd(8): 0323 0008 0002 INFO: WR:portstatus[1]0x100 DEBUG: roothub.a: 02001202 POTPGT=2 NOCP NPS NDP=2 DEBUG: roothub.b: PPCM= DR= DEBUG: roothub.status: DEBUG: roothub.portstatus [0] = 0x0100 PPS DEBUG: roothub.portstatus [1] = 0x0100 PPS DEBUG: RET(rh) URB:[ 33b] dev: 1,ep: 0-O,type:CTRL,len:0/0 stat:0x0 INFO: submit_control_msg DEBUG: SUB URB:[ 346] dev: 1,ep: 0-I,type:CTRL,len:0/4 stat:0x8000 DEBUG: SUB(rh) URB:[ 34c] dev: 1,ep: 0-I,type:CTRL,len:0/4 stat:0x8000 INFO: Root-Hub: adr: 1 cmd(8): 00a3 0001 0004 DEBUG: roothub.a: 02001202 POTPGT=2 NOCP NPS NDP=2 DEBUG: roothub.b: PPCM= DR= DEBUG: roothub.status: DEBUG: roothub.portstatus [0] = 0x0100 PPS DEBUG: roothub.portstatus [1] = 0x0100 PPS DEBUG: RET(rh) URB:[ 36b] dev: 1,ep: 0-I,type:CTRL,len:0/4 stat:0x0 INFO: submit_control_msg DEBUG: SUB URB:[ 373] dev: 1,ep: 0-I,type:CTRL,len:0/4 stat:0x8000 DEBUG: SUB(rh) URB:[ 379] dev: 1,ep: 0-I,type:CTRL,len:0/4 stat:0x8000 INFO: Root-Hub: adr: 1 cmd(8): 00a3 0002 0004 DEBUG: roothub.a: 02001202 POTPGT=2 NOCP NPS NDP=2 DEBUG: roothub.b: PPCM= DR= DEBUG: roothub.status: DEBUG: roothub.portstatus [0] = 0x0100 PPS DEBUG: roothub.portstatus [1] = 0x0100 PPS DEBUG: RET(rh) URB:[ 398] dev: 1,ep: 0-I,type:CTRL,len:0/4 stat:0x0 1 USB Device(s) found scanning bus for storage devices... i=0 i=1 0 Storage Device(s) found ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] At91 mass storage device
I'm using git source from a few weeks back, sometime early part of last month. Have those changes merged or are they somewhere else? On Thu, Mar 12, 2009 at 3:49 PM, Remy Bohmer li...@bohmer.net wrote: Hello, I've got a problem recognizing a USB mass storage device on the at91sam9263ek. I'm not familiar with this interface and I'm hoping someone might be able to shed some light on it. I enable debug hoping something might catch my eyes but so far nothing. At one point I was unable to reset the port; What version of U-boot are you using? There has been changes the last U-boot releases in this area to get it working, even on 9263ek. As far as I know, the latest releases should work properly. Kind Regards, Remy ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] sprintf side effect, a bug?
On Monday 26 January 2009 04:30:36 pm Wolfgang Denk wrote:
Dear E Robertson,
In message 200901261453.10434.e.robertson@gmail.com you wrote:
It seems that sprintf() is modifying at least two bytes from the source
and I have duplicate this with different varibles.
For instance, I have a mac address defined as unsigned char [6]:
Doing the following sets the environment variable correctly, however
bytes [0] and [1], are modified at the source.
sprintf(env_ethaddr,%02X:%02X:%02X:%02X:%02X:%02X, MACAddress[0],
MACAddress[1],
MACAddress[2], MACAddress[3],
MACAddress[4], MACAddress[5]);
Has anyone noticed this before?
I don't think the machine matters but I am building for an arm at91.
Hmm... I think I wouldbe surprised. What exactly does your test code
look like?
I tried this one:
...
unsigned char buf[128];
unsigned char a[6] = { 0x11, 0x22, 0x33, 0x44, 0x55, 0x66, };
int i;
...
printf (Before: ); for (i=0; i6; ++i) printf ( %02X,a[i]); putc
('\n'); sprintf (buf, %02X:%02X:%02X:%02X:%02X:%02X, a[0], a[1], a[2],
a[3], a[4], a[5]); printf (After: ); for (i=0; i6; ++i) printf (
%02X,a[i]); putc ('\n'); printf (buf=\%s\\n, buf);
...
And this is what I got:
Before: 11 22 33 44 55 66
After: 11 22 33 44 55 66
buf=11:22:33:44:55:66
Hi,
I did the following:
memcpy (gd-bd-bi_enetaddr, MACAddress, sizeof(gd-bd-bi_enetaddr));
memcpy (dupMACAddress, MACAddress, sizeof(dupMACAddress));
printf(Before %02X:%02X:%02X:%02X:%02X:%02X\n,dupMACAddress[0],
dupMACAddress[1],
dupMACAddress[2], dupMACAddress[3],
dupMACAddress[4], dupMACAddress[5]);
sprintf(env_ethaddr,%02X:%02X:%02X:%02X:%02X:%02X,dupMACAddress[0],
dupMACAddress[1],
dupMACAddress[2], dupMACAddress[3],
dupMACAddress[4], dupMACAddress[5]);
printf(After %02X:%02X:%02X:%02X:%02X:%02X\n,dupMACAddress[0],
dupMACAddress[1],
dupMACAddress[2], dupMACAddress[3],
dupMACAddress[4], dupMACAddress[5]);
printf(ethaddr %02X:%02X:%02X:%02X:%02X:%02X\n,gd-bd-bi_enetaddr[0],
gd-bd-bi_enetaddr[1],
gd-bd-bi_enetaddr[2], gd-bd-bi_enetaddr[3],
gd-bd-bi_enetaddr[4], gd-bd-bi_enetaddr[5]);
and I got this:
Before 00:04:A6:00:6A:E6
After 36:00:A6:00:6A:E6
ethaddr 00:04:A6:00:6A:E6
Alse env_ethaddr has the correct correct.
I make a duplicate before did the sprintf.
I'm also on v 1.3.4 and haven't tried it on the latest git.
Looks sane to me...
Best regards,
Wolfgang Denk
signature.asc
Description: This is a digitally signed message part.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] sprintf side effect, a bug?
Hi, It seems that sprintf() is modifying at least two bytes from the source and I have duplicate this with different varibles. For instance, I have a mac address defined as unsigned char [6]: Doing the following sets the environment variable correctly, however bytes [0] and [1], are modified at the source. sprintf(env_ethaddr,%02X:%02X:%02X:%02X:%02X:%02X, MACAddress[0], MACAddress[1], MACAddress[2], MACAddress[3], MACAddress[4], MACAddress[5]); Has anyone noticed this before? I don't think the machine matters but I am building for an arm at91. signature.asc Description: This is a digitally signed message part. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] SAM9263 TWI inquiry
Hi All, As far as I can tell, their are no i2c hardware driver support for the at91sam9263 TWI. Are their any known problems with this interface? Thanks. signature.asc Description: This is a digitally signed message part. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
