AnsweredAssumed Answered

SPI Slave Boot mode: SPI_RDY stays high

Question asked by larsk on May 17, 2017
Latest reply on Jul 24, 2017 by mat_mo

I am using an ADSP Cm403F-C in a protoype design. It worked flawlessly. Program upload worked via SPI Slave Boot mode (running from RAM) and by flashing via Segger's JLink software.

 

Just today my workflow was abruptly interrupted without me doing anything different than before.

I can see the following symtoms:

  • A) the JLink software fails to connect (see below)
  • B) after configuring the SPI Slave Boot mode (SYS_BMODE=b'10') and toggling the RESET line, the SPI_RDY pin stays high (for another prototype board it goes down to zero - as it should)

 

Symptom (A) could probably be caused by the chip being locked via its security header.

Symptom (B) is completely unexpected for me, since the SPI communication should always start to work (even with an invalid security header) in order to being able to issue the magic Bulk Erase command (0x48D0B3BA) via SPI (I used this before).

 

I checked that the voltage level of the two boot mode pins and the RESET line are properly defined (no shortcuts, toggling is possible). Thus I am sure, that all conditions for entering the SPI Slave Boot mode are met.

 

Could you give me a hint, which conditions could lead to this state? Anything else besides a broken oscillator?

 

Thank you!
Cheers,

Lars

 

 

// Output of the JLink tool while trying to connect to the device //

 

J-Link>connect
Device "ADSP-CM403BSWZ-FF" selected.


******************************
* J-Link script: Init CM408x *
******************************
TotalIRLen = 5, IRPrint = 0x01
CM408x (InitTarget): Enabling access to CPU core via TAPC
CM408x (InitTarget): Sending security key needed for CPU core access
TotalIRLen = 9, IRPrint = 0x0011
AP-IDR: 0x00000000, Type: JTAG-AP
******************************
* J-Link script: Init CM408x *
******************************
TotalIRLen = 5, IRPrint = 0x01
CM408x (InitTarget): Enabling access to CPU core via TAPC
CM408x (InitTarget): Sending security key needed for CPU core access
TotalIRLen = 9, IRPrint = 0x0011

****** Error: AP[0] selected for communication is not an AHB-AP.
******************************
* J-Link script: Init CM408x *
******************************
TotalIRLen = 5, IRPrint = 0x01
CM408x (InitTarget): Enabling access to CPU core via TAPC
CM408x (InitTarget): Sending security key needed for CPU core access
TotalIRLen = 9, IRPrint = 0x0011
******************************
* J-Link script: Init CM408x *
******************************
TotalIRLen = 5, IRPrint = 0x01
CM408x (InitTarget): Enabling access to CPU core via TAPC
CM408x (InitTarget): Sending security key needed for CPU core access
TotalIRLen = 9, IRPrint = 0x0011
Cannot connect to target.
J-Link>q

Outcomes