flash error on T1042 based customized board using code warrior tap

[Abubakar]

Hi,

I am trying to bring up T1042 based customized board with nothing flashed on the nor flash. As a first step, I am flashing RCW on it using code warrior tap by following way:

I am running the board on the hardcoded RCW setting using dip switches and flashing the customized RCW using code warrior bare board project but it fails to initialize the target with following error on console:

fl::target -lc "flashing_kit-core00_RAM_T1042_Download"
fl::target -b 0x0 0x5130
fl::target -v off -l off
cmdwin::fl::device -d "JS28F00AM29EWL" -o "64Mx16x1" -a 0xe8000000 0xefffffff
cmdwin::fl::image -f "C:\\Users\\CW\\Desktop\\code warrior projects\\flashing kit\\rcw.bin" -t "Auto Detect" -re on -r 0xe8000000 0xefffffff -oe on -o 0xeff40000
cmdwin::fl::erase image
Beginning Operation ...
-------------------------
Auto-detection is successful.
File is of type Binary/Raw Format.

Performing target initialization ...
failed on register write: L2MMU_CAM1
failed on register write: L2MMU_CAM2
failed on register write: L2MMU_CAM3
failed on register write: L2MMU_CAM4
failed on register write: L2MMU_CAM5
Error writing memory
[CCS last error: Scan timeout ](CCSProtocolPlugin)
Error: invalid input value
Error: Couldn't stop the target. Can't stop the target.
Error: Couldn't stop the target.Can't stop the target.

The related error images are attached  as well.

In this case, no rcw is present on board as i am bringing up a new board. Can you please tell me why am I getting these errors?

[Abubakar]

The problem is solved by forced RCW mode in code warrior using the customized RCW file in the target option.

[Abubakar]

1) Yes, TRST_B is managed and asserted on power on reset sequence.

2) I had verified some of the signals but am not sure which particular reset signals you are talking about. Can you elaborate?

3) Sorry I cannot share them due to company policy but they are the same as in the t1042d4rdb reference kit.

Recently, I encountered another error while flashing in which the erase command was succeeded but error occurred on flashing. The console output is below:

fl::target -lc "jtag_flash-core00_RAM_T1042_Download"
fl::target -b 0x0 0x5130
fl::target -v off -l off
cmdwin::fl::device -d "JS28F00AM29EWL" -o "128Mx8x1" -a 0xe8000000 0xefffffff
cmdwin::fl::image -f "C:\\Users\\CW\\Desktop\\mydtb_spi_disable.dtb" -t "Auto Detect" -re on -r 0xe8000000 0xefffffff -oe on -o 0xe8000000
cmdwin::fl::erase image
Beginning Operation ...
-------------------------
Auto-detection is successful.
File is of type Binary/Raw Format.

Performing target initialization ...
Downloading Flash Device Driver ...
Reading flash ID ...
Erasing Sector 0xE8000000 to 0xE801FFFF
Erasing ...
Erase Command Succeeded
cmdwin::fl::write verify
-------------------------
Using restricted address range 0xE8000000 to 0xEFFFFFFF
Programming file C:\Users\CW\Desktop\mydtb_spi_disable.dtb
Auto-detection is successful.
File is of type Binary/Raw Format.

Downloading Flash Device Driver ...
Reading flash ID ...
Auto-detection is successful.
File is of type Binary/Raw Format.

Downloading 0x00001BA0 bytes to be programmed at 0xE8000000
Executing program with verify ....
Error: Program with Verify failed. Flash driver reports the following error(s): Chip reported error during program. Pleasecheck that the sector you are programming is erased.

Error: Program with Verify failed. Flash driver reports the following error(s): Chip reported error during program. Please check
that the sector you are programming is erased.

[ufedor]

2) Please refer to the QorIQ T1040 Reference Manual, Figure 4-1. Power-on reset sequence.

[ufedor]

Please provide additional information:

1) Confirm that TRST_B is pulsed low (asserted) during power-on reset sequence;

2) A digital scope trace(s) showing behavior of all reset signals when hard-coded RCW option is selected;

3) The processor connection schematics as searchable PDF.