Re: [U-Boot] Nand flash R/W,saveenv issue..
Dear Manukumar,
Hello,
CCing someone who might actually help you, CCing the uboot mailing list, please keep it that way.
i can able to detect nand flash. but i had an issue that i could not do operation(Read/write) on nand flash. i tried to erase the nand flash i got the error as below:
NAND 32MiB 3,3V 8-bit: MTD Erase failure: -5 NAND 32MiB 3,3V 8-bit: MTD Erase failure: -5 NAND 32MiB 3,3V 8-bit: MTD Erase failure: -5 NAND 32MiB 3,3V 8-bit: MTD Erase failure: -5
even if i try to saveenv then also is not saving the envionment variables
processor used: P1012 nand flash: samsung K9F5608U0D
please reply ASAP.
manukumar signal-networks
Best regards, Marek Vasut
On 05/22/2012 09:15 AM, Marek Vasut wrote:
Dear Manukumar,
Hello,
CCing someone who might actually help you, CCing the uboot mailing list, please keep it that way.
i can able to detect nand flash. but i had an issue that i could not do operation(Read/write) on nand flash. i tried to erase the nand flash i got the error as below:
NAND 32MiB 3,3V 8-bit: MTD Erase failure: -5 NAND 32MiB 3,3V 8-bit: MTD Erase failure: -5 NAND 32MiB 3,3V 8-bit: MTD Erase failure: -5 NAND 32MiB 3,3V 8-bit: MTD Erase failure: -5
even if i try to saveenv then also is not saving the envionment variables
processor used: P1012 nand flash: samsung K9F5608U0D
please reply ASAP.
manukumar signal-networks
What version of U-Boot is this?
How are you configuring BRn/ORn for this chipselect?
Could you define VERBOSE_DEBUG at the top of drivers/mtd/nand/fsl_elbc_nand.c?
-Scott
u-boot version: u-boot-2010.12
My OR and BR register values(according to our memory map): BR0 0xFF800C21 OR0 0xFF800396 BR1 0xE8000801 OR1 0xFFFF8074 BR2 0xE8009001 OR2 0xFFFF8074
after defining VERBOSE_DEBUG in drivers/mtd/nand/fsl_elbc_nand.c i gave sacveenv command, igot below logs. please go through that and resolve asap.
Hit any key to stop autoboot: 0 => saveenv Saving Environment to NAND... Erasing Nand... nand_erase_opts_1 nand_erase_opts_2 erase_length = 3 erase.addr = 0 meminfo->erasesize = 540672 **********************************************************erase_length = 3 erase.addr = 0 meminfo->erasesize = 540672 skipping bad block = 0 DEBUG: set_addr: bank=0, ctrl->addr=0xff800000 (0xff800000), index 0, pes 14 ps 9 fsl_elbc_run_command DEBUG: fsl_elbc_run_command: fmr=0000f023 fir=4e000000 fcr=70000000 DEBUG: fsl_elbc_run_command: fbar=00000000 fpar=00000000 fbcr=00000001 bank=0 DEBUG: fsl_elbc_run_command: stat=40000001 mdr=00000000 fmr=0000f020 Page size = 0 ctrl->status(ctrl->status == LTESR_CC ? 0 : -EIO) = fffffffb DEBUG: fsl_elbc_cmdfunc: NAND_CMD_ERASE1, page_addr: 0x420. DEBUG: set_addr: bank=0, ctrl->addr=0xff800000 (0xff800000), index 0, pes 14 ps 9 DEBUG: fsl_elbc_cmdfunc: NAND_CMD_ERASE2. fsl_elbc_run_command DEBUG: fsl_elbc_run_command: fmr=0000f023 fir=c2500000 fcr=60d00000 DEBUG: fsl_elbc_run_command: fbar=00000021 fpar=00000000 fbcr=00000000 bank=0 DEBUG: fsl_elbc_run_command: stat=00000000 mdr=00000000 fmr=0000f023 Page size = 0 ctrl->status(ctrl->status == LTESR_CC ? 0 : -EIO) = fffffffb ctrl->status= 0 --------------------------------------------------- result = -5
NAND 32MiB 3,3V 8-bit: MTD Erase failure: -5 erase_length = 3 erase.addr = 0 meminfo->erasesize = 557056 skipping bad block = 0 DEBUG: set_addr: bank=0, ctrl->addr=0xff800000 (0xff800000), index 0, pes 14 ps 9 fsl_elbc_run_command DEBUG: fsl_elbc_run_command: fmr=0000f023 fir=4e000000 fcr=70000000 DEBUG: fsl_elbc_run_command: fbar=00000000 fpar=00000000 fbcr=00000001 bank=0 DEBUG: fsl_elbc_run_command: stat=00000000 mdr=00000000 fmr=0000f023 Page size = 0 ctrl->status(ctrl->status == LTESR_CC ? 0 : -EIO) = fffffffb DEBUG: fsl_elbc_cmdfunc: NAND_CMD_ERASE1, page_addr: 0x440. DEBUG: set_addr: bank=0, ctrl->addr=0xff800000 (0xff800000), index 0, pes 14 ps 9 DEBUG: fsl_elbc_cmdfunc: NAND_CMD_ERASE2. fsl_elbc_run_command DEBUG: fsl_elbc_run_command: fmr=0000f023 fir=c2500000 fcr=60d00000 DEBUG: fsl_elbc_run_command: fbar=00000022 fpar=00000000 fbcr=00000000 bank=0 DEBUG: fsl_elbc_run_command: stat=40000001 mdr=00000000 fmr=0000f020 Page size = 0 ctrl->status(ctrl->status == LTESR_CC ? 0 : -EIO) = fffffffb ctrl->status= 40000001 --------------------------------------------------- result = -5
NAND 32MiB 3,3V 8-bit: MTD Erase failure: -5 erase_length = 3 erase.addr = 0 meminfo->erasesize = 573440 skipping bad block = 0 DEBUG: set_addr: bank=0, ctrl->addr=0xff800000 (0xff800000), index 0, pes 14 ps 9 fsl_elbc_run_command DEBUG: fsl_elbc_run_command: fmr=0000f023 fir=4e000000 fcr=70000000 DEBUG: fsl_elbc_run_command: fbar=00000000 fpar=00000000 fbcr=00000001 bank=0 DEBUG: fsl_elbc_run_command: stat=00000000 mdr=00000000 fmr=0000f023 Page size = 0 ctrl->status(ctrl->status == LTESR_CC ? 0 : -EIO) = fffffffb DEBUG: fsl_elbc_cmdfunc: NAND_CMD_ERASE1, page_addr: 0x460. DEBUG: set_addr: bank=0, ctrl->addr=0xff800000 (0xff800000), index 0, pes 14 ps 9 DEBUG: fsl_elbc_cmdfunc: NAND_CMD_ERASE2. fsl_elbc_run_command DEBUG: fsl_elbc_run_command: fmr=0000f023 fir=c2500000 fcr=60d00000 DEBUG: fsl_elbc_run_command: fbar=00000023 fpar=00000000 fbcr=00000000 bank=0 DEBUG: fsl_elbc_run_command: stat=40000001 mdr=00000000 fmr=0000f023 Page size = 0 ctrl->status(ctrl->status == LTESR_CC ? 0 : -EIO) = fffffffb ctrl->status= 40000001 --------------------------------------------------- result = -5
NAND 32MiB 3,3V 8-bit: MTD Erase failure: -5 nand_erase_opts_3
Writing to Nand... nand_write DEBUG: set_addr: bank=0, ctrl->addr=0xff800000 (0xff800000), index 0, pes 14 ps 9 fsl_elbc_run_command DEBUG: fsl_elbc_run_command: fmr=0000f023 fir=4e000000 fcr=70000000 DEBUG: fsl_elbc_run_command: fbar=00000000 fpar=00000000 fbcr=00000001 bank=0 DEBUG: fsl_elbc_run_command: stat=00000000 mdr=00000000 fmr=0000f023 Page size = 0 ctrl->status(ctrl->status == LTESR_CC ? 0 : -EIO) = fffffffb DEBUG: fsl_elbc_cmdfunc: NAND_CMD_SEQIN/PAGE_PROG, page_addr: 0x420, column: 0x0. DEBUG: set_addr: bank=0, ctrl->addr=0xff800000 (0xff800000), index 0, pes 14 ps 9 DEBUG: fsl_elbc_cmdfunc: NAND_CMD_PAGEPROG writing 528 bytes. fsl_elbc_run_command DEBUG: fsl_elbc_run_command: fmr=0000f023 fir=c6128d00 fcr=00108000 DEBUG: fsl_elbc_run_command: fbar=00000021 fpar=00000000 fbcr=00000000 bank=0 DEBUG: fsl_elbc_run_command: stat=40000001 mdr=00000000 fmr=0000f020 Page size = 0 ctrl->status(ctrl->status == LTESR_CC ? 0 : -EIO) = fffffffb DEBUG: set_addr: bank=7, ctrl->addr=0xff801c00 (0xff800000), index 206, pes 14 ps 9 fsl_elbc_run_command DEBUG: fsl_elbc_run_command: fmr=0000f023 fir=c12e0000 fcr=50000000 DEBUG: fsl_elbc_run_command: fbar=00ffffff fpar=00007e06 fbcr=00000003 bank=0 DEBUG: fsl_elbc_run_command: stat=00000000 mdr=00000000 fmr=0000f023 Page size = 0 ctrl->status(ctrl->status == LTESR_CC ? 0 : -EIO) = fffffffb ctrl->status= 0 FAILED!
I am expecting your response at earliest.
manukumar signal-networks
On Tue, 2012-05-22 at 12:56 -0500, Scott Wood wrote:
On 05/22/2012 09:15 AM, Marek Vasut wrote:
Dear Manukumar,
Hello,
CCing someone who might actually help you, CCing the uboot mailing list, please keep it that way.
i can able to detect nand flash. but i had an issue that i could not do operation(Read/write) on nand flash. i tried to erase the nand flash i got the error as below:
NAND 32MiB 3,3V 8-bit: MTD Erase failure: -5 NAND 32MiB 3,3V 8-bit: MTD Erase failure: -5 NAND 32MiB 3,3V 8-bit: MTD Erase failure: -5 NAND 32MiB 3,3V 8-bit: MTD Erase failure: -5
even if i try to saveenv then also is not saving the envionment variables
processor used: P1012 nand flash: samsung K9F5608U0D
please reply ASAP.
manukumar signal-networks
What version of U-Boot is this?
How are you configuring BRn/ORn for this chipselect?
Could you define VERBOSE_DEBUG at the top of drivers/mtd/nand/fsl_elbc_nand.c?
-Scott
Dear Manukumar,
In message 1337752596.2378.37.camel@Manukumar you wrote:
u-boot version: u-boot-2010.12
This is ancient code. Please update and use current code, then try again.
Best regards,
Wolfgang Denk
Hello, when we get rference board(P1020RDB) we got the u-boot-2010.12 source. by using above source we have modified according to custom boards requirement. can you please provide the link to get updated u-boot source that support P1012 with nand flash samsung(K95608U0D) or please provide me the patch...
manukumar signal-networks
On Wed, 2012-05-23 at 10:02 +0200, Wolfgang Denk wrote:
Dear Manukumar,
In message 1337752596.2378.37.camel@Manukumar you wrote:
u-boot version: u-boot-2010.12
This is ancient code. Please update and use current code, then try again.
Best regards,
Wolfgang Denk
On 05/23/2012 03:30 AM, Manukumar wrote:
Hello, when we get rference board(P1020RDB) we got the u-boot-2010.12 source.
That board is supported by current mainline U-Boot as well -- no patch needed.
by using above source we have modified according to custom boards requirement. can you please provide the link to get updated u-boot source that support P1012 with nand flash samsung(K95608U0D) or please provide me the patch...
git.denx.de, or ftp://ftp.denx.de/pub/u-boot/u-boot-latest.tar.bz2
-Scott
hello, I was able to solve nand erase and nand write and saveenv. Now,I am making kernel up and followed below steps..
1) tf 1000000 uImage_icm_v1.1 nand erase 0x00200000 361483 nand write 1000000 0x00200000 361483
2) tf c00000 p1021rdb_32b.dtb nand erase 0x00100000 3000 nand write c00000 0x00100000 3000
3) tf 2000000 mini.rootfs.ext2.gz.uboot nand erase 0x00600000 2115d4 nand write 2000000 0x00600000 2115d4
then to boot kernel from nand i used bootm 0x00200000 0x00600000 0x00100000
it is giving below log message. 2168276 bytes written: OK => bootm 0x00200000 0x00600000 0x00100000 WARNING: adjusting available memory to 30000000 Wrong Image Format for bootm command ERROR: can't get kernel image!
and also my next question is cp.b 1000000 0x00200000 100000 not working it is showing log as:
=> cp.b 1000000 0x00200000 100000 Copy to Flash... Flash not Erased
why this is happenning please give me the solution for this.
manukumar signal-networks
On Wed, 2012-05-23 at 11:16 -0500, Scott Wood wrote:
On 05/23/2012 03:30 AM, Manukumar wrote:
Hello, when we get rference board(P1020RDB) we got the u-boot-2010.12 source.
That board is supported by current mainline U-Boot as well -- no patch needed.
by using above source we have modified according to custom boards requirement. can you please provide the link to get updated u-boot source that support P1012 with nand flash samsung(K95608U0D) or please provide me the patch...
git.denx.de, or ftp://ftp.denx.de/pub/u-boot/u-boot-latest.tar.bz2
-Scott
On 05/30/2012 12:02 AM, Manukumar wrote:
hello, I was able to solve nand erase and nand write and saveenv. Now,I am making kernel up and followed below steps..
tf 1000000 uImage_icm_v1.1 nand erase 0x00200000 361483 nand write 1000000 0x00200000 361483
tf c00000 p1021rdb_32b.dtb nand erase 0x00100000 3000 nand write c00000 0x00100000 3000
tf 2000000 mini.rootfs.ext2.gz.uboot nand erase 0x00600000 2115d4 nand write 2000000 0x00600000 2115d4
then to boot kernel from nand i used bootm 0x00200000 0x00600000 0x00100000
Bootm takes a RAM address, not a NAND address. Unlike NOR flash, NAND is not directly addressable. You need to use "nand read" first.
-Scott
thanks scott.
i loaded my u-boot image to nand flash its fine. and also I need my kernel image and rootfs also in nand flash so that my system should make kernel UP using nand flash. how can i do this using nand flash as we are using only nand flash as boot device.
manukumar siganl-networks
On Wed, 2012-05-30 at 11:18 -0500, Scott Wood wrote:
On 05/30/2012 12:02 AM, Manukumar wrote:
hello, I was able to solve nand erase and nand write and saveenv. Now,I am making kernel up and followed below steps..
tf 1000000 uImage_icm_v1.1 nand erase 0x00200000 361483 nand write 1000000 0x00200000 361483
tf c00000 p1021rdb_32b.dtb nand erase 0x00100000 3000 nand write c00000 0x00100000 3000
tf 2000000 mini.rootfs.ext2.gz.uboot nand erase 0x00600000 2115d4 nand write 2000000 0x00600000 2115d4
then to boot kernel from nand i used bootm 0x00200000 0x00600000 0x00100000
Bootm takes a RAM address, not a NAND address. Unlike NOR flash, NAND is not directly addressable. You need to use "nand read" first.
-Scott
On 05/30/2012 11:15 PM, Manukumar wrote:
thanks scott.
i loaded my u-boot image to nand flash its fine. and also I need my kernel image and rootfs also in nand flash so that my system should make kernel UP using nand flash. how can i do this using nand flash as we are using only nand flash as boot device.
Again, you need to use "nand read" to move the images from NAND to RAM before booting.
-Scott
Thanks scott..
manukumar signal-networks
On Thu, 2012-05-31 at 11:21 -0500, Scott Wood wrote:
Wolfgang Denk wd@denx.de, Marek Vasut marex@denx.de, joe.hershberger@ni.com, sr@denx.de, u-boot@lists.denx.de,
Hello scott.
I can able make the kernel up but it hangs after probing serial driver as shown below:
It has to boot further but its not happenig.. I have attached the file i should get the log as this i also mentioned where it hangs...
what may be the problem with this how could i fix this issue.
manukumar signal-networks
On Thu, 2012-05-31 at 11:21 -0500, Scott Wood wrote:
On 05/30/2012 11:15 PM, Manukumar wrote:
thanks scott.
i loaded my u-boot image to nand flash its fine. and also I need my kernel image and rootfs also in nand flash so that my system should make kernel UP using nand flash. how can i do this using nand flash as we are using only nand flash as boot device.
Again, you need to use "nand read" to move the images from NAND to RAM before booting.
-Scott
On 06/01/2012 05:10 AM, Manukumar wrote:
Hello scott.
I can able make the kernel up but it hangs after probing serial driver as shown below:
It has to boot further but its not happenig.. I have attached the file i should get the log as this i also mentioned where it hangs...
what may be the problem with this how could i fix this issue.
This is getting off topic for the U-Boot list. Plus, it looks like you're using a Freescale-provided kernel. Please e-mail support@freescale.com, or try the latest upstream kernel and get help from linuxppc-dev@lists.ozlabs.org.
But in this case, since this is your custom board, and it works on the evaluation board, this is something you'll need to debug yourself (or hire someone to debug).
Given the place where it hangs, the obvious suggestion is to make sure the baud rate and serial input clock are correct.
-Scott
Hello scott,
The issue is solved by making baud rate correction. thank you
manukumar signal-networks
On Fri, 2012-06-01 at 12:15 -0500, Scott Wood wrote:
On 06/01/2012 05:10 AM, Manukumar wrote:
Hello scott.
I can able make the kernel up but it hangs after probing serial driver as shown below:
It has to boot further but its not happenig.. I have attached the file i should get the log as this i also mentioned where it hangs...
what may be the problem with this how could i fix this issue.
This is getting off topic for the U-Boot list. Plus, it looks like you're using a Freescale-provided kernel. Please e-mail support@freescale.com, or try the latest upstream kernel and get help from linuxppc-dev@lists.ozlabs.org.
But in this case, since this is your custom board, and it works on the evaluation board, this is something you'll need to debug yourself (or hire someone to debug).
Given the place where it hangs, the obvious suggestion is to make sure the baud rate and serial input clock are correct.
-Scott
Hello,
I have connected USB hard disk to P1020RB and in command prompt(u-boot) i used command => usb start (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 3 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found
=> usb dev
USB device 0: Vendor: Seagate Rev: 0130 Prod: Portable Type: Hard Disk Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
and USB got detected.
but If i used the same command in our custom board => usb start (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 1 USB Device(s) found scanning bus for storage devices... 0 Storage Device(s) found
=> usb dev
USB device -1: device type unknown
How do resolve this issue and why the device is not detecting my USB hard disk.?
manukumar signal-networks
Hi Manukumar,
On Thu, 05 Jul 2012 15:57:49 +0530, Manukumar manukumar@signal-networks.com wrote:
Hello,
I have connected USB hard disk to P1020RB
Which board is this? Neither "git grep -i P1020RB" nor "find . iname '*P1020RB*'" yield any result.
and in command prompt(u-boot) i used command => usb start (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 3 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found
=> usb dev
USB device 0: Vendor: Seagate Rev: 0130 Prod: Portable Type: Hard Disk Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
and USB got detected.
but If i used the same command in our custom board => usb start (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 1 USB Device(s) found scanning bus for storage devices... 0 Storage Device(s) found
=> usb dev
USB device -1: device type unknown
How do resolve this issue and why the device is not detecting my USB hard disk.?
Considering that you're trying this on a custom board, and assuming "P1020RB" is a nickname for a board supported in mainline U-Boot, there are two possibilities:
1) the custom board uses exactly the same U-Boot (source, configuration and binaries) as P1020RB, and the issue is in HW, in which case we can barely help;
2) the custom board uses a custom U-Boot, and we can barely help too, as this issue is not about (recent) mainline U-Boot code.
manukumar signal-networks
Amicalement,
Dear Albert ARIBAUD,
Hi Manukumar,
On Thu, 05 Jul 2012 15:57:49 +0530, Manukumar
manukumar@signal-networks.com wrote:
Hello,
I have connected USB hard disk to P1020RB
Which board is this? Neither "git grep -i P1020RB" nor "find . iname '*P1020RB*'" yield any result.
Ain't it P1020RDB?
and in command prompt(u-boot) i used command => usb start (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found=> usb dev
USB device 0: Vendor: Seagate Rev: 0130 Prod: Portable
Type: Hard Disk Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)and USB got detected.
but If i used the same command in our custom board => usb start (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 1 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found=> usb dev
USB device -1: device type unknown
How do resolve this issue and why the device is not detecting my USB hard disk.?
This happens with mainline u-boot, right? Can you try older version of uboot and then git bisect to find the offending change please?
Considering that you're trying this on a custom board, and assuming "P1020RB" is a nickname for a board supported in mainline U-Boot, there are two possibilities:
- the custom board uses exactly the same U-Boot (source, configuration
and binaries) as P1020RB, and the issue is in HW, in which case we can barely help;
- the custom board uses a custom U-Boot, and we can barely help too,
as this issue is not about (recent) mainline U-Boot code.
manukumar signal-networks
Amicalement,
Best regards, Marek Vasut
hello I checked with the hardware spec in that P1020RDB: having connection like P1012processor -> PHY -> HUB -> ports
whereas in custom board P1012processor -> phy -> port(single usb port)
In uboot source code initializing sequence of u-boot is below: 1.usb_init() 2.usb_scan_devices() 3.usb_new_device(dev) 4.usb_hub_probe(dev, 0) 5.usb_hub_configure(dev)
how can we do this in u-boot source code
manukumar signal-networks
On Thu, 2012-07-05 at 13:45 +0200, Albert ARIBAUD wrote:
Hi Manukumar,
On Thu, 05 Jul 2012 15:57:49 +0530, Manukumar manukumar@signal-networks.com wrote:
Hello,
I have connected USB hard disk to P1020RB
Which board is this? Neither "git grep -i P1020RB" nor "find . iname '*P1020RB*'" yield any result.
and in command prompt(u-boot) i used command => usb start (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 3 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found
=> usb dev
USB device 0: Vendor: Seagate Rev: 0130 Prod: Portable Type: Hard Disk Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
and USB got detected.
but If i used the same command in our custom board => usb start (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 1 USB Device(s) found scanning bus for storage devices... 0 Storage Device(s) found
=> usb dev
USB device -1: device type unknown
How do resolve this issue and why the device is not detecting my USB hard disk.?
Considering that you're trying this on a custom board, and assuming "P1020RB" is a nickname for a board supported in mainline U-Boot, there are two possibilities:
- the custom board uses exactly the same U-Boot (source, configuration
and binaries) as P1020RB, and the issue is in HW, in which case we can barely help;
- the custom board uses a custom U-Boot, and we can barely help too,
as this issue is not about (recent) mainline U-Boot code.
manukumar signal-networks
Amicalement,
Hi Manukumar,
On Mon, 09 Jul 2012 14:17:49 +0530, Manukumar manukumar@signal-networks.com wrote:
hello I checked with the hardware spec in that P1020RDB: having connection like P1012processor -> PHY -> HUB -> ports
whereas in custom board P1012processor -> phy -> port(single usb port)
In uboot source code initializing sequence of u-boot is below: 1.usb_init() 2.usb_scan_devices() 3.usb_new_device(dev) 4.usb_hub_probe(dev, 0) 5.usb_hub_configure(dev)
how can we do this in u-boot source code
I am not a USB specialist, but it seems like it is the first time ever that U-Boot meets a board where the core's USB port is mapped directly to a device without passing through a hub. Is this design compliant with the USB standards?
Anyway, you seem to have nailed the (USB) root cause, so the course of action is obvious even if its compliance with standards is not: you need to make usb hub probing and configuration optional and enabled by default, and to disable this option for your custom board.
manukumar signal-networks
Amicalement,
Dear Manukumar,
hello I checked with the hardware spec in that P1020RDB: having connection like P1012processor -> PHY -> HUB -> ports
whereas in custom board P1012processor -> phy -> port(single usb port)
This is fairy normal.
In uboot source code initializing sequence of u-boot is below: 1.usb_init() 2.usb_scan_devices() 3.usb_new_device(dev) 4.usb_hub_probe(dev, 0) 5.usb_hub_configure(dev)
how can we do this in u-boot source code
But I don't see what you're asking about.
manukumar signal-networks
[...]
Best regards, Marek Vasut
Hello,
I resolved u-boot issues in u-boot level but i am facing an issue in kernel level usb detection can any suggest me to resolve this issue.
manukumar signal-networks
On Tue, 2012-07-10 at 04:17 +0200, Marek Vasut wrote:
Dear Manukumar,
hello I checked with the hardware spec in that P1020RDB: having connection like P1012processor -> PHY -> HUB -> ports
whereas in custom board P1012processor -> phy -> port(single usb port)
This is fairy normal.
In uboot source code initializing sequence of u-boot is below: 1.usb_init() 2.usb_scan_devices() 3.usb_new_device(dev) 4.usb_hub_probe(dev, 0) 5.usb_hub_configure(dev)
how can we do this in u-boot source code
But I don't see what you're asking about.
manukumar signal-networks
[...]
Best regards, Marek Vasut
Dear All
While board bring up in custom board iam getting below mentioned error
I2C: ready DRAM: DDR: failed to read SPD from address
I googled it but i am un able to rectify it.. Please resole ASAP manukumar
Truncated CCs
Hi,
On 2012.10/25, Manukumar wrote:
Dear All
While board bring up in custom board iam getting below mentioned error
I2C: ready DRAM: DDR: failed to read SPD from address
It seems you are using a DIMM for your memory (as opposed to directly soldered on the board).
Simply put, DDR DIMMs have a small EEPROM which contains data about the device. You access the SPD EEPROM via an I2C address. If the DIMM detection code talks to this address and does not detect correct data, then you have the problem you are encountering.
Since you are using a custom board, you should read your specs or ask your HW people about the correct SPD address.
I googled it but i am un able to rectify it.. Please resole ASAP manukumar
All the best, RgC
Dear all I have a query on bootm command. In the link provided below: http://www.linuxquestions.org/questions/linux-kernel-70/how-kernel-figure-ou...
They have given: bootm command will modify the dts/dtb file's memory section, and pass the memory size into Kernel by dts/dtb file.
please provide me information how dose bootm command is related to dts file.and how to overcome this issue.
manukumar signal-networks
Dear Manukumar,
[excessive Cc: list truncated]
In message 1348656159.2591.4.camel@Manukumar you wrote:
bootm command will modify the dts/dtb file's memory section, and pass the memory size into Kernel by dts/dtb file.
It does this, and more things, depending on architecture and board. for example, it will most likely also insert the MAC address(es) into the device tree.
please provide me information how dose bootm command is related to dts file.and how to overcome this issue.
I don't see why you would want to "overcome" this. This is an important and extremely useful capability of U-Boot.
Best regards,
Wolfgang Denk
Dear all,
In u-boot(u-boot-2010.12) 1) The TEXT_BASE address is 11001000. 2) Nand Flash Erasing at Address 0x00000000 3) Nand Flash Writing u-boot-nand.bin at address 0x00000000 4) When Power is switched On the booting happens.
till this there is no issue, now i want to change the booting address to different location(ex:0x02000000) do i want to change the TEXT_BASE address accordingly to boot it from 0x02000000. like below,
1) The TEXT_BASE address is 0x02000000. 2) Nand Flash Erasing at Address 0x02000000 3) Nand Flash writing u-boot-nand.bin at address 0x02000000 .
if i do as above i cant boot from nand there is no boot log messages.
Please suggest me on How can i do to boot from different location
Manukumar Signal-networks
On 10/03/2012 07:24:35 AM, Manukumar wrote:
Dear all,
In u-boot(u-boot-2010.12)
That's almost two years old. Please upgrade.
- The TEXT_BASE address is 11001000.
Judging from this you seem to be using either P1010RDB or P1023RDS (or maybe some out-of-tree board?). Always let us know what board you're talking about.
- Nand Flash Erasing at Address 0x00000000
- Nand Flash Writing u-boot-nand.bin at address 0x00000000
- When Power is switched On the booting happens.
till this there is no issue, now i want to change the booting address to different location(ex:0x02000000)
Because you don't have as much RAM on this board, or some other reason?
do i want to change the TEXT_BASE address accordingly to boot it from 0x02000000. like below,
- The TEXT_BASE address is 0x02000000.
- Nand Flash Erasing at Address 0x02000000
- Nand Flash writing u-boot-nand.bin at address 0x02000000 .
Did you update other relevant variables such as CONFIG_SYS_NAND_U_BOOT_DST and CONFIG_SYS_NAND_U_BOOT_START?
Plus you really should leave that 0x1000 offset in there. On mpc85xx NAND boot, TEXT_BASE is 4K after the start of the image, since the boot page comes first.
-Scott
Dear all,
Yes i am using P1020RDb board. Actually i have to make 2 boot(u-boot) B1 and B2 B1 is stored 0x0000_0000,B2 is stored in 0x010_0000 of nand flash.
when 1 power cycle is given Board gets booted from 0x0000_0000
my requirement is to boot B2 from 0x010_0000 how can i do that?
Regards Manukumar
On Wed, 2012-10-03 at 10:22 -0500, Scott Wood wrote:
On 10/03/2012 07:24:35 AM, Manukumar wrote:
Dear all,
In u-boot(u-boot-2010.12)
That's almost two years old. Please upgrade.
- The TEXT_BASE address is 11001000.
Judging from this you seem to be using either P1010RDB or P1023RDS (or maybe some out-of-tree board?). Always let us know what board you're talking about.
- Nand Flash Erasing at Address 0x00000000
- Nand Flash Writing u-boot-nand.bin at address 0x00000000
- When Power is switched On the booting happens.
till this there is no issue, now i want to change the booting address to different location(ex:0x02000000)
Because you don't have as much RAM on this board, or some other reason?
do i want to change the TEXT_BASE address accordingly to boot it from 0x02000000. like below,
- The TEXT_BASE address is 0x02000000.
- Nand Flash Erasing at Address 0x02000000
- Nand Flash writing u-boot-nand.bin at address 0x02000000 .
Did you update other relevant variables such as CONFIG_SYS_NAND_U_BOOT_DST and CONFIG_SYS_NAND_U_BOOT_START?
Plus you really should leave that 0x1000 offset in there. On mpc85xx NAND boot, TEXT_BASE is 4K after the start of the image, since the boot page comes first.
-Scott
On 10/04/2012 05:18:57 AM, Manukumar wrote:
Dear all,
Yes i am using P1020RDb board.
Note that there are (at least) two variants of this board, one using P1_P2_RDB and the other p1_p2_rdb_pc.
Actually i have to make 2 boot(u-boot) B1 and B2 B1 is stored 0x0000_0000,B2 is stored in 0x010_0000 of nand flash.
when 1 power cycle is given Board gets booted from 0x0000_0000
my requirement is to boot B2 from 0x010_0000 how can i do that?
You can't. That's not what TEXT_BASE means. The hardware is only capable of booting from the beginning of NAND flash.
At best you could have one SPL at the beginning of NAND flash that chooses which main U-Boot to load, but that is something you'd have to implement yourself.
-Scott
Dear All,
How to access u-boot environment variables from kernel space or user space in P1012 processor.
The variables required to be accessed from uboot environment section are:
eth1addr serverip
Note: Kernel version = 2.6.35
Regards Manukumar
On Tue, Dec 4, 2012 at 1:04 PM, Manukumar manukumar@signal-networks.com wrote:
Dear All,
How to access u-boot environment variables from kernel space or user space in P1012 processor.
The variables required to be accessed from uboot environment section are:
eth1addr
You can get the MAC address from related registers of your Ethernet controller, provided they where set by u-boot. This is way the network driver goes.
Yegor
On 12/04/2012 07:24:51 AM, Yegor Yefremov wrote:
On Tue, Dec 4, 2012 at 1:04 PM, Manukumar manukumar@signal-networks.com wrote:
Dear All,
How to access u-boot environment variables from kernel space or user space in P1012 processor.
The variables required to be accessed from uboot environment section are:
eth1addr
You can get the MAC address from related registers of your Ethernet controller, provided they where set by u-boot. This is way the network driver goes.
No, you get that from the device tree. You cannot rely on U-Boot to have initialized the network hardware, or on the network hardware to not have been reset since then.
-Scott
On 12/04/2012 07:24:51 AM, Yegor Yefremov wrote:
On Tue, Dec 4, 2012 at 1:04 PM, Manukumar <manukumar@signal-networks.com**> wrote:
Dear All,
How to access u-boot environment variables from kernel space or user space in P1012 processor.
Have you looked at fw_printenv? I get output like this from it:
root:~> fw_printenv
bootargs=root=/dev/mtdblock0 rw console=ttyBF0,115200
bootcmd=run flashboot
bootdelay=2
Email me direct if you want my notes on setting it up.
Steve
Dear All,
I have to implement the jtag and execute XSVF file through diagnostic command from u-boot. the layout of our board as below: __________ |_Processor| -> FPGA -> CPLD---- ^ | |__________________________|
I can able to get Device ID of both FPGA and CPLD but iam not able to execute XSVF file. when i debuged the code i found that it is expecting data from TDO line. but this is not happening.
My question is: when i can able to get device id why can i execute the XSVF file
NOTE: The state is moving As below
xsvfDoXREPEAT xsvfDoXENDXR xsvfDoXENDXR xsvfDoXSTATE xsvfDoXSTATE xsvfDoXRUNTEST xsvfDoXSIR xsvfDoXSDRSIZE xsvfDoXSDRSIZE xsvfDoXTDOMASK xsvfDoXSDRTDO
TAP State = DRUPDATE TAP State = RUNTEST/IDLE TDO Expected = 0xf4004093 TDO Captured = TDO Mask = 0x0fffffff xsvfDoXSDRTDO iErrorCode ERROR: TDO mismatch ERROR at or near XSVF command #10.See line #10 in the XSVF ASCII file. Upgarde the Image and RESTART !!!
Regards Manukumar
Dear Manukumar,
In message 1359096605.2559.15.camel@Manukumar you wrote:
I have to implement the jtag and execute XSVF file through diagnostic command from u-boot. the layout of our board as below:
What exactly has this to do with above thread and with the "access u-boot environment variables from kernel space" subject?
And why exactly did you put all these people on Cc: ???
Best regards,
Wolfgang Denk
Hello, I am new to JTAG related concepts and I need to know from the basics. So please provide me related document or link to study on that.
Manukumar Signal-Networks
Dear Manukumar,
In message 1353643735.2597.0.camel@Manukumar you wrote:
I am new to JTAG related concepts and I need to know from the basics. So please provide me related document or link to study on that.
Please see http://bit.ly/TSzjGG
Note: there is no need to Cc: a ton of people who are all subscribed anyway.
Best regards,
Wolfgang Denk
Dear All
I am facing issue in Nand flash 2Gigabits(i.e 256MB)(MT29F2G08AABWP) Bring up After changing from 32MB(K9F5608U0d).
To program nand flash we are using code warrior, here we dont have correct match of nand flash part number for 2Gbits and so we took nand flash part number where flash organization is similar to 2Gbits. with this above procedure i can able to detect,erase and write the flash. After flashing u-boot image to this flash the board has not Up. please provide me inputs to solve this issues.
(Note: we are not faced any issues while booting from 32MB board has completly up)
I want to know reason why board has not up with 256MB flash.
manukumar signal-networks.
Dear Manukumar,
Dear All
I am facing issue in Nand flash 2Gigabits(i.e 256MB)(MT29F2G08AABWP) Bring up After changing from 32MB(K9F5608U0d).
What board is that? Please never leave these details out, we can't help you otherwise.
To program nand flash we are using code warrior, here we dont have correct match of nand flash part number for 2Gbits and so we took nand flash part number where flash organization is similar to 2Gbits. with this above procedure i can able to detect,erase and write the flash. After flashing u-boot image to this flash the board has not Up. please provide me inputs to solve this issues.
(Note: we are not faced any issues while booting from 32MB board has completly up)
I want to know reason why board has not up with 256MB flash.
manukumar signal-networks.
Best regards, Marek Vasut
On 05/23/2012 12:56 AM, Manukumar wrote:
u-boot version: u-boot-2010.12
My OR and BR register values(according to our memory map): BR0 0xFF800C21 OR0 0xFF800396 BR1 0xE8000801 OR1 0xFFFF8074 BR2 0xE8009001 OR2 0xFFFF8074
after defining VERBOSE_DEBUG in drivers/mtd/nand/fsl_elbc_nand.c i gave sacveenv command, igot below logs. please go through that and resolve asap.
People on this list are generally happy to help as time is available, but if you need "asap" either contact support@freescale.com (especially when using Freescale-supplied U-Boot) or another official Freescale FAE or support contact, or hire someone to look into it.
skipping bad block = 0
I don't see this exact message in mainline U-Boot, even in old versions. And zero being a bad block would be a bad thing -- I suspect things have gone wrong before the output you provided.
DEBUG: set_addr: bank=0, ctrl->addr=0xff800000 (0xff800000), index 0, pes 14 ps 9 fsl_elbc_run_command DEBUG: fsl_elbc_run_command: fmr=0000f023 fir=4e000000 fcr=70000000 DEBUG: fsl_elbc_run_command: fbar=00000000 fpar=00000000 fbcr=00000001 bank=0 DEBUG: fsl_elbc_run_command: stat=40000001 mdr=00000000 fmr=0000f020
This is showing a command timeout (LTESR[FCT]). What happened with the NAND earlier in the boot sequence?
-Scott
participants (9)
-
Albert ARIBAUD -
Manukumar -
Marek Vasut -
Marek Vasut -
RgC -
Scott Wood -
Steve Strobel -
Wolfgang Denk -
Yegor Yefremov