AM2732: Unhandled Async Event During awr2243 openCfg

bruce

Part Number: AM2732
Other Parts Discussed in Thread: AWR2243

Hi,

We are developing the am273x demo. The SDK version is mmwave_mcuplus_sdk_04_02_00_03.

After open the mmWave module by calling MMWave_open(), the soc receives an Async MsgId from awr2243, log shown as below:

My question is the asyncSB: 0x5, should happens here? How to fix it?

over 3 years ago

0 Jitendra Gupta over 3 years ago

TI__Guru 69960 points

Hi,

Could you confirm if you are using AWR2243 ES1.0 or ES1.1, as bootup sequence for these two revisions are slightly different.

And was it different behavior with older MCU+SDK version 4.2.0.2?

Regards,

Jitendra

0 bruce over 3 years ago in reply to Jitendra Gupta

Prodigy 60 points

Hi，I have confirmed that we are using AWR2243 ES1.1. I don’t test on version 4.2.0.2 yet.

0 Jitendra Gupta over 3 years ago in reply to bruce

TI__Guru 69960 points

Understood, those two async-events are expected one but only things it didn't handled in the application code.

But do you see any issue with the final functionality of the application??

0 bruce over 3 years ago in reply to Jitendra Gupta

Prodigy 60 points

It seems that the final functionality of the application is OK. So, those two events happen only once during booting, can we ignore them?

0 Jitendra Gupta over 3 years ago in reply to bruce

TI__Guru 69960 points

Yes, you can skip that during the bootup.

But make sure that you check all the bootup status to be passed.

MMWL_asyncEventHandler() {

....

case RL_DEV_AE_MSS_BOOTERRSTATUS_SB:
{
mmwl_bMssBootErrStatus = 1U;
/* check all the status for test to be passed/Failed */
//(rlMssBootErrStatus_t *)payload->powerUpStatus1, powerUpStatus2, bootTestStatus1, bootTestStatus2
}

Arm-based microcontrollers

Arm-based microcontrollers forum

AM2732: Unhandled Async Event During awr2243 openCfg