• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 488 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.

AWR2944EVM: BSS reported CPU fault

Wu Jason
Prodigy 30 points
Part Number: AWR2944EVM
Other Parts Discussed in Thread: AWR2944

BSS firmware version Info:

RF H/W Version                     : 02.00
RF F/W Version                     : 02.04.05.03
RF F/W Version continuing    : 22.04.20
BSS reported MSGID: RL_RF_ASYNC_EVENT_MSG and SUBID: RL_RF_AE_CPUFAULT_SB

INFO: MMWave_asyncEventHandler:384: mmwavelink async event handler: BSS Event MsgId: 128 [Device Index: 0x0 Sub Block Id: 0x1002 Sub Block Length: 32]
INFO: MssMMWave_eventCallbackFxn:228: Error: CPU Fault has been detected
INFO: MssMMWave_eventCallbackFxn:243: Error: Fault
type: 3, lineNum: 886, LR: 0x1a72e
PrevLR: 0x0, spsr: 0x6000011f, sp: 0x800feb8, PC: 0x0
Status: 0xffff, Source: 255, AxiErrType: 255, AccType: 255, Recovery Type: 255
ASSERT: 0.356200s: mss/mss_main.c:MssMMWave_eventCallbackFxn:244: 0 failed !!!

This issue will be reported some time with low frequency.

But I want to clarify the following:

1. Is it a known issue from this BSS firmware version?

2. Is it a software issue or hardware issue inside AWR2944? or it is related to the PCBA level design issue?

  • 0
    TI__Mastermind 32725 points

    Hi,

    Please find my comments below.

    Wu Jason said:
    1. Is it a known issue from this BSS firmware version?

    No. This is not a known issue. 

    Wu Jason said:
    2. Is it a software issue or hardware issue inside AWR2944? or it is related to the PCBA level design issue?

    It looks like a software issue. Based on your observations, there is some issue in the RF init calibrations. Is your API sequence as per the suggested flow in the Interface Control document. Will suggest you to check this document and check the sequencing of API calls. If the sequence is correct, please see to it that no frame is initiated when the device is in calibration.

    Thanks,

    Pradipta.

  • 0 in reply to Pradipta Bandyopadhyay
    Prodigy 30 points

    I think the sequence of API calls would be correct, because it only happens one time during total nearly 50 power cycles.

    for the other power cycle, it works well and detection output is normal

    It is a RL_RF_AE_CPUFAULT_SB report from BSS domain, but BSS domain is a black-box for me and I only have the firmware information.

    According to the ICD, This sub block indicates CPU fault status of BIST SS. fault type is RF Processor Firmware Fatal Error

  • +1 in reply to Wu Jason
    TI__Mastermind 32725 points

    Hi,

    We did check the error as per the ICD and the details in the thread. The firmware error is due to issue in AWR_RF_INIT_SB call. So,

    1) The programming sequence may be incorrect.

    2) Have you followed the below two notes as per the ICD

    3) Please see to it that no frame is initiated when the device is in calibration.

    Thanks,

    Pradipta.

  • 0 in reply to Pradipta Bandyopadhyay
    Prodigy 30 points

    Based on your suggestion, I found that I didn't avoid other command being sent before AWR_AE_RF_INITCALIBSTATUS_SB from BSS, so I implmented a condition to fix this issue.

    But after some days testing, The same issue happened again, with the same fault information reported from BSS.

    Is there any other possibility for this issue to occur? or what else information should I provide to find the root cause?

  • 0 in reply to Wu Jason
    TI__Mastermind 32725 points

    Hi,

    In my previous response i tried to reply back with all the possible cases for this issue to occur. 

    On the software side of things please check again with the ICD if

    1) The programming sequence is aper the document.

    2) You are passing the correct parameter to the API.

    3) The API is issued only once in every power cycle. 

    Thanks,

    Pradipta.