SD card booting T2081 processor

[sabeer]

Hi NXP Team and contributors,
I have a T2081 custom board in which i am attempting sd card booting,

rcw source settings is attached below

This is my rcw for sd card boot
T2081 (2 1) (210001 0x120c0017) (210002 0x15000000) (210003 0x00000000) (210004 0x00000000) (210005 0x6c000002) (210006 0x00008000) (210007 0x68000000) (210008 0xc1000000) (210009 0x00000000) (210010 0x00000000) (210011 0x00000000) (210012 0x000307ff) (210013 0x00000000) (210014 0x00000004) (210015 0x00000000) (210016 0x00000004)

after power on(POR) we are able to see sd_clk,
but we are not seeing any change on sd_cmd signal.

kindly suggest us if there are any issues with our settings
how do we know the processor is going to sd card boot mode.

[yipingwang]

The above RCW file is JTAG configuration file loaded through CodeWarrior.

You need to deploy RCW binary to SD card, then configure the switch settings to set the target board boot from SD card.

In u-boot source code, please modify file board/freescale/t208xqds/t2081_sd_rcw.cfg according to your custom board, then build SD boot u-boot image with T2081QDS_SDCARD_defconfig.

Then deploy the whole u-boot image with RCW at block 8 on SD card, plug in SD card to the target board and configure the switch setting to boot RCW from SD card.

[sabeer]

Hi yipingwang,

Thank you for your quick response, we tried your changes
Even though we put the correct RCW in the SD card, we suspect the SD card read is failing. How can we check whether the PBL has the correct RCW?

We are trying to connect to the target using the CodeWarrior tap debugger, but it is not connecting, saying "bad arguments to function."  What is the best way to check the core status and other registers while the PBL and the follow-up code is running?

Thanks.

[yipingwang]

After PORESET_B de-assertion, HRESET_B is de-asserted (indicating RCW is loaded successfully) and ASLEEP signal should be low (indicating PBI is loaded successfully).

In CodeWarrior please check whether your RCW is correct, please create a SRAM project and configure JTAG configuration file as the following, then check whether the SRAM project can run normally.

T2081 (2 1) (210001 0x120c0017) (210002 0x15000000) (210003 0x00000000) (210004 0x00000000) (210005 0x6c000002) (210006 0x00008000) (210007 0xfc000000) (210008 0xc1000000) (210009 0x00000000) (210010 0x00000000) (210011 0x00000000) (210012 0x000307ff) (210013 0x00000000) (210014 0x00000004) (210015 0x00000000) (210016 0x00000004)

[sabeer]

Hi Yipingwang,

Thanks for your quick response.

We were able to create and run a SRAM project successfully. Using SRAM object, we were able to configure and access DDR too. Then we proceeded to do booting from SDcard. And got struck in booting.

We create a PBL using codewarrior with the following RCW and PBI commands as given in SDK document page 1930. We put the PBL at sector 8 again using the dd command as specified by you.

aa 55 aa 55 01 0e 01 00 12 0c 00 17 15 00 00 00
00 00 00 00 00 00 00 00 6c 00 00 02 00 00 80 00
68 00 00 00 c1 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 03 87 ff 00 00 00 00 00 00 00 04
00 00 00 00 00 00 00 04 09 01 00 00 00 20 04 00
09 13 80 00 00 00 00 00 09 13 80 c0 00 00 01 00
09 01 01 00 00 00 00 00 09 01 01 04 ff f8 00 09
09 01 0f 00 08 00 00 00 09 01 00 00 80 00 00 00
09 00 0d 00 00 00 00 00 09 00 0d 04 ff f8 00 00
09 00 0d 08 81 00 00 12 09 11 00 00 80 00 04 03

We see that Processor is initializing the SD card and is reading the RCW but getting struck after that.

Is our RCW correct (are there any issues with Endianness or others)?
How to know whether the processor has got the RCW correctly. We checked from hardware wise, there are no issues on the SD card data lines or command lines.

In a related note, if we want to run this PBL or u-boot-spl from SRAM, how can we do it? If you want, I can open another thread for this query.

This is the rcw we are using for sd card booting,
T2081 (2 1) (210001 0x120c0017) (210002 0x15000000) (210003 0x00000000) (210004 0x00000000) (210005 0x6c000002) (210006 0x00008000) (210007 0x68000000) (210008 0xc1000000) (210009 0x00000000) (210010 0x00000000) (210011 0x00000000) (210012 0x000387ff) (210013 0x00000000) (210014 0x00000004) (210015 0x00000000) (210016 0x00000004)

thanks

[yipingwang · Accepted solution]

I checked t2080qds u-boot-sdcard.bin provided in the pre-built image ISO, RCW[PBI_SRC](RCW[192-195]) should be "e" rather than "6", please refer to the following.

00000000: aa55 aa55 010e 0100 0c07 0012 0e00 0000 .U.U............
00000010: 0000 0000 0000 0000 6615 0002 0000 0000 ........f.......
00000020: e810 4000 c100 0000 0000 0000 0000 0000 ..@.............
00000030: 0000 0000 0003 07fc 0000 0000 0000 0000 ................
00000040: 0000 0000 0000 0004 0901 0000 0020 0400 ............. ..
00000050: 0913 8000 0000 0000 0913 80c0 0000 0100 ................
00000060: 0901 0100 0000 0000 0901 0104 fff8 0009 ................
00000070: 0901 0f00 0800 0000 0901 0000 8000 0000 ................
00000080: 0900 0d00 0000 0000 0900 0d04 fff8 0000 ................
00000090: 0900 0d08 8100 0012 0911 0000 8000 0403 ................
000000a0: 0911 0020 2d17 0008 0911 0024 0010 0008 ... -......$....
000000b0: 0911 0028 0010 0008 0911 002c 0010 0008 ...(.......,....
000000c0: 094f c030 0000 8148 094f d030 0000 8148 .O.0...H.O.0...H
000000d0: 0900 0010 0000 0000 0900 0014 ff00 0000 ................
000000e0: 0900 0018 8100 0000 0913 8000 0000 0000 ................
000000f0: 0913 80c0 0000 0000 81fd 8000 2705 1956 ............'..

In addition, please refer to "Figure 4-1. Power-on reset sequence" in T2080RM, After PORESET_B de-assertion, HRESET_B is de-asserted (indicating RCW is loaded successfully) and ASLEEP signal should be low (indicating PBI is loaded successfully).

Please configure JTAG configuration file as the following in CodeWarrior IDE  to verify whether your RCW is configured correctly.

T2081 (2 1) (210001 0x120c0017) (210002 0x15000000) (210003 0x00000000) (210004 0x00000000) (210005 0x6c000002) (210006 0x00008000) (210007 0xfc000000) (210008 0xc1000000) (210009 0x00000000) (210010 0x00000000) (210011 0x00000000) (210012 0x000307ff) (210013 0x00000000) (210014 0x00000004) (210015 0x00000000) (210016 0x00000004)