• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 3 answers
  • Subscribers 30 subscribers
  • Views 517 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.

Original question:

AWR1843: DPM error causing runtime to crash

AWR1843BOOST: Error Code: Out of L3 RAM during detection matrix allocation - Demo lab

Jairo Gallardo
Expert 1640 points
Part Number: AWR1843BOOST
Other Parts Discussed in Thread: AWR1843

Hi, I get the error -40112 and I found that is an L3 RAM error:

I also check the stack status of the tasks and everything seems ok

So, what could be the cause of this error?

I am trying to reconfigure the radar creating a new task (can_task) and calling the functions you provide in the demo lab, if I configure a single profile works ok but when I try the advance frame config I get this error, I am using the profile_advanced_subframe.cfg as guide.

Thanks

  • 0
    Expert 1640 points

    I have reduced the stack size of the CLI and CAN task and I dont see the previous errors anymore but now I get another error in the mmw_cli.c file

    this kind of error happens when you want to load a new configuration from the demo GUI but you have not made a reset, so I stop the debug mode and  I flash the .bin and start the app in deploy mode, then I load a config from the GUI, everything is ok, but then I reset the evk and I use the can_task to load another config in advance frame mode but the GUI does not show anything and the evk does not allow a new config from the GUI (it seems the app crashes), I have to reset the board to load a new config

  • 0
    TI__Mastermind 24955 points

    Jairo,

    The "Out of L3 RAM error occurs when there is not sufficient space in L3 memory to allocate memory for the detection matrix following the radar cube. In both cases, this is a direct function of the the chirp configuration you are using and will depend on several factors including:

    1. Number of transmitters enabled (when used in a TDM-MIMO configuration)

    2. Number of receivers enabled

    3. Number of samples per chirp

    4. Number of chirps per frame

    The AWR1843 device has shared L3 memory size of 1 MB. Based on your chirp configuration, it is not out of the realm of possibility to encounter a scenario where the radar cube alone consumes the entire L3 memory.

    Are you using the unmodified "profile_advanced_subframe.cfg" configuration file when you encounter this error?

    Regards,

    Kyle

  • 0 in reply to Kyle Cousino
    Expert 1640 points

    Hi, I am using the "profile_advanced_subframe.cfg"  as a guide, the profiles, chirps, and frame configurations correspond to the MRR lab.

  • 0 in reply to Jairo Gallardo
    TI__Mastermind 24955 points

    Which of the MRR configurations are you using? The MRR lab has configurations for 80 meters and 120 meters in MRR mode. Similarly, the MRR lab has configurations for 20, 30, and 50 meters in USRR mode.

    The MRR lab uses a slightly different processing chain than the Out-of-Box demo. So you will need to evaluate your desired chirps against the Out-of-Box Demo framework and determine where the chirp design needs to be modified.

    Due to memory constraints in the Out-of-Box demo, I would suggest using the 80 meter chirp and and 20 meter chirp profiles, respectively.

    Regards,

    Kyle

  • 0 in reply to Kyle Cousino
    Expert 1640 points

    Hi,

    Kyle Cousino said:
    Which of the MRR configurations are you using? The MRR lab has configurations for 80 meters and 120 meters in MRR mode. Similarly, the MRR lab has configurations for 20, 30, and 50 meters in USRR mode.

    I am using the default MRR lab config: 120m and 30m

    Kyle Cousino said:
    The MRR lab uses a slightly different processing chain than the Out-of-Box demo

    How do you know that?, and what parameters do I have to keep in mind to evaluate and/or modify the chirps I need?, you talk about the memory constraints but I don't know what are those constraints, is there any doc that talks about it?

    thanks

  • 0 in reply to Jairo Gallardo
    TI__Mastermind 24955 points

    Jairo,

    As I previously mentioned, I would recommend using the 80 meter chirp instead of the 120 meter chirp.

    The AWR1843 uses the shared L3 memory for storing the 1D FFT radar cube. You can see the size of the shared L3 memory for the AWR1843 in the block diagram shown below:

    In the case of AWR1843, the shared L3 memory is 1024 KB or 1 MB. The shared L3 memory is typically used to store the 1D FFT radar cube, the range-Doppler heatmap. It appears that the chirp configuration for the 120 meter chirp will exceed this 1 MB threshold. Let me check in on this a little bit more and get back to you.

    Regards,
    Kyle