AM623: AM623 GPMC NAND boot issue

Jomon Thomas

Prodigy 160 points

Part Number: AM623
Other Parts Discussed in Thread: SK-AM62B-P1, SK-AM62-LP

Tool/software:

Hi,

I am Woking on a custom AM623 board with GPMC-NAND.

NAND Flash Part Number is MT29F2G08ABBGAH4-IT:G

I have followed below forum link to compile and download the binaries.

[FAQ] How to flash u-boot to GPMC-NAND with USB-DFU on AM62x - Processors forum - Processors - TI E2E support forums.

I have done the following procedure:

1) compiled tiboot3.bin tispl.bin u-boot.img as per the forum mentioned above

2) For testing purpose, I used this tiboot3.bin with SK-AM62B-P1 (just make sure the binary is proper and working condition). The EVK boot logs added below

U-Boot SPL 2024.04-dirty (Jan 11 2025 - 16:37:13 +0530)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
SPL initial stack usage: 13392 bytes
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

This is what I expected. At the time of reset tiboot3 is started to work (some print is coming) but getting error due to NAND unavailability in the EVK

3) In next step I have flashed the same binary to the Custom board GPMC-NAND flash (0x00 and 0x400000 locations). and verified binaries using u-boot "cmp" commands

4) Also verified the BOOTMODE using below command

=> md.w 0x43000030 1
43000030: 045b

5) Reset the board, but no message is coming through the serial UART. But still I can able to boot with DFU

In my understanding I have flashed tiboot3 to the NAND but due to some unknown reason, processor not able to load and boot form the GPMC-NAND and it goes to backup boot mode (DFU).

6) For the further analysis I have tried to read the ROM code "Warning/Error logs" (TRM Section 5.8) using the DFU loaded u-boot. And it is showing some values, but I didn't get any idea of how to decode this log.

=> md.b 0x43c3e680 0x200 
43c3e680: fe 82 80 41 d6 00 00 00 82 4e 41 4e 00 00 00 00  ...A.....NAN....
43c3e690: e3 04 00 00 00 00 00 00 fe 82 80 41 40 02 00 00  ...........A@...
43c3e6a0: 83 4e 41 4e 00 00 00 00 e7 04 00 00 00 00 00 00  .NAN............
43c3e6b0: 50 82 80 41 70 01 00 00 04 00 00 00 00 00 00 00  P..Ap...........
43c3e6c0: e9 04 00 00 00 00 00 00 e5 81 80 41 df 0a 00 00  ...........A....
43c3e6d0: ff ff ff ff 00 00 00 00 ef 04 00 00 00 00 00 00  ................
43c3e6e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e6f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e710: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e720: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e730: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e740: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e750: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e760: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e770: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e790: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e7a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e7b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e7c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e7d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e7e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e7f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e810: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e820: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e830: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e840: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e850: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e860: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
43c3e870: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

My Questions is:

1) How to decode ROM code "Warning/Error logs" mentioned in the (TRM Section 5.8)?

2) We are using a 2 plane NAND for this booting purpose. And "AM62x Sitara Errata (Rev. F)" document mentioned "2372 — ROM doesn't support select multi-plane addressing schemes in Serial NAND boot". Is it applicable to GPMC parallel NAND Booting?

7 months ago

0 RJ DJ 7 months ago

Intellectual 396 points

Hi Ti Team ,

Any input is appreciated !.

Regards,

-RJ

0 Hong Guan64 7 months ago in reply to RJ DJ

TI__Guru 68430 points

The steps 1) to 6) looks good to me.
1/. what is the device type on your board?
2/. have we flashed the matching tiboot3.bin to gpmc-nand?
Best,
-Hong

0 Jomon Thomas 7 months ago in reply to Hong Guan64

Prodigy 160 points

1/. what is the device type on your board?

Processor: AM6231AKGGHHALW
Nand flash: MT29F2G08ABBGAH4-IT:G

2/. have we flashed the matching tiboot3.bin to gpmc-nand?

yes we followed following link and used am62x_lpsk_r5_gpmc_defconfig for generating tiboot3.bin

e2e.ti.com/.../faq-how-to-flash-u-boot-to-gpmc-nand-with-usb-dfu-on-am62x

We did the following steps:

1) compiled the tiboot3.bin binary with am62x_lpsk_r5_gpmc_defconfig

2) booted custom board with another "dfu enabled binaries"

3) loaded and flashed "am62x_lpsk_r5_gpmc_defconfig" based tiboot3.bin in to the NAND flash

4) verified flashed area using u-boot cmp commands

5) verified the boot pins by reading the register (md.w 0x43000030 1 )

6) rebooted the board but no print is coming. and processor is goes in to the secondary DFU mode

Initially we are not expecting a complete booting of u-boot/linux but we are just looking a print message form NAND based "R5 SPL" to make sure the ROM code can able to identify the NAND device as boot media and start execution form the NAND based tiboot3.bin but it is not happening. Processor is entering to the DFU boot mode. Also it generating the ROM code "Warning/Error logs" as per the Technical Reference Manual section 5.8.

0 Hong Guan64 7 months ago in reply to Jomon Thomas

TI__Guru 68430 points

Hi Jomon,
Your steps looks good to me.
I'd like to confirm one thing

Jomon Thomas said:
3) loaded and flashed "am62x_lpsk_r5_gpmc_defconfig" based tiboot3.bin in to the NAND flash

What is the device type? HS-FS, HS-SE or GP?
Have we flashed to gpmc-nand the tiboot3.bin built for the matching device type?
Best,
-Hong

0 Jomon Thomas 7 months ago in reply to Hong Guan64

Prodigy 160 points

This device is a HS-FS device.

SDK used: ti-processor-sdk-linux-am62xx-evm-10.00.07.04

tiboot3-am62x-hs-fs-evm.bin - this is the tiboot3.bin (am62x_lpsk_r5_gpmc_defconfig" based) i used to flash in to the NAND.

Please find the attached logs below

Fullscreen hostlog.txt Download

user1@Linux:~/tisdk/board-support/u-boot-build/bin/nand$ sudo dfu-util -l
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Found DFU: [0451:6165] ver=0223, devnum=72, cfg=1, intf=0, path="1-1", alt=2, name="u-boot.img", serial="0000000000000000"
Found DFU: [0451:6165] ver=0223, devnum=72, cfg=1, intf=0, path="1-1", alt=1, name="tispl.bin", serial="0000000000000000"
Found DFU: [0451:6165] ver=0223, devnum=72, cfg=1, intf=0, path="1-1", alt=0, name="tiboot3.bin", serial="0000000000000000"


user1@Linux:~/tisdk/board-support/u-boot-build/bin/nand$ sudo dfu-util -a 0 -D tiboot3-am62x-hs-fs-evm.bin
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0451:6165
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 4096
Copying data from PC to DFU device
Download	[=========================] 100%       323062 bytes
Download done.
state(7) = dfuMANIFEST, status(0) = No error condition is present
state(2) = dfuIDLE, status(0) = No error condition is present
Done!


user1@Linux:~/tisdk/board-support/u-boot-build/bin/nand$ sudo dfu-util -a 1 -D tispl.bin
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0451:6165
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #1 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 4096
Copying data from PC to DFU device
Download	[=========================] 100%      1111383 bytes
Download done.
state(7) = dfuMANIFEST, status(0) = No error condition is present
state(2) = dfuIDLE, status(0) = No error condition is present
Done!


user1@Linux:~/tisdk/board-support/u-boot-build/bin/nand$ sudo dfu-util -a 2 -D u-boot.img
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0451:6165
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #2 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 4096
Copying data from PC to DFU device
Download	[=========================] 100%      1004467 bytes
Download done.
state(7) = dfuMANIFEST, status(0) = No error condition is present
state(2) = dfuIDLE, status(0) = No error condition is present
Done!

Fullscreen Devicelog.txt Download

U-Boot 2024.04-dirty (Jan 02 2025 - 14:12:20 +0530)

SoC:   AM62X SR1.0 HS-FS
Model: Texas Instruments AM625 SK
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -19
DRAM:  1 GiB
Core:  59 devices, 30 uclasses, devicetree: separate
NAND:  256 MiB
MMC:   mmc@fa10000: 0
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -121
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0 
=> nand erase.chip

NAND erase.chip: device 0 whole chip
Erasing at 0xffe0000 -- 100% complete.
OK
=> setenv dfu_alt_info "tiboot3.bin raw 0x0 0x200000; tispl.bin raw 0x200000 0x400000; u-boot.img raw 0x600000 0xA00"
=> dfu 0 mtd nand0
generic_phy_get_bulk : no phys property
###DOWNLOAD ... OK
Ctrl+C to exit ...
#########DOWNLOAD ... OK
Ctrl+C to exit ...
########DOWNLOAD ... OK
Ctrl+C to exit ...
=>

I followed below procedure for an experiment:

1) Put the device in DFU mode

2) Send the "am62x_lpsk_r5_gpmc_defconfig" based tiboot3-am62x-hs-fs-evm.bin to the device

3) and i got the following log on the device console

    U-Boot SPL 2024.04-dirty (Jan 16 2025 - 12:31:26 +0530)
    SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
    SPL initial stack usage: 13392 bytes
    SPL: failed to boot from all boot devices
    ### ERROR ### Please RESET the board ###

The same tiboot3.bin is started to run and generated some print message even if the configuration is mismatching.

0 Hong Guan64 7 months ago in reply to Jomon Thomas

TI__Guru 68430 points

Jomon Thomas said:
tiboot3-am62x-hs-fs-evm.bin - this is the tiboot3.bin (am62x_lpsk_r5_gpmc_defconfig" based) i used to flash in to the NAND.

Can you share the tiboot3.bin you built for gpmc-nand, and flashed to gpmc-nand on your board?
Best,
-Hong

0 Jomon Thomas 7 months ago in reply to Hong Guan64

Prodigy 160 points

How can i share bin file, i have tried to attach to this chat but not working

0 Hong Guan64 7 months ago in reply to Jomon Thomas

TI__Guru 68430 points

Have we tried uploading the file by clicking the "Insert" button, and selecting "Image/video/file"...?
Best,
-Hong

0 Jomon Thomas 7 months ago in reply to Hong Guan64

Prodigy 160 points

tiboot3-am62x-hs-fs-evm.txt
Actually i cant able to upload .bin files(not showing the file one i click upload button). So i changed its name from "tiboot3-am62x-hs-fs-evm.bin" to "tiboot3-am62x-hs-fs-evm.txt" and it uploaded now

+1 Hong Guan64 7 months ago in reply to Jomon Thomas

TI__Guru 68430 points

I flashed your "tiboot3-am62x-hs-fs-evm.bin" to gpmc-nand on TI nand daughter card along with SK-AM62-LP board, and the gpmc-nand booted up as shown in the attached log.
1/. did you build your shared "tiboot3-am62x-hs-fs-evm.bin" for SK-AM62-LP or your customer board?
2/. It looks like the issue on your customer board might be your HW/board related. You may want to check gpmc-nand reset in regards to SoC POR.
Best,
-Hong

Fullscreen am62-lpsk_e2e_nand_flash_boot.log Download

U-Boot SPL 2024.04-00002-g85fca2d6-dirty (Oct 11 2024 - 10:05:39 -0500)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
SPL initial stack usage: 13392 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE:  BL31: Built : 16:09:05, Feb  9 2024

U-Boot SPL 2024.04-00002-g85fca2d6-dirty (Oct 11 2024 - 10:06:11 -0500)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
SPL initial stack usage: 1904 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed


U-Boot 2024.04-00002-g85fca2d6-dirty (Oct 11 2024 - 10:06:11 -0500)

SoC:   AM62X SR1.0 HS-FS
Model: Texas Instruments AM62x LP SK
EEPROM not available at 0x50, trying to read at 0x51
Board: AM62-LP-SKEVM rev E2
DRAM:  2 GiB
Core:  83 devices, 32 uclasses, devicetree: separate
NAND:  1024 MiB
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  2  0 
=> md.l 0x43000030 1
43000030: 00000243                             C...
=> mtd list
List of MTD devices:
* nand0
  - device: nand@0,0
  - parent: memory-controller@3b000000
  - driver: gpmc-nand
  - path: /bus@f0000/memory-controller@3b000000/nand@0,0
  - type: NAND flash
  - block size: 0x40000 bytes
  - min I/O: 0x1000 bytes
  - OOB size: 128 bytes
  - OOB available: 142 bytes
  - ECC strength: 8 bits
  - ECC step size: 512 bytes
  - bitflip threshold: 6 bits
  - 0x000000000000-0x000040000000 : "nand0"
	  - 0x000000000000-0x000000200000 : "NAND.tiboot3"
	  - 0x000000200000-0x000000400000 : "NAND.tispl"
	  - 0x000000400000-0x000000600000 : "NAND.tiboot3.backup"
	  - 0x000000600000-0x000000a00000 : "NAND.u-boot"
	  - 0x000000a00000-0x000000a40000 : "NAND.u-boot-env"
	  - 0x000000a40000-0x000000a80000 : "NAND.u-boot-env.backup"
	  - 0x000000a80000-0x000040000000 : "NAND.file-system"
* spi-nand0
  - device: flash@0
  - parent: spi@fc40000
  - driver: spi_nand
  - path: /bus@f0000/bus@fc00000/spi@fc40000/flash@0
  - type: NAND flash
  - block size: 0x40000 bytes
  - min I/O: 0x1000 bytes
  - OOB size: 128 bytes
  - OOB available: 80 bytes
  - 0x000000000000-0x000008000000 : "spi-nand0"
	  - 0x000000000000-0x000000080000 : "ospi_nand.tiboot3"
	  - 0x000000080000-0x000000280000 : "ospi_nand.tispl"
	  - 0x000000280000-0x000000680000 : "ospi_nand.u-boot"
	  - 0x000000680000-0x0000006c0000 : "ospi_nand.env"
	  - 0x0000006c0000-0x000000700000 : "ospi_nand.env.backup"
	  - 0x000002000000-0x000007fc0000 : "ospi_nand.rootfs"
	  - 0x000007fc0000-0x000008000000 : "ospi_nand.phypattern"
=> nand erase 0x0 0x200000

NAND erase: device 0 offset 0x0, size 0x200000

Erasing at 0x0 --  12% complete.
Erasing at 0x40000 --  25% complete.
Erasing at 0x80000 --  37% complete.
Erasing at 0xc0000 --  50% complete.
Erasing at 0x100000 --  62% complete.
Erasing at 0x140000 --  75% complete.
Erasing at 0x180000 --  87% complete.
Erasing at 0x1c0000 -- 100% complete.
OK
=> ls mmc 1 nand_e2e
            ./
            ../
   323062   tiboot3-am62x-hs-fs-evm.bin

1 file(s), 2 dir(s)

=> load mmc 1 ${loadaddr} nand_e2e/tiboot3-am62x-hs-fs-evm.bin
323062 bytes read in 38 ms (8.1 MiB/s)
=> nand write ${loadaddr} 0x0 ${filesize}

NAND write: device 0 offset 0x0, size 0x4edf6
 323062 bytes written: OK
=> mw.l 0x43000030 0x045B
=> md.l 0x43000030 1
43000030: 0000045b                             [...
=> reset
resetting ...

U-Boot SPL 2024.04-dirty (Jan 17 2025 - 12:00:45 +0530)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
SPL initial stack usage: 13392 bytes
Trying to boot from NAND
Authentication passed
Authentication passed
Authentication passed
Loading Environment from nowhere... OK
init_env from device 11 not supported!
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE:  BL31: Built : 16:09:05, Feb  9 2024

U-Boot SPL 2024.04-dirty (Aug 16 2024 - 15:52:09 -0500)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
SPL initial stack usage: 1904 bytes
Trying to boot from NAND
Authentication passed
Authentication passed


U-Boot 2024.04-dirty (Aug 16 2024 - 15:52:09 -0500)

SoC:   AM62X SR1.0 HS-FS
Model: Texas Instruments AM62x LP SK
EEPROM not available at 0x50, trying to read at 0x51
Board: AM62-LP-SKEVM rev E2
DRAM:  2 GiB
ti_sci_probe(dev=00000000fd59ff30)
ti_sci system-controller@44043000: ti_sci_of_to_info: Acquiring notify channel failed. ret = -61
>>>> ti_sci_setup_ops(core_ops->get_soc_uid=00000000ff60b574)
Core:  83 devices, 32 uclasses, devicetree: separate
NAND:  1024 MiB
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  2  0 
=> md.l 0x43000030 1
43000030: 0000045b                             [...
=>

0 Jomon Thomas 7 months ago in reply to Hong Guan64

Prodigy 160 points

1/. did you build your shared "tiboot3-am62x-hs-fs-evm.bin" for SK-AM62-LP or your customer board?

We don't have a SK-AM62-LP in our hand we are testing with custom AM623 board and SK-AM62B-P1 EVK
This particular binary is based on SK-AM62-LP, we used UBOOT_MACHINE_R5 as am62x_lpsk_r5_gpmc_defconfig in the SDK Rules.make file and no other code change. This is the same binary i used in DFU experiment on the custom board and i got print messages on the console.
Also i did another tisdk build with custom configuration, in R5 SPL perspective the main change is only DDR memory size. but getting the same result.

2/. It looks like the issue on your customer board might be your HW/board related. You may want to check gpmc-nand reset in regards to SoC POR.
Best,

In our custom board contains both EMMC and NAND flash, we already achieved EMMC based booting with out any problem. what we are trying is to make NAND booting is up and remove EMMC for further development but it is not working. And our observation is once the u-boot/linux is up we can able to access the NAND flash, ubi ubifs file system creation, writing reading files everything is working.
I will check more about nand reset sequence. But still my main doubt is about NAND flash multi-plane support can you please verify it? is this AM623 ROM code support multi-plane addressing schemes in parallel NAND boot? i am attaching ROM code version details below.
Fullscreen ROM_Code_Version.txt Download
```
=> md.b 0x4182FF80 0x4    (Version Number)
4182ff80: 01 00 01 00                                      ....



=> md.b 0x4182FF84 0x8   (Version Date)
4182ff84: 31 30 2f 32 36 2f 32 31                          10/26/21
=>



=> md.b 0x4182FF8C 0xC  (Device Name)
4182ff8c: 61 6d 36 32 78 00 00 00 00 00 00 00              am62x.......
=>



=> md.b 0x4182FF98 0x28  (Commit ID)
4182ff98: 35 61 37 36 62 32 36 35 61 31 65 37 31 38 64 66  5a76b265a1e718df
4182ffa8: 35 34 65 61 34 63 65 30 36 38 37 38 66 36 37 65  54ea4ce06878f67e
4182ffb8: 39 38 31 35 64 35 38 39                          9815d589
```

0 Jomon Thomas 7 months ago in reply to Hong Guan64

Prodigy 160 points

Thanks for the suggestions, NAND is started to work.

0 Hong Guan64 7 months ago in reply to Jomon Thomas

TI__Guru 68430 points

Hi Jomon,
It is good to know gpmc-nand boot started working on your setup.
Will you share what changes you added?
Best,
-Hong

0 Jomon Thomas 7 months ago in reply to Hong Guan64

Prodigy 160 points

Issue is with R/B pin pull-up resistor, it wasn't soldered properly.

0 Hong Guan64 7 months ago in reply to Jomon Thomas

TI__Guru 68430 points

Thanks Jomon for your reply.
Yes, "Ready/Busy is implemented as an open drain circuit, thus a pull-up resistor shall be used for termination." as specified in the ONFI specification.
Best,
-Hong