* [U-Boot] Nand flash R/W,saveenv issue.. [not found] <1337677828.2382.30.camel@Manukumar> @ 2012-05-22 14:15 ` Marek Vasut 2012-05-22 17:56 ` Scott Wood 0 siblings, 1 reply; 40+ messages in thread From: Marek Vasut @ 2012-05-22 14:15 UTC (permalink / raw) To: u-boot 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] Nand flash R/W,saveenv issue.. 2012-05-22 14:15 ` [U-Boot] Nand flash R/W,saveenv issue Marek Vasut @ 2012-05-22 17:56 ` Scott Wood 2012-05-23 5:56 ` Manukumar 0 siblings, 1 reply; 40+ messages in thread From: Scott Wood @ 2012-05-22 17:56 UTC (permalink / raw) To: u-boot 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] Nand flash R/W,saveenv issue.. 2012-05-22 17:56 ` Scott Wood @ 2012-05-23 5:56 ` Manukumar 2012-05-23 8:02 ` Wolfgang Denk 2012-05-23 22:45 ` [U-Boot] Nand flash R/W,saveenv issue Scott Wood 0 siblings, 2 replies; 40+ messages in thread From: Manukumar @ 2012-05-23 5:56 UTC (permalink / raw) To: u-boot 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 > ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] Nand flash R/W,saveenv issue.. 2012-05-23 5:56 ` Manukumar @ 2012-05-23 8:02 ` Wolfgang Denk 2012-05-23 8:30 ` Manukumar 2012-05-23 22:45 ` [U-Boot] Nand flash R/W,saveenv issue Scott Wood 1 sibling, 1 reply; 40+ messages in thread From: Wolfgang Denk @ 2012-05-23 8:02 UTC (permalink / raw) To: u-boot 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 -- 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: wd at denx.de The moral of the story is: "Don't stop to tighten your shoe laces during the Olympics 100m finals". - Kevin Jones in <DEJo68.K1t@bri.hp.com> ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] Nand flash R/W,saveenv issue.. 2012-05-23 8:02 ` Wolfgang Denk @ 2012-05-23 8:30 ` Manukumar 2012-05-23 16:16 ` Scott Wood 0 siblings, 1 reply; 40+ messages in thread From: Manukumar @ 2012-05-23 8:30 UTC (permalink / raw) To: u-boot 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 > ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] Nand flash R/W,saveenv issue.. 2012-05-23 8:30 ` Manukumar @ 2012-05-23 16:16 ` Scott Wood 2012-05-30 5:02 ` [U-Boot] problem while making kernel up Manukumar 0 siblings, 1 reply; 40+ messages in thread From: Scott Wood @ 2012-05-23 16:16 UTC (permalink / raw) To: u-boot 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] problem while making kernel up 2012-05-23 16:16 ` Scott Wood @ 2012-05-30 5:02 ` Manukumar 2012-05-30 16:18 ` Scott Wood 0 siblings, 1 reply; 40+ messages in thread From: Manukumar @ 2012-05-30 5:02 UTC (permalink / raw) To: u-boot 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 > ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] problem while making kernel up 2012-05-30 5:02 ` [U-Boot] problem while making kernel up Manukumar @ 2012-05-30 16:18 ` Scott Wood 2012-05-31 4:15 ` Manukumar 0 siblings, 1 reply; 40+ messages in thread From: Scott Wood @ 2012-05-30 16:18 UTC (permalink / raw) To: u-boot 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.. > > 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 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] problem while making kernel up 2012-05-30 16:18 ` Scott Wood @ 2012-05-31 4:15 ` Manukumar 2012-05-31 16:21 ` Scott Wood 0 siblings, 1 reply; 40+ messages in thread From: Manukumar @ 2012-05-31 4:15 UTC (permalink / raw) To: u-boot 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.. > > > > 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 > > 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 > ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] problem while making kernel up 2012-05-31 4:15 ` Manukumar @ 2012-05-31 16:21 ` Scott Wood 2012-06-01 3:58 ` Manukumar 2012-06-01 10:10 ` Manukumar 0 siblings, 2 replies; 40+ messages in thread From: Scott Wood @ 2012-05-31 16:21 UTC (permalink / raw) To: u-boot 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] problem while making kernel up 2012-05-31 16:21 ` Scott Wood @ 2012-06-01 3:58 ` Manukumar 2012-06-01 10:10 ` Manukumar 1 sibling, 0 replies; 40+ messages in thread From: Manukumar @ 2012-06-01 3:58 UTC (permalink / raw) To: u-boot 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 at ni.com, sr at denx.de, u-boot at lists.denx.de, ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] problem while making kernel up 2012-05-31 16:21 ` Scott Wood 2012-06-01 3:58 ` Manukumar @ 2012-06-01 10:10 ` Manukumar 2012-06-01 17:15 ` Scott Wood 2012-09-11 12:47 ` [U-Boot] Nand Flash Programing and Board Bring Up Manukumar 1 sibling, 2 replies; 40+ messages in thread From: Manukumar @ 2012-06-01 10:10 UTC (permalink / raw) To: u-boot 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 > -------------- next part -------------- U-Boot 2010.12 (May 11 2012 - 10:14:18) CPU0: P1021, Version: 1.1, (0x80e40111) Core: E500, Version: 5.1, (0x80212051) Clock Configuration: CPU0:533.333 MHz, CPU1:1200 MHz, CCB:266.667 MHz, DDR:100 MHz (200 MT/s data rate) (Asynchronous), LBC:16.667 MHz QE:266.667 MHz L1: D-cache 32 kB enabled I-cache 32 kB enabled Board: P1021RDB CPLD: V15.15 PCBA: V15.0 Error reading i2c boot information! I2C: ready SPI: ready DRAM: DDR: failed to read SPD from address 82 SPD error! Trying fallback to raw timing calculation Detected UDIMM(s) The choosen cas latency 5 is too large 1 GiB (DDR3, 32-bit, CL=6, ECC off) **board_init_r** L2: 256 KB enabled CPU up timeout. CPU up mask is 1 should be 3 NAND: fsl_elbc_nand: address did not match any chip selects 0 MiB MMC: FSL_ESDHC: 0 *** Warning - bad CRC, using default environment PCIe1: disabled PCIe2: disabled In: serial Out: serial Err: serial Net: PHY_ADDR=4 PHY_ADDR3=5 eTSEC1: PHY is AR8021 (4dd041) MII read Phy 4 debug reg address 0x0b val:bc60 PHY_ADDR=0 PHY_ADDR3=5 eTSEC2: PHY is AR8021 (4dd041) PHY_ADDR=5 PHY_ADDR3=5 eTSEC3: No support for PHY id ffffffff; assuming generic eTSEC1, eTSEC2, eTSEC3 Hit any key to stop autoboot: 0 => setenv bootargs root=/dev/nfs rw nfsroot=192.168.1.68:/home/project/ICMv1.1/filesystem ip=192.168.1.250:192.168.1.68:192.1680 => setenv ipaddr 192.168.1.250; setenv serverip 192.168.1.68; setenv ethaddr 00:1a:b0:00:02:50; tftp 1000000 uImage_icm_v1.1;tf0 SIG_PRIN: phy addr 4 SIG_PRIN: mii_parse_link SIG_PRIN: adjust_link Speed: 100, full duplex Using eTSEC1 device TFTP from server 192.168.1.68; our IP address is 192.168.1.250 Filename 'uImage_icm_v1.1'. Load address: 0x1000000 Loading: ############Got error 14 T ##########################Got error 14 T ######Got error 14 T #################Got error 4 Abort SIG_PRIN: phy addr 4 SIG_PRIN: mii_parse_link SIG_PRIN: adjust_link Speed: 100, full duplex Using eTSEC1 device TFTP from server 192.168.1.68; our IP address is 192.168.1.250 Filename 'p1021rdb_32b.dtb'. Load address: 0xc00000 Loading: ## done Bytes transferred = 15066 (3ada hex) WARNING: adjusting available memory to 30000000 ## Booting kernel from Legacy Image at 01000000 ... Image Name: Signal ICMv1.1 Created: 2012-05-31 21:36:15 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 3559856 Bytes = 3.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image! => setenv ipaddr 192.168.1.250; setenv serverip 192.168.1.68; setenv ethaddr 00:1a:b0:00:02:50; tftp 1000000 uImage_icm_v1.1;tf0 SIG_PRIN: phy addr 4 SIG_PRIN: mii_parse_link SIG_PRIN: adjust_link Speed: 100, full duplex Using eTSEC1 device TFTP from server 192.168.1.68; our IP address is 192.168.1.250 Filename 'uImage_icm_v1.1'. Load address: 0x1000000 Loading: ########################################Got error 4 T #############Got error 14 T ############ ################################################Got error 14 T ################# ################################################################# ###############################################Got error 4 T # done Bytes transferred = 3559920 (3651f0 hex) SIG_PRIN: phy addr 4 SIG_PRIN: mii_parse_link SIG_PRIN: adjust_link Speed: 100, full duplex Using eTSEC1 device TFTP from server 192.168.1.68; our IP address is 192.168.1.250 Filename 'p1021rdb_32b.dtb'. Load address: 0xc00000 Loading: ## done Bytes transferred = 15066 (3ada hex) WARNING: adjusting available memory to 30000000 ## Booting kernel from Legacy Image at 01000000 ... Image Name: Signal ICMv1.1 Created: 2012-05-31 21:36:15 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 3559856 Bytes = 3.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 00c00000 Booting using the fdt blob at 0xc00000 Uncompressing Kernel Image ... OK Loading Device Tree to 00ff9000, end 00fffad9 ... OK WARNING: could not find compatiblenode fsl-usb2-dr: FDT_ERR_NOTFOUND. Using P1021 RDB-PC machine description Memory CAM mapping: 256/256/256 Mb, residual: 256Mb Linux version 2.6.35 (root at NatLAB7) (gcc version 4.5.1 (Sourcery G++ Lite 2010.09-55) ) #16 SMP Fri Jun 1 03:06:05 IST 2012 CPU maps initialized for 1 thread per core bootconsole [udbg0] enabled setup_arch: bootmem mpc85xx_rdb_setup_arch() Could not find Quicc Engine node MPC85xx RDB board from Freescale Semiconductor arch: exit Zone PFN ranges: DMA 0x00000000 -> 0x00030000 Normal empty HighMem 0x00030000 -> 0x00040000 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0: 0x00000000 -> 0x00040000 MMU: Allocated 1088 bytes of context maps for 255 contexts PERCPU: Embedded 7 pages/cpu @c0f33000 s6880 r8192 d13600 u65536 pcpu-alloc: s6880 r8192 d13600 u65536 alloc=16*4096 pcpu-alloc: [0] 0 [0] 1 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260096 Kernel command line: root=/dev/nfs rw nfsroot=192.168.1.68:/home/project/ICMv1.1/filesystem ip=192.168.1.250:192.168.1.68:192.10 PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 1032048k/1048576k available (6856k kernel code, 16528k reserved, 288k data, 189k bss, 252k init) Kernel virtual memory layout: * 0xfffbf000..0xfffff000 : fixmap * 0xff800000..0xffc00000 : highmem PTEs * 0xff7fe000..0xff800000 : early ioremap * 0xf1000000..0xff7fe000 : vmalloc & ioremap SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 Hierarchical RCU implementation. RCU-based detection of stalled CPUs is disabled. Verbose stalled-CPUs detection is disabled. NR_IRQS:512 mpic: Setting up MPIC " OpenPIC " version 1.2 at ffe40000, max 2 CPUs mpic: ISU size: 256, shift: 8, mask: ff mpic: Initializing for 256 sources Could not find qe-ic node clocksource: timebase mult[7800001] shift[22] registered Console: colour dummy device 80x25 pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 mpic: requesting IPIs... Processor 1 is stuck. Brought up 1 CPUs xor: measuring software checksum speed 8regs : 654.000 MB/sec 8regs_prefetch: 563.000 MB/sec 32regs : 651.000 MB/sec 32regs_prefetch: 579.000 MB/sec xor: using function: 8regs (654.000 MB/sec) NET: Registered protocol family 16 tdm_init PCI: Probing PCI hardware bio: create slab <bio-0> at 0 vgaarb: loaded SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb raid6: int32x1 76 MB/s raid6: int32x2 133 MB/s raid6: int32x4 190 MB/s raid6: int32x8 159 MB/s raid6: using algorithm int32x4 (190 MB/s) Freescale Elo / Elo Plus DMA driver Advanced Linux Sound Architecture Driver Version 1.0.23. Switching to clocksource timebase NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 7, 524288 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered UDP hash table entries: 512 (order: 2, 16384 bytes) UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. SIGNET: qe_drv_init fsl-elo-dma ffe21300.dma: #0 (fsl,eloplus-dma-channel), irq 20 fsl-elo-dma ffe21300.dma: #1 (fsl,eloplus-dma-channel), irq 21 fsl-elo-dma ffe21300.dma: #2 (fsl,eloplus-dma-channel), irq 22 fsl-elo-dma ffe21300.dma: #3 (fsl,eloplus-dma-channel), irq 23 MPIC global timer init done... MPIC EXTERNAL INTERRUPT init done audit: initializing netlink socket (disabled) type=2000 audit(5.495:1): initialized highmem bounce pool size: 64 pages Installing knfsd (copyright (C) 1996 okir at monad.swb.de). Slow work thread pool: Starting up Slow work thread pool: Ready NTFS driver 2.1.29 [Flags: R/O]. JFFS2 version 2.2. (NAND) (SUMMARY) ?? 2001-2006 Red Hat, Inc. JFFS2: default compression mode: priority SGI XFS with security attributes, large block/inode numbers, no debug enabled msgmni has been set to 1503 alg: No test for stdrng (krng) async_tx: api initialized (async) io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) Generic non-volatile memory driver v1.1 Serial: 8250/16550 driver, 2 ports, IRQ sharing enabled serial8250.0: ttyS0 at MMIO 0xffe04500 (irq = 42) is a 16550A (---------------------manu----------------------->>>>> after this it hangs in our custom board.) console [ttyS0] enabled, bootconsole disabled console [ttyS0] enabled, bootconsole disabled serial8250.0: ttyS1 at MMIO 0xffe04600 (irq = 42) is a 16550A Freescale QUICC Engine UART device driver brd: module loaded loop: module loaded st: Version 20081215, fixed bufsize 32768, s/g segs 256 of-flash ef000000.nor: do_map_probe() failed fsl-lbc ffe05000.localbus: address did not match any chip selects fsl-espi ffe07000.spi: Freescale eSPI Controller driver at 0xf110c000 (irq = 59) fsl_m25p80 spi32766.0: m25p80 (1024 Kbytes) Creating 5 MTD partitions on "SPIFLASH0": 0x000000000000-0x000000080000 : "SPI (RO) U-Boot Image" ftl_cs: FTL header not found. 0x000000080000-0x000000100000 : "SPI (RO) DTB Image" ftl_cs: FTL header not found. 0x000000100000-0x000000500000 : "SPI (RO) Linux Kernel Image" mtd: partition "SPI (RO) Linux Kernel Image" is out of reach -- disabled ftl_cs: FTL header not found. 0x000000500000-0x000000900000 : "SPI (RO) Compressed RFS Image" mtd: partition "SPI (RO) Compressed RFS Image" is out of reach -- disabled ftl_cs: FTL header not found. 0x000000900000-0x000001000000 : "SPI (RW) JFFS2 RFS" mtd: partition "SPI (RW) JFFS2 RFS" is out of reach -- disabled ftl_cs: FTL header not found. Fixed MDIO Bus: probed e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k4 e1000e: Copyright (c) 1999 - 2009 Intel Corporation. /proc/ptp_1588 created IEEE1588: ptp-timer devicepresent in the system IEEE1588: ptp-timer initialized eth0: Gianfar Ethernet Controller Version 1.4-skbr1.1.5, 00:1a:b0:00:02:50 eth0: Running with NAPI enabled eth0: RX BD ring size for Q[0]: 128 eth0: RX BD ring size for Q[1]: 128 eth0: RX BD ring size for Q[2]: 128 eth0: RX BD ring size for Q[3]: 128 eth0: RX BD ring size for Q[4]: 128 eth0: RX BD ring size for Q[5]: 128 eth0: RX BD ring size for Q[6]: 128 eth0: RX BD ring size for Q[7]: 128 eth0: TX BD ring size for Q[0]: 128 eth0: TX BD ring size for Q[1]: 128 eth0: TX BD ring size for Q[2]: 128 eth0: TX BD ring size for Q[3]: 128 eth0: TX BD ring size for Q[4]: 128 eth0: TX BD ring size for Q[5]: 128 eth0: TX BD ring size for Q[6]: 128 eth0: TX BD ring size for Q[7]: 128 IEEE1588: ptp-timer devicepresent in the system IEEE1588: ptp-timer initialized eth1: Gianfar Ethernet Controller Version 1.4-skbr1.1.5, 00:00:00:00:00:00 eth1: Running with NAPI enabled eth1: RX BD ring size for Q[0]: 128 eth1: RX BD ring size for Q[1]: 128 eth1: RX BD ring size for Q[2]: 128 eth1: RX BD ring size for Q[3]: 128 eth1: RX BD ring size for Q[4]: 128 eth1: RX BD ring size for Q[5]: 128 eth1: RX BD ring size for Q[6]: 128 eth1: RX BD ring size for Q[7]: 128 eth1: TX BD ring size for Q[0]: 128 eth1: TX BD ring size for Q[1]: 128 eth1: TX BD ring size for Q[2]: 128 eth1: TX BD ring size for Q[3]: 128 eth1: TX BD ring size for Q[4]: 128 eth1: TX BD ring size for Q[5]: 128 eth1: TX BD ring size for Q[6]: 128 eth1: TX BD ring size for Q[7]: 128 Freescale PowerQUICC MII Bus: probed mdio_bus mdio at ffe24000: error probing PHY at address 5 Freescale PowerQUICC MII Bus: probed Freescale PowerQUICC MII Bus: probed ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver fsl-ehci fsl-ehci.0: Found HC with no IRQ! usbcore: registered new interface driver cdc_acm cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usbcore: registered new interface driver usbserial usbserial: USB Serial Driver core Freescale USB OTG Driver loaded, $Revision: 1.55 $ i2c /dev entries driver rtc-pt7c4338 0-0068: rtc core: registered pt7c4338 as rtc0 PowerPC Book-E Watchdog Timer Loaded md: raid6 personality registered for level 6 md: raid5 personality registered for level 5 md: raid4 personality registered for level 4 sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman mmc0: SDHCI controller on ffe2e000.sdhci [ffe2e000.sdhci] using DMA <6>mknod tdm c 239 0 tdm_dev_init: registering the character device adap 0 tdm_fsl_starlite: Freescale Starlite TDM Driver Adapter:Init ucc_tdm: Freescale QE UCC TDM Driver:Init Freescale P1022 DS ALSA SoC fabric driver Freescale Synchronous Serial Interface (SSI) ASoC Driver ALSA device list: No soundcards found. IPv4 over IPv4 tunneling driver GRE over IPv4 tunneling driver TCP cubic registered Initializing XFRM netlink socket NET: Registered protocol family 10 IPv6 over IPv4 tunneling driver NET: Registered protocol family 17 NET: Registered protocol family 15 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com> All bugs added by David S. Miller <davem@redhat.com> rtc-pt7c4338 0-0068: setting system clock to 2000-01-01 00:01:25 UTC (946684885) ADDRCONF(NETDEV_UP): eth0: link is not ready IP-Config: Complete: device=eth0, addr=192.168.1.250, mask=255.255.255.0, gw=192.168.1.1, host=192.168.1.250, domain=, nis-domain=(none), bootserver=192.168.1.68, rootserver=192.168.1.68, rootpath= md: Waiting for all devices to be available before autodetect md: If you don't use raid, use raid=noautodetect md: Autodetecting RAID arrays. md: Scanned 0 and added 0 devices. md: autorun ... md: ... autorun DONE. Looking up port of RPC 100003/2 on 192.168.1.68 PHY: mdio at ffe24000:04 - Link is Up - 100/Full ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Looking up port of RPC 100005/1 on 192.168.1.68 VFS: Mounted root (nfs filesystem) on device 0:12. Freeing unused kernel memory: 252k init udev: starting version 141 udevd-event[1242]: error changing netif name eth0 to eth1: Device or resource busy FAT: unable to read boot sector EXT3-fs (md0): error: unable to read superblock EXT2-fs (md0): error: unable to read superblock EXT3-fs (md0): error: unable to read superblock EXT2-fs (md0): error: unable to read superblock FAT: unable to read boot sector INIT: Entering runlevel: 5 Starting OpenBSD Secure Shell server: sshd Privilege separation user sshd does not exist starting Busybox HTTP Daemon: httpd... done. Starting network benchmark server: netserver. sh: bad number creating NFS state directory: done starting 8 nfsd kernel threads: svc: failed to register lockdv1 RPC service (errno 97). done starting mountd: done starting statd: done Starting random number generator daemoncan't open /dev/hwrng: No such file or directory . Starting Samba: smbd nmbd. Starting syslogd/klogd: done OpenEmbedded Linux p1021rdb ttyS0 Mentor Graphics System Builder 3.0-release-20120310 p1021rdb ttyS0 p1021rdb login: ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] problem while making kernel up 2012-06-01 10:10 ` Manukumar @ 2012-06-01 17:15 ` Scott Wood 2012-06-06 8:13 ` Manukumar 2012-07-05 10:27 ` [U-Boot] USB detection Manukumar 2012-09-11 12:47 ` [U-Boot] Nand Flash Programing and Board Bring Up Manukumar 1 sibling, 2 replies; 40+ messages in thread From: Scott Wood @ 2012-06-01 17:15 UTC (permalink / raw) To: u-boot 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 at freescale.com, or try the latest upstream kernel and get help from linuxppc-dev at 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] problem while making kernel up 2012-06-01 17:15 ` Scott Wood @ 2012-06-06 8:13 ` Manukumar 2012-07-05 10:27 ` [U-Boot] USB detection Manukumar 1 sibling, 0 replies; 40+ messages in thread From: Manukumar @ 2012-06-06 8:13 UTC (permalink / raw) To: u-boot 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 at freescale.com, or try the latest upstream kernel and get help > from linuxppc-dev at 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 > ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] USB detection 2012-06-01 17:15 ` Scott Wood 2012-06-06 8:13 ` Manukumar @ 2012-07-05 10:27 ` Manukumar 2012-07-05 11:45 ` Albert ARIBAUD 1 sibling, 1 reply; 40+ messages in thread From: Manukumar @ 2012-07-05 10:27 UTC (permalink / raw) To: u-boot 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] USB detection 2012-07-05 10:27 ` [U-Boot] USB detection Manukumar @ 2012-07-05 11:45 ` Albert ARIBAUD 2012-07-05 15:34 ` Marek Vasut 2012-07-09 8:47 ` Manukumar 0 siblings, 2 replies; 40+ messages in thread From: Albert ARIBAUD @ 2012-07-05 11:45 UTC (permalink / raw) To: u-boot 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, -- Albert. ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] USB detection 2012-07-05 11:45 ` Albert ARIBAUD @ 2012-07-05 15:34 ` Marek Vasut 2012-07-09 8:47 ` Manukumar 1 sibling, 0 replies; 40+ messages in thread From: Marek Vasut @ 2012-07-05 15:34 UTC (permalink / raw) To: u-boot 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: > > 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, Best regards, Marek Vasut ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] USB detection 2012-07-05 11:45 ` Albert ARIBAUD 2012-07-05 15:34 ` Marek Vasut @ 2012-07-09 8:47 ` Manukumar 2012-07-09 12:18 ` Albert ARIBAUD ` (3 more replies) 1 sibling, 4 replies; 40+ messages in thread From: Manukumar @ 2012-07-09 8:47 UTC (permalink / raw) To: u-boot 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: > > 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, ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] USB detection 2012-07-09 8:47 ` Manukumar @ 2012-07-09 12:18 ` Albert ARIBAUD 2012-07-10 2:17 ` Marek Vasut ` (2 subsequent siblings) 3 siblings, 0 replies; 40+ messages in thread From: Albert ARIBAUD @ 2012-07-09 12:18 UTC (permalink / raw) To: u-boot 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, -- Albert. ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] USB detection 2012-07-09 8:47 ` Manukumar 2012-07-09 12:18 ` Albert ARIBAUD @ 2012-07-10 2:17 ` Marek Vasut 2012-07-12 6:10 ` Manukumar 2012-09-26 10:42 ` [U-Boot] bootm command in U-boot Manukumar 2012-10-03 12:24 ` [U-Boot] Booting through nand flash with other address Manukumar 3 siblings, 1 reply; 40+ messages in thread From: Marek Vasut @ 2012-07-10 2:17 UTC (permalink / raw) To: u-boot 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] USB detection 2012-07-10 2:17 ` Marek Vasut @ 2012-07-12 6:10 ` Manukumar 2012-10-25 12:21 ` Manukumar 0 siblings, 1 reply; 40+ messages in thread From: Manukumar @ 2012-07-12 6:10 UTC (permalink / raw) To: u-boot 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 > ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] USB detection 2012-07-12 6:10 ` Manukumar @ 2012-10-25 12:21 ` Manukumar 2012-10-25 13:26 ` RgC 0 siblings, 1 reply; 40+ messages in thread From: Manukumar @ 2012-10-25 12:21 UTC (permalink / raw) To: u-boot 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] USB detection 2012-10-25 12:21 ` Manukumar @ 2012-10-25 13:26 ` RgC 0 siblings, 0 replies; 40+ messages in thread From: RgC @ 2012-10-25 13:26 UTC (permalink / raw) To: u-boot 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 487 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20121025/843eb01c/attachment.pgp> ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] bootm command in U-boot 2012-07-09 8:47 ` Manukumar 2012-07-09 12:18 ` Albert ARIBAUD 2012-07-10 2:17 ` Marek Vasut @ 2012-09-26 10:42 ` Manukumar 2012-09-26 14:14 ` Wolfgang Denk 2012-10-03 12:24 ` [U-Boot] Booting through nand flash with other address Manukumar 3 siblings, 1 reply; 40+ messages in thread From: Manukumar @ 2012-09-26 10:42 UTC (permalink / raw) To: u-boot 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-out-ddr-ram-size-when-bootargss-mem-not-specified-948165/ 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] bootm command in U-boot 2012-09-26 10:42 ` [U-Boot] bootm command in U-boot Manukumar @ 2012-09-26 14:14 ` Wolfgang Denk 0 siblings, 0 replies; 40+ messages in thread From: Wolfgang Denk @ 2012-09-26 14:14 UTC (permalink / raw) To: u-boot 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 -- 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: wd at denx.de Steal five dollars and you were a petty thief. Steal thousands of dollars and you are either a government or a hero. - Terry Pratchett, _Going_Postal_ ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] Booting through nand flash with other address 2012-07-09 8:47 ` Manukumar ` (2 preceding siblings ...) 2012-09-26 10:42 ` [U-Boot] bootm command in U-boot Manukumar @ 2012-10-03 12:24 ` Manukumar 2012-10-03 15:22 ` Scott Wood 3 siblings, 1 reply; 40+ messages in thread From: Manukumar @ 2012-10-03 12:24 UTC (permalink / raw) To: u-boot 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] Booting through nand flash with other address 2012-10-03 12:24 ` [U-Boot] Booting through nand flash with other address Manukumar @ 2012-10-03 15:22 ` Scott Wood 2012-10-04 10:18 ` Manukumar 2012-11-23 4:08 ` [U-Boot] Quer on JTAG Manukumar 0 siblings, 2 replies; 40+ messages in thread From: Scott Wood @ 2012-10-03 15:22 UTC (permalink / raw) To: u-boot 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. > 1) 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. > 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) 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, > > 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 . 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] Booting through nand flash with other address 2012-10-03 15:22 ` Scott Wood @ 2012-10-04 10:18 ` Manukumar 2012-10-04 17:21 ` Scott Wood 2012-11-23 4:08 ` [U-Boot] Quer on JTAG Manukumar 1 sibling, 1 reply; 40+ messages in thread From: Manukumar @ 2012-10-04 10:18 UTC (permalink / raw) To: u-boot 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. > > > 1) 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. > > > 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) > > 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, > > > > 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 . > > 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] Booting through nand flash with other address 2012-10-04 10:18 ` Manukumar @ 2012-10-04 17:21 ` Scott Wood 2012-12-04 12:04 ` [U-Boot] access u-boot environment variables from kernel space Manukumar 0 siblings, 1 reply; 40+ messages in thread From: Scott Wood @ 2012-10-04 17:21 UTC (permalink / raw) To: u-boot 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] access u-boot environment variables from kernel space 2012-10-04 17:21 ` Scott Wood @ 2012-12-04 12:04 ` Manukumar 2012-12-04 13:24 ` Yegor Yefremov 0 siblings, 1 reply; 40+ messages in thread From: Manukumar @ 2012-12-04 12:04 UTC (permalink / raw) To: u-boot 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] access u-boot environment variables from kernel space 2012-12-04 12:04 ` [U-Boot] access u-boot environment variables from kernel space Manukumar @ 2012-12-04 13:24 ` Yegor Yefremov 2012-12-04 16:26 ` Scott Wood 0 siblings, 1 reply; 40+ messages in thread From: Yegor Yefremov @ 2012-12-04 13:24 UTC (permalink / raw) To: u-boot 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] access u-boot environment variables from kernel space 2012-12-04 13:24 ` Yegor Yefremov @ 2012-12-04 16:26 ` Scott Wood 2012-12-04 16:35 ` Steve Strobel 2013-01-25 6:50 ` Manukumar 0 siblings, 2 replies; 40+ messages in thread From: Scott Wood @ 2012-12-04 16:26 UTC (permalink / raw) To: u-boot 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] access u-boot environment variables from kernel space 2012-12-04 16:26 ` Scott Wood @ 2012-12-04 16:35 ` Steve Strobel 2013-01-25 6:50 ` Manukumar 1 sibling, 0 replies; 40+ messages in thread From: Steve Strobel @ 2012-12-04 16:35 UTC (permalink / raw) To: u-boot 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 -- Steve Strobel Link Communications, Inc. 1035 Cerise Rd Billings, MT 59101-7378 (406) 245-5002 ext 102 (406) 245-4889 (fax) WWW: http://www.link-comm.com MailTo:steve.strobel at link-comm.com ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] access u-boot environment variables from kernel space 2012-12-04 16:26 ` Scott Wood 2012-12-04 16:35 ` Steve Strobel @ 2013-01-25 6:50 ` Manukumar 2013-01-25 9:22 ` Wolfgang Denk 1 sibling, 1 reply; 40+ messages in thread From: Manukumar @ 2013-01-25 6:50 UTC (permalink / raw) To: u-boot 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] access u-boot environment variables from kernel space 2013-01-25 6:50 ` Manukumar @ 2013-01-25 9:22 ` Wolfgang Denk 0 siblings, 0 replies; 40+ messages in thread From: Wolfgang Denk @ 2013-01-25 9:22 UTC (permalink / raw) To: u-boot 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 -- 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: wd at denx.de The White Rabbit put on his spectacles. "Where shall I begin, please your Majesty ?" he asked. "Begin at the beginning,", the King said, very gravely, "and go on till you come to the end: then stop." -- Lewis Carroll ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] Quer on JTAG. 2012-10-03 15:22 ` Scott Wood 2012-10-04 10:18 ` Manukumar @ 2012-11-23 4:08 ` Manukumar 2012-11-23 5:33 ` Wolfgang Denk 1 sibling, 1 reply; 40+ messages in thread From: Manukumar @ 2012-11-23 4:08 UTC (permalink / raw) To: u-boot 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] Quer on JTAG. 2012-11-23 4:08 ` [U-Boot] Quer on JTAG Manukumar @ 2012-11-23 5:33 ` Wolfgang Denk 0 siblings, 0 replies; 40+ messages in thread From: Wolfgang Denk @ 2012-11-23 5:33 UTC (permalink / raw) To: u-boot 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 -- 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: wd at denx.de You get a wonderful view from the point of no return. - Terry Pratchett, _Making_Money_ ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] Nand Flash Programing and Board Bring Up 2012-06-01 10:10 ` Manukumar 2012-06-01 17:15 ` Scott Wood @ 2012-09-11 12:47 ` Manukumar 2012-09-11 14:10 ` Marek Vasut 1 sibling, 1 reply; 40+ messages in thread From: Manukumar @ 2012-09-11 12:47 UTC (permalink / raw) To: u-boot 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. ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] Nand Flash Programing and Board Bring Up 2012-09-11 12:47 ` [U-Boot] Nand Flash Programing and Board Bring Up Manukumar @ 2012-09-11 14:10 ` Marek Vasut 0 siblings, 0 replies; 40+ messages in thread From: Marek Vasut @ 2012-09-11 14:10 UTC (permalink / raw) To: u-boot 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
* [U-Boot] Nand flash R/W,saveenv issue.. 2012-05-23 5:56 ` Manukumar 2012-05-23 8:02 ` Wolfgang Denk @ 2012-05-23 22:45 ` Scott Wood 1 sibling, 0 replies; 40+ messages in thread From: Scott Wood @ 2012-05-23 22:45 UTC (permalink / raw) To: u-boot 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 at 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 ^ permalink raw reply [flat|nested] 40+ messages in thread
end of thread, other threads:[~2013-01-25 9:22 UTC | newest]
Thread overview: 40+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1337677828.2382.30.camel@Manukumar>
2012-05-22 14:15 ` [U-Boot] Nand flash R/W,saveenv issue Marek Vasut
2012-05-22 17:56 ` Scott Wood
2012-05-23 5:56 ` Manukumar
2012-05-23 8:02 ` Wolfgang Denk
2012-05-23 8:30 ` Manukumar
2012-05-23 16:16 ` Scott Wood
2012-05-30 5:02 ` [U-Boot] problem while making kernel up Manukumar
2012-05-30 16:18 ` Scott Wood
2012-05-31 4:15 ` Manukumar
2012-05-31 16:21 ` Scott Wood
2012-06-01 3:58 ` Manukumar
2012-06-01 10:10 ` Manukumar
2012-06-01 17:15 ` Scott Wood
2012-06-06 8:13 ` Manukumar
2012-07-05 10:27 ` [U-Boot] USB detection Manukumar
2012-07-05 11:45 ` Albert ARIBAUD
2012-07-05 15:34 ` Marek Vasut
2012-07-09 8:47 ` Manukumar
2012-07-09 12:18 ` Albert ARIBAUD
2012-07-10 2:17 ` Marek Vasut
2012-07-12 6:10 ` Manukumar
2012-10-25 12:21 ` Manukumar
2012-10-25 13:26 ` RgC
2012-09-26 10:42 ` [U-Boot] bootm command in U-boot Manukumar
2012-09-26 14:14 ` Wolfgang Denk
2012-10-03 12:24 ` [U-Boot] Booting through nand flash with other address Manukumar
2012-10-03 15:22 ` Scott Wood
2012-10-04 10:18 ` Manukumar
2012-10-04 17:21 ` Scott Wood
2012-12-04 12:04 ` [U-Boot] access u-boot environment variables from kernel space Manukumar
2012-12-04 13:24 ` Yegor Yefremov
2012-12-04 16:26 ` Scott Wood
2012-12-04 16:35 ` Steve Strobel
2013-01-25 6:50 ` Manukumar
2013-01-25 9:22 ` Wolfgang Denk
2012-11-23 4:08 ` [U-Boot] Quer on JTAG Manukumar
2012-11-23 5:33 ` Wolfgang Denk
2012-09-11 12:47 ` [U-Boot] Nand Flash Programing and Board Bring Up Manukumar
2012-09-11 14:10 ` Marek Vasut
2012-05-23 22:45 ` [U-Boot] Nand flash R/W,saveenv issue Scott Wood
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox