• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 30 subscribers
  • Views 421 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AWR2243: RF Initialization/Calibration failed with error code -8

radar_pete
Intellectual 400 points
Part Number: AWR2243
Other Parts Discussed in Thread: MMWCAS-RF-EVM,

Tool/software:

Hello,

We are having an issue with some custom cascade boards that we designed based on the MMWCAS-RF-EVM board. Note that we are controlling the chips from an MCU. On recent board builds we have observed the below issue occurring intermittently whereby we get this error - 'RF Initialization/Calibration failed with error code -8'. This seems to be what the error code refers to:
#define RL_RET_CODE_RESP_TIMEOUT            (-8)        /* device failed to send response within time */

Just to note that we are power cycling before running this initialization code so RF Init is only being called once per power cycle. The issue happens intermittently and at random numbers of power cycles - for instance on one occasion after 16 successful initializations or another occasion after the 5th successful initialization. It has been observed in multiple recent builds but hadn't been observed before this to the best of our knowledge (and this part of radar chip initialization code hadn't changed in that time). 

We realise that as per the app note relating to this, in a cascade system we should really only be running RF Init once at the factory during radar assembly/calibrations and then applying these coefficients from then on. We plan to implement this in future but for now are running it each time at power on. 

Is this likely to be a hardware issue (such as a problem with these specific AWR2243 chips or a PCB assembly issue) or a software issue do you think? Are there any next steps we can take to debug further?

Best regards,

Peter.

Device map 1 : mmWave Device Power on success

Device map 1 : CRC Type set for MasterSS success

Device map 1 : BSS Power Up Async event

Device map 1 : RF Version [ 2. 2. 0.13] 
Device map 1 : MSS version [ 2.  2. 1.  7] 
Device map 1 : mmWaveLink version [ 2. 2. 3. 2]

Device map 1 : RF Patch Version [ 2. 2. 3. 3] 
Device map 1 : MSS Patch version [ 2. 2. 2. 0]

Device map 1 : Die ID hex value 0 [4607536] 
Die ID hex value 1 [15] 
Die ID hex value 2 [31] 
Die ID hex value 3[26] 

Device map 1 : Radar/RF subsystem Power up successful

======================Basic/Static Configuration======================

Device map 1 : Calling rlSetChannelConfig With [15]Rx and [7]Tx Channel Enabled 

Device map 1 : Channel Configuration success

Device map 1 : Calling rlSetAdcOutConfig With [2]ADC Bits and [1]ADC Format 

Device map 1 : AdcOut Configuration success

rlsSOPControl: genericMainGPIOHandle: 0xaaaaedbf3e60
Set SOP_LINE_0
Set AWR1_SOP_LINE_1
Set SOP_LINE_1
Set SOP_LINE_2
== Device map 2 : SOP 4 mode successful

Full Reset for Device: 1...
|RESET Device [1] with cmd[1]: BF
|Write cmd: 0x2 0xbf
Full Reset for Device: 1...
|Pull Device [1] out of RESET with cmd[1]: FF
|Write cmd: 0x2 0xff
== Device map 2 : Device reset successful

[VER] mmWaveLink Studio Version: 1.1.5.4.22.11.18
SPI Port already Open and initalized
Setting Chip Select
Comm Interfaces Opened Successfully
Device [1] Register interrupt handler
rlDeviceEnable Callback is called by mmWaveLink for Device Index [1]

Device Index [1] rlsEnableDevice
Starting IRQ Polling Thread for device: 1
Polling thread already running: 0x30513aa2ffff0000
Device map 2 : MSS Power Up Async event

PowerUp Time = 1238927, PowerUp Status 1 = 0x0, PowerUp Status 2 = 0x0, BootTestStatus 1 = 0x0, BootTestStatus 2 = 0x0

Device map 2 : mmWave Device Power on success

rlsSOPControl: genericMainGPIOHandle: 0xaaaaedbf3e60
Set SOP_LINE_0
Set AWR1_SOP_LINE_1
Set SOP_LINE_1
Set SOP_LINE_2
== Device map 4 : SOP 4 mode successful

Full Reset for Device: 2...
|RESET Device [2] with cmd[1]: FE
|Write cmd: 0x3 0xfe
Full Reset for Device: 2...
|Pull Device [2] out of RESET with cmd[1]: FF
|Write cmd: 0x3 0xff
== Device map 4 : Device reset successful

[VER] mmWaveLink Studio Version: 1.1.5.4.22.11.18
SPI Port already Open and initalized
Setting Chip Select
Comm Interfaces Opened Successfully
Device [2] Register interrupt handler
rlDeviceEnable Callback is called by mmWaveLink for Device Index [2]

Device Index [2] rlsEnableDevice
Starting IRQ Polling Thread for device: 2
Polling thread already running: 0x30513aa2ffff0000
Device map 4 : MSS Power Up Async event

PowerUp Time = 1236457, PowerUp Status 1 = 0x0, PowerUp Status 2 = 0x0, BootTestStatus 1 = 0x0, BootTestStatus 2 = 0x0

Device map 4 : mmWave Device Power on success

rlsSOPControl: genericMainGPIOHandle: 0xaaaaedbf3e60
Set SOP_LINE_0
Set AWR1_SOP_LINE_1
Set SOP_LINE_1
Set SOP_LINE_2
== Device map 8 : SOP 4 mode successful

Full Reset for Device: 3...
|RESET Device [3] with cmd[1]: FB
|Write cmd: 0x3 0xfb
Full Reset for Device: 3...
|Pull Device [3] out of RESET with cmd[1]: FF
|Write cmd: 0x3 0xff
== Device map 8 : Device reset successful

[VER] mmWaveLink Studio Version: 1.1.5.4.22.11.18
SPI Port already Open and initalized
Setting Chip Select
Comm Interfaces Opened Successfully
Device [3] Register interrupt handler
rlDeviceEnable Callback is called by mmWaveLink for Device Index [3]

Device Index [3] rlsEnableDevice
Starting IRQ Polling Thread for device: 3
Polling thread already running: 0x30513aa2ffff0000
Device map 8 : MSS Power Up Async event

PowerUp Time = 1237037, PowerUp Status 1 = 0x0, PowerUp Status 2 = 0x0, BootTestStatus 1 = 0x0, BootTestStatus 2 = 0x0

Device map 8 : mmWave Device Power on success

Device map 14 : CRC Type set for MasterSS success

Device map 2 : BSS Power Up Async event

Device map 4 : BSS Power Up Async event

Device map 8 : BSS Power Up Async event

Device map 2 : RF Version [ 2. 2. 0.13] 
Device map 2 : MSS version [ 2.  2. 1.  7] 
Device map 2 : mmWaveLink version [ 2. 2. 3. 2]

Device map 2 : RF Patch Version [ 2. 2. 3. 3] 
Device map 2 : MSS Patch version [ 2. 2. 2. 0]

Device map 2 : Die ID hex value 0 [4607536] 
Die ID hex value 1 [15] 
Die ID hex value 2 [47] 
Die ID hex value 3[11] 

Device map 4 : RF Version [ 2. 2. 0.13] 
Device map 4 : MSS version [ 2.  2. 1.  7] 
Device map 4 : mmWaveLink version [ 2. 2. 3. 2]

Device map 4 : RF Patch Version [ 2. 2. 3. 3] 
Device map 4 : MSS Patch version [ 2. 2. 2. 0]

Device map 4 : Die ID hex value 0 [4607536] 
Die ID hex value 1 [15] 
Die ID hex value 2 [48] 
Die ID hex value 3[28] 

Device map 8 : RF Version [ 2. 2. 0.13] 
Device map 8 : MSS version [ 2.  2. 1.  7] 
Device map 8 : mmWaveLink version [ 2. 2. 3. 2]

Device map 8 : RF Patch Version [ 2. 2. 3. 3] 
Device map 8 : MSS Patch version [ 2. 2. 2. 0]

Device map 8 : Die ID hex value 0 [4607536] 
Die ID hex value 1 [16] 
Die ID hex value 2 [26] 
Die ID hex value 3[21] 

Device map 14 : Radar/RF subsystem Power up successful

======================Basic/Static Configuration======================

Device map 14 : Calling rlSetChannelConfig With [15]Rx and [7]Tx Channel Enabled 

Device map 14 : Channel Configuration success

Device map 14 : Calling rlSetAdcOutConfig With [2]ADC Bits and [1]ADC Format 

Device map 14 : AdcOut Configuration success

Device map 15 : Calling rlRfSetDeviceCfg With bssAnaControl = [0] and bssDigCtrl = [0]

Device map 15 : RF Device Configuration success

Device map 15 : Calling rlRfSetLdoBypassConfig With Bypass [0] 

Device map 15 : LDO Bypass Configuration success

Device map 15 : Data format Configuration success

