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.
Part Number: IWR6843AOPEVM
NOTE: The following update will be included in future MMWAVE-SDK releases.
Users can follow the instructions provided below to make the necessary code changes in the SDK themselves
use the pre-updated C file (soc.c) and the updated AOP out of box demo binary: xwr64xxAOP_mmw_demo.bin available in the 68xx AoP - mmWave SDK Demo Lab in mmWave Industrial Toolbox 4.0.1. You will still need follow step-2 given below to re-build the soc lib with source code updates.
Devices affected: IWR6843 ES1.0, IWR6843AOP ES1.0
SW Versions affected: MMWAVE-SDK 184.108.40.206, MMWAVE-SDK 220.127.116.11_AOP
Description: The start-up sequence in the affected MMWAVE-SDK and MMWAVE-SDK AOP releases can fail causing the application to terminate during startup.
The ROM bootloader on IWR6843 ES1.0 devices performs APLL calibration during device boot-up and the status of this calibration is checked by MMWAVE-SDK initialization code. The APLL might not fully settle during ROM bootloader execution causing this SDK check to fail. This does not impact application code since APLL calibration is again performed by the BSS firmware during BSS (aka Radar SS) power-up and SDK checks BSS returned APLL calibration status before starting the application tasks.
In summary, the SDK startup code checks the APLL calibration status twice:
Solution: As mentioned above, the first check is redundant and needs to be removed. Please follow the steps given below to update the code in MMWAVE-SDK 18.104.22.168 (if using IWR6843 ES1.0) and MMWAVE-SDK 22.214.171.124_AOP (if using IWR6843AOP ES1.0). The following updates will be included in future MMWAVE-SDK releases.
Step-1. Make the following modifications in file: C:\ti\mmwave_sdk_03_02_00_xx\packages\ti\drivers\soc\src\soc.c
a) In function SOC_init(), delete/disable the section of code highlighted below (you can put this section inside #if 0 and #endif pre-processor directives to disable it):
if (ptrCfg->clockCfg == SOC_SysClock_INIT)
retVal = SOC_checkBLAPLLCalibration();
if(retVal < 0)
/* Error: Expect APLL calibration is done by BL without errors */
*errCode = SOC_EBLERR;
/* Free memory and return NULL handle */
ptrSOCDriverMCB = (SOC_DriverMCB *)NULL;
b) You will also need to disable the :exit label towards the end of this function to avoid an unused label compiler error.
c) Delete/disable both the function declaration and definition for SOC_checkBLAPLLCalibration() in the same file.
d) Add the new function call SOC_waitAPLLCalibration(…) after SOC_unhaltBCC(…) as highlighted below;
/* YES: Unhalt the BSS: */
/* Wait until APLL calibration is done by BSS */
e) Add the following new code (function declaration and body for SOC_waitAPLLCalibration) in the same file, as shown below. This code can be added at the top of this file before other function declarations and definitions.
/* Function declaration */
static void SOC_waitAPLLCalibration(SOC_DriverMCB* ptrSOCDriverMCB);
/* Function definition */
* @b Description
* This function checks APLL status and wait until APLL clock Calibration
* is done from BSS.
* @param[in] ptrSOCDriverMCB
* Pointer to the SOC Driver
* \ingroup SOC_DRIVER_INTERNAL_FUNCTION
* Not Applicable
static void SOC_waitAPLLCalibration(SOC_DriverMCB* ptrSOCDriverMCB)
/* Get the TOP RCM registers: */
ptrTopRCMRegs = ptrSOCDriverMCB->ptrTopRCMRegs;
/* Wait until APLL clock calibration is done successfully */
while (CSL_FEXTR(ptrTopRCMRegs->SPARE0, 17U, 16U) != 0x3);
Step-2. Rebuild the soc lib using the steps provided below
a) Open a command window in C:\ti\mmwave_sdk_03_02_00_xx\packages\scripts\windows
b) Execute “setenv.bat”
c) In the same terminal session cd to C:\ti\mmwave_sdk_03_02_00_06_AOP\packages\ti\drivers\soc
d) Execute “gmake clean” followed by “gmake all”.
e) The above steps are also shown in the following snapshots (all from the same command window):
Step-3. Rebuild the mmw demo for the Target device (68xx or 68xx AOP)
a) Either using the build instructions provided in the corresponding SDK user guide, section Building Demo
b) Using the mmWave SDK Demo lab for the target device (68xx or 68xx AOP) provided as part of mmWave Industrial Toolbox on TI Resource Explorer
Step-4. Flash the updated mmw demo binary on the target EVM.
Flash and execute the new demo binary on the target EVM as described in the mmWave SDK user’s guide or the mmWave SDK Demo Labs mentioned above.
Thank you for posting this!
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.