CC1352P: Simple Broadcaster assert issues

Alec R

Part Number: CC1352P

Hi,

I have a Custom CC1352P1F3 board, and I am trying to get it have it run the BLE 5 Simple Broadcaster, but unlike on my launchpad for the same code, it runs into an assert issue on Bios_start(). I can run other, non BLE example RTOS code on this microcontroller.

I am not really sure what is wrong with this, and I have included my error stack and the RTOS BIOS.

stack

the error message is "Caught exception in view init code: "C:/ti/xdctools_3_62_00_08_core/packages/xdc/rov/StructureDecoder.xs", line 525: java.lang.Exception: Target memory read failed at address: 0x20004710, length: 32This read is at an INVALID address according to the application's section map. The application is likely either uninitialized or corrupt."

Is this a configuration issue on my end or is there anything else I could do about this?

over 4 years ago

0 Marie H over 4 years ago

TI__Guru* 83901 points

Hi Alec,

That's strange!

I would start by looking at the HWI view in ROV, is there a hardware exception captured there?

I would also recommend reading through the Custom Board guide:

https://dev.ti.com/tirex/content/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/docs/ble5stack/ble_user_guide/html/cc13xx_cc26xx/custom-hardware-cc13xx_cc26xx.html

and the HW design App note:

https://www.ti.com/lit/swra640

Cheers,

Marie H

0 Alec R over 4 years ago in reply to Marie H

Prodigy 30 points

Hey Marie,

I have checked in HWI view and there are no exception captured there.

I'll read through the custom board guide just to make sure I remembered to do all of that correctly

Thanks for your help,

Alec

0 Marie H over 4 years ago in reply to Alec R

TI__Guru* 83901 points

Hi Alec,

It's strange that you get a seemingly memory related error message, since I assume you haven't made any changes in the linker file (.cmd file). Even though you are using a custom board, you're still using the same device so the memory layout is the same.

Can you check the value of assertCause and assertSubcause when this happens?

You could try removing HAL asserts and see what kind of error/behavior this prompts? (It should be as easy as removing the EXT_HAL_ASSERT define.)

Cheers,

Marie H

Bluetooth®︎

Bluetooth forum

CC1352P: Simple Broadcaster assert issues