TDA2HF: [TDA2x]: SPI and QSPI issue from TDA to NOR flash

Myat Zin

Part Number: TDA2HF

HI,

Recently, I have noticed this issue while during SBL boot-up, TDA2x cannot successfully bootup and goes into boot abort. I want to investigate if it is hardware or software issues as this is not observed in good sample, only in a few bad sample.

I checked the possibility of boot abort and it is possible in the cases of ENGINE_v_FillUnusedDDR or ENGINE_v_ImageCopy fails. I am using driver provided by TI such as bl_engine.c to initialize QSPI and read sectors using QSPI.

I am suspecting TDA2x cannot successfully read form NOR flash using QSPI that's why it goes into boot abort.

I have attached a snippet as below and I saw TDA_CLK and NOR_CLK lines are all dead. Does the clock initialization and pulses generation will be done during QSPI initialization or does it supposed to come from external hardware like crystal/ oscillator?

over 4 years ago

0 Prasad Konnur over 4 years ago

TI__Expert 6065 points

Hi,

Which software/version are you using?

Regards,

Prasad

0 Myat Zin over 4 years ago in reply to Prasad Konnur

Intellectual 540 points

Hi Prasad,

I am using starterware 01_04 version.

0 Prasad Konnur over 4 years ago in reply to Myat Zin

TI__Expert 6065 points

Hi,

Are you using the TI EVM or the custom board?
Which example/testapp are you using to access the QSPI memory?

Also in the waveform you attached there is a TDA_CLK/CS and NOR_CLK/CS, what is the difference between these lines?

Regards,
Prasad

0 Myat Zin over 4 years ago in reply to Prasad Konnur

Intellectual 540 points

HI,

I am using the custom board. I am using api from qspiflash_driver.c to initialize and read sectors from NOR flash.

NOR_CLK/CS are signals from TDA to NOR flash and TDA_CLK/CS are another SPI signal from TDA to another controller.

I am having doubt if SBL is stuck in while loop while waiting for EVE core to boot-up. Is there anything from hardware point which can prevents EVE core from booting-up?

// Enable EVE1 core
u32ErrBitVector = mGetExeErrorBitset((SBLLibEVE1BringUp(entryPoint_EVE1, sblBuildMode) == 0), 0);
SBLAppRecordWarnings("SBLLibEVE1BringUp", u32ErrBitVector, nWarningCheck);

0 Prasad Konnur over 4 years ago in reply to Myat Zin

TI__Expert 6065 points

Hi,

The issue you are facing is when you are trying to boot using the QSPI bootmode right?
Were you able to flash the sbl and the application images in the QSPI flash?

Regards,
Prasad

0 Myat Zin over 4 years ago in reply to Prasad Konnur

Intellectual 540 points

HI, at first I thought it was the QSPI problem while SBL was trying to read application images from NOR flash.

Now, I think SBL has successfully read the application images in the NOR flash. Unfortunately, when it tries to reset and bring up the EVE core, it gets stuck there while waiting for EVE core to read the shared variable.

I would like to understand is there anything that can prevents EVE core from coming out of reset? I have tried to connect using debugger but it is to no effort as core are in reset mode.

Please kindly advise. Thank you.

0 Karthik Ramanan over 4 years ago in reply to Myat Zin

TI__Guru** 113800 points

Hi Myat,

Since we have an ongoing discussion separately, I'm closing this thread since it is a duplicate here.

Regards

Karthik

Processors

Processors forum

TDA2HF: [TDA2x]: SPI and QSPI issue from TDA to NOR flash