• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 527 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.

RTOS/AWR1243: AWR1243 cascaded - timeout on boot with Processor SDK 3.5

TG2718
Intellectual 1000 points
Part Number: AWR1243

Tool/software: TI-RTOS

I am in the process of upgrading from Processor SDK 3.4 to Processor SDK 3.5 (PSDK hereafter). We have a custom RF board with multiple AWR1243 chips that plugs into a TDA2Px EVM board. Everything was working as expected on PSDK 3.4, but with the change to PSDK 3.5 there is an issue with the power-on sequence for the cascaded radar chips as seen below. The "Power On failed" line at the end is printed due to a timeout.

[IPU1-0]     20.546117 s:  CHAINS: Init AR12xx ...
[IPU1-0]     20.546117 s:  UTILS_MCSPI: McSPI is configured in interrupt mode!!
[IPU1-0]     20.546117 s:  SYSTEM: UART: INTERRUPT Mode is Selected
[IPU1-0]     20.546117 s:  AR12XX: RL_DEV_AE_MSSPOWERUPDONE_SB received
[IPU1-0]     20.546117 s:  AR12XX: ES2.0 Device detected!!
[IPU1-0]     20.546117 s:  AR12XX: Firmware Download Started : Ftype: MSS_BUILD
[IPU1-0]     20.546117 s:  AR12XX: Firmware Download Successful : Ftype: MSS_BUILD
[IPU1-0]     20.546117 s:  AR12XX: Firmware Download Started : Ftype: BSS_BUILD
[IPU1-0]     20.546117 s:  AR12XX: Firmware Download Successful : Ftype: BSS_BUILD
[IPU1-0]     20.546117 s:  AR12XX: Firmware Download Started : Ftype: CONFIG_INFO
[IPU1-0]     20.546117 s:  AR12XX: Firmware Download Successful : Ftype: CONFIG_INFO
[IPU1-0]     20.546117 s:  AR12XX: RL_DEV_AE_MSSPOWERUPDONE_SB received
[IPU1-0]     20.546117 s:  AR12XX: RL_DEV_AE_RFPOWERUPDONE_SB received
[IPU1-0]     20.546117 s:  AR12XX: ES2.0 Device detected!!
[IPU1-0]     20.546117 s:  AR12XX: RL_DEV_AE_MSSPOWERUPDONE_SB received
[IPU1-0]     20.546117 s: radar_ar12xx/src/bspdrv_ar12xxPriv.c @ Line 429:
[IPU1-0]     20.546117 s:  AR12XX: Radar Slave Device Power On failed!!

Comparing mmwave_dfp_01_02_00_00 included with PSDK 3.5 with mmwave_dfp_01_01_00_00 included with PSDK 3.4, the code in general and the device on/power on code in particular appears very similar. Oddly, the file rl_internal.c does not appear to be included with mmwave 1.2/PSDK 3.5, and there is no longer a call to rlDeviceSetInternalConf() at the end of Bsp_ar12xxRadarDeviceOn(). Is this expected?

Any ideas what may be causing this difficulty with the upgrade to PSDK 3.5? Or what I should do to debug and resolve the issue?

Thanks.

  • 0
    TI__Mastermind 30245 points
    Hi Todd,

    The rlInternal has now moved to bspdrv_ar12xxInternal.c.

    Can you please try reducing the mcSPI clock frequency just to check if the communication to the slaves at boot up is working fine for you?

    PROCESSOR_SDK_RADAR_03_05_00_00\vision_sdk\links_fw\src\rtos\utils_common\src\utils_mcspi.c

    /* 24 MHz Bus Frequency */
    mcspiCfgPrms[mcSPINum].spiHWCfgData.configChfmt[i]. = 24000000;

    The SPI frequency has been kept at default of 24 MHz from 3.5 onwards.

    Thanks and Regards,
    Piyali
  • 0 in reply to Piyali Goswami
    Intellectual 1000 points

    I lowered the SPI frequency back to 8 MHz and that seems to resolve the issue. Thanks for your helpful suggestion!