TDA4VM: [ TDA4 Platfotm ] How to use JTAG creating boot binary in eMMC (boot0)

Hi Gibbs,

1. Do you have SD boot available on the custom board you have? if yes, then we can boot u-boot from there and then use u-boot utilities to flash the eMMC boot0.

2. Do you have a Lauterbach? If yes, we can use this to flash.

3. When you say your UART is broken, is this the MCU UART? UNIFLASH needs MCU UART.

Regards,

Karan

Hi,  Karan :

Happy New Year.

>> 1. Do you have SD boot available on the custom board you have? if yes, then we can boot u-boot from there and then use u-boot utilities to flash the eMMC boot0.

Our board do not have SD interface.

>>2. Do you have a Lauterbach? If yes, we can use this to flash.

No, but our board kept JTAG port, could we use XDS1011?

>>3. When you say your UART is broken, is this the MCU UART? UNIFLASH needs MCU UART.

Yes, we use MCU uart, the program halt whan "tispl.bin" burning, log as below :

C:\ti\uniflash_6.1.0\processors>burn1.bat

C:\ti\uniflash_6.1.0\processors>echo "Prepare Burnning eMMC"
"Prepare Burnning eMMC"

C:\ti\uniflash_6.1.0\processors>pause.

C:\ti\uniflash_6.1.0\processors>ProcessorSDKSerialFlash -c COM26 -f c:\ti\uniflash_6.1.0\processors\FlashWriter\j721e_evm\uart_j721e_evm_flash_programmer_release.tiimage -i 0

----------------------------------------------------------------------------
ProcessorSDKSerialFlash CLI Tool
Copyright (C) 2017-2020 Texas Instruments Incorporated - http://www.ti.com/
Version 1.3.0.0
----------------------------------------------------------------------------
Downloading Flash Programmer..

Transferring File of size 215005 bytes
File Transfer complete!

Enabling SysFw transfer!!!
Header Transfer complete
Transferring System Firmware..
Transferring File of size 263083 bytes
File Transfer complete!

C:\ti\uniflash_6.1.0\processors>ProcessorSDKSerialFlash -c COM26 -f c:\ti\uniflash_6.1.0\processors\FlashWriter\j721e_evm\tiboot3.bin -d 4 -o 0

----------------------------------------------------------------------------
ProcessorSDKSerialFlash CLI Tool
Copyright (C) 2017-2020 Texas Instruments Incorporated - http://www.ti.com/
Version 1.3.0.0
----------------------------------------------------------------------------
Transferring the Image to Flash Programmer..

Transferring Header Information..
Header Transfer Complete!
Failure: Canceled by remote !!

C:\ti\uniflash_6.1.0\processors>ProcessorSDKSerialFlash -c COM26 -f c:\ti\uniflash_6.1.0\processors\FlashWriter\j721e_evm\tispl.bin -d 4 -o 80000

----------------------------------------------------------------------------
ProcessorSDKSerialFlash CLI Tool
Copyright (C) 2017-2020 Texas Instruments Incorporated - http://www.ti.com/
Version 1.3.0.0
----------------------------------------------------------------------------
Transferring the Image to Flash Programmer..

(programmer halt .... )

After few days debug for software, I try to compare our hardware with TDA4 EVB board (MCU UART PORT), we loss  this pin "2P_FTDI_RXR_OE"  connection,  is this pin necessary?!

(appendix file)

Thanks

Gibbs

Hi Gibbs,

Gibbs Shih said:

After few days debug for software, I try to compare our hardware with TDA4 EVB board (MCU UART PORT), we loss  this pin "2P_FTDI_RXR_OE"  connection,  is this pin necessary?!

I need to check this. In the meantime, I'd like to check a couple of other things.

1. Why are you not using the pre-built dslite.bat script in the UNIFLASH?

