• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 133 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.

IWRL6432AOPEVM: Radar demo is not running as a stand along after enabling "CLI Removal" option in example.syscfg

Aleksandr Labunskiy
Intellectual 390 points
Part Number: IWRL6432AOPEVM

Tool/software:

Hello,

I am trying to modify example motion_and_presence_detection_demo_xwrL64xx-aop_m4fss0-0_freertos_ti-arm-clang for IWRL6432AOPEVM board to make it run without Visualizer APP. I added some code to enable PWM outputs when an object is detected. PWM signal comes out on J1 header. I had to flip couple switches to make it work when ran PWM example only. However, the radar example does not run as a stand along. It runs only one cycle (acquires one frame) and then stops. The following messages show up in "CIO" tab at the bottom of CCS:

Cortex_M4_0: Failed to read!

Cortex_M4_0: Failed to read!

Cortex_M4_0: Failed to read!

Cortex_M4_0: Failed to read!

Cortex_M4_0: Failed to read!

Cortex_M4_0: Failed to read!

Cortex_M4_0: ASSERT: 0.563393s: ../power_management.c:powerManagementTask:401: 0 failed !!!

Then I remove all the code I added. I still get the same messages. So, the problem existed to begin with. Please help.

Alex

  • 0
    TI__Mastermind 20921 points

    Hi Alex, 

    Sorry about the slow response here. The 'Failed to read!' message comes from improper switch settings on your EVM. There are some current sensors on the EVM that are read using I2C. If your switch settings disable I2C then you will get this message but it's not actually what is causing the code to crash. If you set S1.6 to OFF then this message should go away.

    For the actual assert failure, can you make sure that you are using the debug build configuration when loading code and running in CCS? Just right click on the project and select 'Build Configurations', then set to debug and rebuild if necessary. This will make sure the device doesn't enter deep sleep and drop the CCS connection after the first frame which is most likely what is happening. 

    Best regards,

    Josh

  • 0 in reply to Josh Dye
    Intellectual 390 points

    Thank you, Josh. I am using Debug Configuration and S1.6 was off. After making the original post I probably relaxed, and my thinking became clear. The PWM pins configuration in example.syscfg was not removed when I said "I remove all the code I added". I had my PWM pins configured to F1 and F4 (very convenient to measure with a scope on J1.1 and J1.2) which moved I2C signals to different pins. 

    Now, I still have my original problem: I need to add two PWM outputs to the example code. When I leave PWM pins configured to the default locations, E4 and E3, the code is running OK in Debug. I need to vary a duty cycle of one PWM based on the distance to the closest object. I have a lot of questions about that. This is actually a different topic. I will ask a new question.

    Alex