Device map 15 : Low Power Configuration success

Device map 15 : APLL Synth BW Configuration success

Device map 15 : Basic/Static configuration success

Device map 1 : MSS RF Error [0x1] Status Async event

Device map 1 : BSS CPU Fault Async event -> 3, 953, 227260, 0, 1074725151, 134281536, 0, 65535, 255, 255, 255, 255
Device map 15 : RF Initialization/Calibration failed with error code -8 

ERROR: DeviceInit2 Failed
ERROR: Starting devices failed

  • 0
    TI__Mastermind 32865 points

    Hi Peter,

    Can you please specify the DFP version you are using on the boards as well?

    Is there any change in the recent builds and previous ones which can contribute to this?

    Thanks,

    Pradipta.

  • 0 in reply to Pradipta Bandyopadhyay
    Intellectual 400 points

    Hi Pradipta,

    I checked and we are using firmware image for ES1.1 chip from mmwave_dfp_02_02_03_01 which was with mmwavelink vesion 2.2.3.1.13.5.21. Since the mmwavelink in our code was updated to 2.2.3.2.4.2.22 which is packaged with mmwave_dfp_02_02_04_00 we have not updated the firmware image that comes with this version. So we now have mmwavelink used in source code from 2.2.3.2.4.2.22 but a firmware image from 2.2.3.1.13.5.21. This is going to be rectified and we will retest with the updated firmware image.

    In terms of changes in recent builds, we are still using the same PCB assemblers as previous builds.

    Best regards,

    Peter

  • 0 in reply to radar_pete
    TI__Mastermind 32865 points

    Hi Peter,

    radar_pete said:
    This is going to be rectified and we will retest with the updated firmware image.

    Can you let us know when will you have these results with you?

    Thanks,

    Pradipta. 

  • 0 in reply to Pradipta Bandyopadhyay
    Intellectual 400 points

    Hi Pradipta,

    We retested there with the updated firmware image and had the same issue.

    Are there any more verbose debug messages that we can get other than those listed below?

    Device map 1 : MSS RF Error [0x1] Status Async event

    Device map 1 : BSS CPU Fault Async event -> 3, 953, 227260, 0, 1074725151, 134281536, 0, 65535, 255, 255, 255, 255 >>> error code of 3 = MSS/RF Processor Firmware Fatal Error

    Device map 15 : RF Initialization/Calibration failed with error code -8 >>> error code of -8 = device failed to send response within time 

    Also can the device ID hex value tell anything in terms of which wafer these AWR2243 chips were from or quality checks done etc?

    Device map 1 : Die ID hex value 0 [4607536]
    Die ID hex value 1 [15]
    Die ID hex value 2 [31]
    Die ID hex value 3[26]

    Device map 2 : Die ID hex value 0 [4607536]
    Die ID hex value 1 [15]
    Die ID hex value 2 [47]
    Die ID hex value 3[11]

    Device map 4 : Die ID hex value 0 [4607536]
    Die ID hex value 1 [15]
    Die ID hex value 2 [48]
    Die ID hex value 3[28]

    Device map 8 : Die ID hex value 0 [4607536]
    Die ID hex value 1 [16]
    Die ID hex value 2 [26]
    Die ID hex value 3[21]

  • 0 in reply to radar_pete
    TI__Mastermind 32865 points

    Hi Peter,

    1) Can you let me know if you have JTAG access on the board which will allow to take memory dumps. 

    2) Also on the failing device can you run it like a single chip and see if the calibration/initialization passes or fails in this case?

    Thanks,

    Pradipta.

  • 0 in reply to Pradipta Bandyopadhyay
    Intellectual 400 points

    Hi Pradipta,

    1) Unfortunately we don't have access to JTAG pins from the AWR2243 on this board. We just connect to TDO pin on the chip as this is used for SOP2 at power-on also.

    2) I'll check with our software team to see if we can try this.

    Best regards,

    Peter.

  • 0 in reply to radar_pete
    Intellectual 400 points

    Hi Pradipta,

    We tried running the Master device like a single chip and we still see the same error message around 30% of the time. Is there anything else we can try?

    Best regards,

    Peter.

  • 0 in reply to radar_pete
    TI__Mastermind 32865 points

    Hi Peter,

    To comment further on this, we will need some memory dump to fully understand the issue in the device. Is there any way you can make a connection to the device to get some memory logs. Meanwhile i will check internally for some other alternatives for the same.

    Thanks,

    Pradipta.