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

CCS/AWR1443BOOST: Adding SPI functionality to the mmw demo

Saad Ahmad
Intellectual 590 points
Part Number: AWR1443BOOST
Other Parts Discussed in Thread: AWR1443, IWR1443

Tool/software: Code Composer Studio

Hi,

I wanted to try and use TI RTOS so the AWR1443 BOOST could communicate with an MSP430 via SPI and send it raw distance data which the MSP430 could use. However, the mmw demo gives the error if i try and add more code to the demo. 

Description Resource Path Location Type
<a href="processors.wiki.ti.com/.../10099"> program will not fit into available memory. placement with alignment fails for section ".text" size 0x20853 . Available memory ranges: r4f_linker.cmd /mmw line 34 C/C++ Problem

 

I haven't been able to use the capture demo as it cant be imported or downloaded using the TI resource explorer. Is there a way around this?

Thanks

  • 0
    TI__Mastermind 23725 points
    Hello Saad,

    There are options to reconfigure available memory for program code via .cmd file changes.

    However we will get back to you on if this size change is expected by merely including the SPI dirver in demo code.

    Thank you,
    Vaibhav
  • 0
    TI__Mastermind 21025 points

    Have  you looked at the level sense demo: Power Optimized Level Sensing Demo Software

    This demo uses SPI to send raw range data from IWR1443 to MSP432.  The SPI driver adds about 3k code size (in thumb mode), not counting the initialization code that is required.

  • 0
    TI__Mastermind 21025 points

    >How would you increase the memory the mmw demo can use so i can implement SPI?

    The first thing would be to modify the compiler optimization settings to optimize for size rather than speed.  I think the default is for no symbolic information, so you probably can't save anything there.  If that doesn't help, you can try compiling in Thumb mode (--code_state 16 as opposed to --code_state 32).  If you compile with Thumb mode, you can also link with a Thumb-mode RTSC: rtsv7R4_T_le_v3D16_eabi.lib instead of rtsv7R4_A_le_v3D16_eabi.lib.  If that is not enough, you can rebuild the mmWave SDK with Thumb mode.  The instructions for rebuilding the SDK are in the SDK's user guide.