Quantcast
Channel: MSP low-power microcontroller forum - Recent Threads
Viewing all articles
Browse latest Browse all 22733

FRAM CTPL Library not operating properly after coming out of LPM3.5

$
0
0

I'm Using the FRAM Utility Library version 02.00.00.15.  I just got all the files to compile and all seems ok until I come out of LPM3.5.  I'm having problem getting my target to operate properly after coming out of LPM3.5, one of my peripheral devices, which was powered off is not communicating with the micro (FR5969) so I'm following the debugging advice in section 2.2.2 of the manual and defining CTPL_LPM_DEBUG in the Assembler Preprocessor window under IAR Embedded Workbench (IAR Assembler for MSP430 6.40.1 (6.40.1.950)).

The problem I ran into is errors in ctpl_low_level.s43.

Building configuration: target - Debug
Updating build tree...
ctpl_low_level.s43
Error[431]: Accessing SFR using incorrect size \fram_utils\ctpl_low_level.s43 127
Error[431]: Accessing SFR using incorrect size \fram_utils\ctpl_low_level.s43 127
Error[50]: Undefined symbol:'__STACK_END'      \fram_utils\ctpl_low_level.s43 127
Error[50]: Undefined symbol:'lpmDebug_return'  \fram_utils\ctpl_low_level.s43 127
Error[444]: PC offset must be even.            \fram_utils\ctpl_low_level.s43 127
Error[444]: PC offset must be even.            \fram_utils\ctpl_low_level.s43 127
Error while running Assembler
 
Total number of errors: 6
Total number of warnings: 0

Here's the MACRO code:

; Allow debugging in LPMx.5 by emulating wakeup
lpmDebug    MACRO
#if defined(CTPL_LPM_DEBUG)
        movx.a  #CTPL_RAM_START,R4                  ; fill dst
        movx.a  #(__STACK_END-CTPL_RAM_START),R5    ; fill length
        movx.a  #0xffff,R6                          ; fill value
        fillx   R4,R5,R6                            ; fill RAM contents with 0xffff
        LOCAL lpmDebug_top

So I defined __STACK_END as 2400h since CTPL_RAM_START was defined as 1c00h. This didn't fix the issue. The naming of __STACK_END is ???? Isn't the end of the stack the same place the RAM starts, since the stack starts at the top of RAM and works down?

I didn't see anyone else having this issue. Please help.

Thanks,

-Jim


Viewing all articles
Browse latest Browse all 22733

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>