AWR1642: Why the QSPI flash start access from 22ms after Nreset?

Wesley He

Expert 6205 points

Part Number: AWR1642

Hello team,

Customer request to send out 1 CAN package <50ms while power up. So it will be a big challenge on the boot time.

But during my test, i only load SDK3.4 1642_SBL.BIN on AWR1642EVM,

And you can see in attach waveform, it will take ~22ms for 1642 to start read something from QSPIFLASH.

Questions:

1. Why the warm reset deasserted 7.08ms later than the Nreset deasserted?

2. Why it take 15ms for 1642 to start read somthing from QSPI flash.

3. Is it any method to send out 1 CAN package <50ms while power up on 1642?

Thanks.

Regards,

Wesley

over 4 years ago

0 Jitendra Gupta over 4 years ago

TI__Guru 69990 points

Hi Wesley,

Let me forward this thread to my colleague who can assist you better on this.

Regards,

Jitendra

+1 Vivek Dham over 4 years ago

TI__Guru 58035 points

Hello Wesley,

There is about 7 msec of HW power up + xtal osc build up time, this is what is reflected by the warm reset. Post that the boot loader execution starts which includes all the clk configurations, memory inits, safety checks etc. and only then the application load from flash starts. Hence it take 22msec.

Regards,
Vivek

0 Wesley He over 4 years ago in reply to Vivek Dham

TI__Expert 6205 points

Hi Vivek,

Thanks. That make sense.

Is it any method to send out 1 CAN package <50ms while power up on 1642?

Can we seperate the binary?

Regards,

Wesley

0 Vivek Dham over 4 years ago in reply to Wesley He

TI__Guru 58035 points

Hello Wesley,

They could try to have a very small application that just sends the CAN packet, this could get loaded first. Then they could load their main application.

Regards,vivek

Sensors

Sensors forum

AWR1642: Why the QSPI flash start access from 22ms after Nreset?