dslite.bat --mode processors -c COM7 -f C:\ti\uniflash_5.3.1\processors\FlashWriter\j721e_evm\uart_j721e_evm_flash_programmer_release.tiimage -i 0
dslite.bat --mode processors -c COM7 -f <PATH_TO_IMAGES>\tiboot3.bin -d 4 -o 0
dslite.bat --mode processors -c COM7 -f <PATH_TO_IMAGES>\tispl.bin -d 4 -o 80000
dslite.bat --mode processors -c COM7 -f <PATH_TO_IMAGES>\u-boot.img -d 4 -o 280000
dslite.bat --mode processors -c COM7 -f <PATH_TO_IMAGES>\sysfw.itb -d 4 -o 6C0000

2. Can you please confirm that you are in UART boot mode when you flash these? Please open the MCU UART (2nd Instance of the 2) and you should see the characters "CCCC....." being printed there.

3. When you validate 2 can you need to close the serial console (teraterm, putty etc..) for the MCU UART and then physically unplug and plug back the USB cable from the HOST machine (this is a known issue on Windows because of which you need to do this).

Regards,

Karan

Hi, Karan :

>> I need to check this. In the meantime, I'd like to check a couple of other things.

we modified this hardware & corrected pin connect  today, but it doesn't work.

>> 1. Why are you not using the pre-built dslite.bat script in the UNIFLASH?

When I use "dslite.bat script" in MS-DOS, it always return command not found (could be environment variable problems for my laptop).

But I am very sure, this script call execution  "C:\ti\uniflash_6.1.0\processors>ProcessorSDKSerialFlash.exe", and "ProcessorSDKSerialFlash" works on EVB, parameter are the same!

2. Can you please confirm that you are in UART boot mode when you flash these? Please open the MCU UART (2nd Instance of the 2) and you should see the characters "CCCC....." being printed there.

Yes, board in uart boot mode, and the char "C" appears!

3. When you validate 2 can you need to close the serial console (teraterm, putty etc..) for the MCU UART and then physically unplug and plug back the USB cable from the HOST machine (this is a known issue on Windows because of which you need to do this).

Yes, after step2, I checked it,  you must  "reset board" or "re-plug " usb uart interface, and then ROM code into programming mode

BTW, we also change eMMC size, our board is "MTFC32GAPALBH-AAT" (32G), EVB is "MTFC16GAPALBH-AAT" (16G), any effect ?!

Many Thanks

Gibbs

Update Status,

We try to add SD interface on our board, and switch to SD boot.

Boot loader works, but new error occurs, message as below :

"Timeout during frequency handshake", and system hangs. it seems DDR problems.

Our board DDR chip (MT53D1024M32D4DT)  is same as TDA4 EVB board, 

Any Comments?

HI Gibbs,

Gibbs Shih said:

When I use "dslite.bat script" in MS-DOS, it always return command not found (could be environment variable problems for my laptop).

But I am very sure, this script call execution  "C:\ti\uniflash_6.1.0\processors>ProcessorSDKSerialFlash.exe", and "ProcessorSDKSerialFlash" works on EVB, parameter are the same!

No need to change the environment variables, but you need to go to the C:\ti\uniflash_6.1.0 directory to execute that. You will see the dslite.bat script there.

Gibbs Shih said:

Yes, board in uart boot mode, and the char "C" appears!

This shows that the bootmode is correctly set to UART boot mode.

Gibbs Shih said:

Yes, after step2, I checked it,  you must  "reset board" or "re-plug " usb uart interface, and then ROM code into programming mode

After closing the serial to UART displaying CCCC... You need to power off the board, unplug that UART cable from the PC and then plug back and power on the board.

Gibbs Shih said:

BTW, we also change eMMC size, our board is "MTFC32GAPALBH-AAT" (32G), EVB is "MTFC16GAPALBH-AAT" (16G), any effect ?!

I need to check this.

On a follow up though, you do not have MAIN UART pinned on you board?

Regards,

Karan