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.

CC1352R: ROV error

Part Number: CC1352R
Other Parts Discussed in Thread: SYSBIOS

Hi,

 I got some errors from the ROV. I don't know how to fix it.

Error: java.lang.Exception: Target memory read failed at address: 0x2000771c, length: 12 This read is at an INVALID address according to the application's section map. The application is likely either uninitialized or corrupt.

Error: java.lang.Exception: Target memory read failed at address: 0x2000673c, length: 20 This read is at an INVALID address according to the application's section map. The application is likely either uninitialized or corrupt.

Thanks in advance

Andrés

  • Hi Andrés,

    Can you please share the generated map file?

    Thanks,
    Nikolaj

  • Hi Andrés, 

    Do you also experience this error at the beginning of main? If not, can you try to debug through the application, and try to determine when this error occurs?

    Regards,
    Nikolaj

  • Hi Nikolaj,

    I got that Semaphore error in ROV after calling GPIO_init()
    I got that Event error in ROV after calling Event_create()

    Thanks in advance

    Andrés

  • Hi Andrés,

    Thanks for all the feedback. Could you also share your linker file?

    Thanks,
    Nikolaj

  • Hi Nikolaj,

    /******************************************************************************
    
     @file  cc13x2_cc26x2.cmd
    
     @brief Linker configuration file for sensor/collector on cc13x2/cc26x2 devices
    
     Group: WCS LPC
     Target Device: cc13x2_26x2
    
     ******************************************************************************
     
     Copyright (c) 2016-2021, Texas Instruments Incorporated
     All rights reserved.
    
     Redistribution and use in source and binary forms, with or without
     modification, are permitted provided that the following conditions
     are met:
    
     *  Redistributions of source code must retain the above copyright
        notice, this list of conditions and the following disclaimer.
    
     *  Redistributions in binary form must reproduce the above copyright
        notice, this list of conditions and the following disclaimer in the
        documentation and/or other materials provided with the distribution.
    
     *  Neither the name of Texas Instruments Incorporated nor the names of
        its contributors may be used to endorse or promote products derived
        from this software without specific prior written permission.
    
     THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
     AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
     THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
     PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
     CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
     EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
     PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
     OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
     WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
     OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
     EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    
     ******************************************************************************
     
     
     *****************************************************************************/
    
    /* Retain interrupt vector table variable                                    */
    --retain=g_pfnVectors
    /* Override default entry point.                                             */
    --entry_point ResetISR
    /* Allow main() to take args                                                 */
    --args 0x8
    /* Suppress warnings and errors:                                             */
    /* - 10063: Warning about entry point not being _c_int00                     */
    /* - 16011, 16012: 8-byte alignment errors. Observed when linking in object  */
    /*   files compiled using Keil (ARM compiler)                                */
    --diag_suppress=10063,16011,16012
    
    /* The following command line options are set as part of the CCS project.    */
    /* If you are building using the command line, or for some reason want to    */
    /* define them here, you can uncomment and modify these lines as needed.     */
    /* If you are using CCS for building, it is probably better to make any such */
    /* modifications in your CCS project and leave this file alone.              */
    /*                                                                           */
    /* --heap_size=0                                                             */
    /* --stack_size=256                                                          */
    /* --library=rtsv7M3_T_le_eabi.lib                                           */
    
    /******************************************************************************
     Memory Sizes
     *****************************************************************************/
    
    /* The starting address of the application.  Normally the interrupt vectors  */
    /* must be located at the beginning of the application.                      */
    #define FLASH_BASE              0x00000000
    #define FLASH_LAST_BASE         0x56000
    #define RAM_BASE                0x20000000
    
    #define FLASH_SIZE              0x56000
    #define FLASH_LAST_SIZE         0x2000
    #define RAM_SIZE                0x14000
    
    /******************************************************************************
     System memory map
     *****************************************************************************/
    MEMORY
    {
        /* Application stored in and executes from internal flash */
        FLASH (RX) : origin = FLASH_BASE, length = FLASH_SIZE
        /* Last flash page */
        FLASH_LAST (RX) : origin = FLASH_LAST_BASE, length = FLASH_LAST_SIZE
        /* Application uses internal RAM for data */
        SRAM (RWX) : origin = RAM_BASE, length = RAM_SIZE
    }
    
    /******************************************************************************
     Section allocation in memory
     *****************************************************************************/
    SECTIONS
    {
        .intvecs        :   > FLASH_BASE
    /*
        flash_last_text
        {
            mac_user_config.obj(.text)
            macTask.obj(.text)
            hmac_rom_init.obj (.const)
            osal_port.obj (.text)
        } > FLASH_LAST
    */
        .text           :   >> FLASH_LAST | FLASH
        .const          :   > FLASH
        .constdata      :   > FLASH
        .rodata         :   > FLASH
        .cinit          :   > FLASH
        .pinit          :   > FLASH
        .init_array     :   > FLASH
        .emb_text       :   > FLASH
        .ccfg           :   > FLASH_LAST (HIGH)
    
        GROUP > SRAM
        {
            .data
            .bss
            .vtable
            .vtable_ram
             vtable_ram
            .sysmem
            .nonretenvar
        } LOAD_END(heapStart)
    
        .stack          :   >  SRAM (HIGH) LOAD_START(heapEnd)
    }
    
    /* Create global constant that points to top of stack */
    /* CCS: Change stack size under Project Properties    */
    __STACK_TOP = __stack + __STACK_SIZE;
    

    Thanks,

    Andrés

  • Hi Andrés,

    Thanks for your linker file. I believe this is an issue related to auto-sized heap.

    Please refer to the "Warning" box in the "ROV in IAR" here: https://dev.ti.com/tirex/content/simplelink_cc13xx_cc26xx_sdk_6_10_00_29/docs/ble5stack/ble_user_guide/html/ble-stack-5.x-guide/debugging-index.html#rov-in-iar 

    It is suggested to add some lines to the \kernel\tirtos\packages\ti\sysbios\heaps\package.xs file in the SDK.

    Even though this is mentioned for IAR, I am able to reproduce your issue in CCS using osal heap manager, and the workaround mentioned in above guide fixed my issue.

    If I use the HeapMem instead of the legacy osal heap manager, then I am also not seeing the issue (without the workaround).

    So I would suggest to either use the HeapMem (or HeapTrack) heap manager instead of the osal heap manager or apply the workaround to  \kernel\tirtos\packages\ti\sysbios\heaps\package.xs as mentioned in above guide.

    Regards,
    Nikolaj