• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 335 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

IWRL6432: iwrl 6432

Prasad Shamain
Prodigy 10 points
Part Number: IWRL6432

Hi 
I have a few questions about 6432L. 
When I compile  the motion and presence detection project for 6432 Low Power, I get the following: 


I have a few questions and comments. Could you please address them?

Please comment on the following

  1. The total code + data is 786K. Correct? Is it possible to separate it between code vs. data ? The firmware is about 244KB, 
  2. Do you have a projectspec file for 6432L people counting?
  3. The memory banks are in multiple of 128 KB. But the memory allocation can be done over finer granularity. For example, HWASS has 426KB memory. Correct?
  4. In the above memory allocation, 360K+16K of Prog+Data RAM  (512KB) is used and there is 131KB M4F RAM is unutilized. Out of 512KB shared L3 memory, APP uses 256KB and the rest 160KB for radar cube. There is (512-426)=86 KB of the shared memory is not utilized.
  • 0
    TI__Genius 16441 points

    Hi, 

    Prasad Shamain said:
    Is it possible to separate it between code vs. data ?

    Can you clarify what you mean by this? If you click the arrows next to each section to expand you can see more specific usage details. Is this what you are looking for?

    Prasad Shamain said:
    Do you have a projectspec file for 6432L people counting?

    People counting/tracking is actually included as part of the motion and presence detection demo so there is no separate .projectspec file. It must be enabled in the configuration file. The IWRL6432 People Tracking demo in the Radar Toolbox provides example configuration files which enable this feature. 

    Prasad Shamain said:
    The memory banks are in multiple of 128 KB. But the memory allocation can be done over finer granularity. For example, HWASS has 426KB memory. Correct?

    HWASS is 426KB because there is a block of 96KB which is being used by FECSS. The remaining shared memory is split into two 128 KB partitions. 

    Prasad Shamain said:
    There is (512-426)=86 KB of the shared memory is not utilized.

    The 426 is actually in bytes and 512 in KB. Converting both to KB we can see that the unused portion is actually 96KB. This is being utilized by FECSS. 

    I recommend that you refer to this shared memory documentation in the Radar Toolbox for understanding how the shared memory is allocated.

    Best Regards,

    Josh