Part Number: MSPM0G3519 Hi,
I am developing a custom bootloader on the MSPM0G3519. I created two separate projects:
Bootloader Project
Application Project
To separate bootloader and application memory, I modified the flash regions in device_linker…
Part Number: MSPM0G3519 Hi Team, We are using the MSPM0G3519 MCU in our system with a total of 14 ADC channels configured as follows:
ADC12_0: 7 channels ADC12_1: 7 channels
Currently, ADC values are read every 500 ms using the ADC_GetRawValue(x,…
Part Number: MSPM0G3519
Currently we are using the J_Link Ozone, were unable to see the Peripherals Data, Require .svd file for MSPM0G3519 to help us reading the values from registers while debugging in our tool.
Can you please help with this
Part Number: MSPM0G3519 Other Parts Discussed in Thread: UNIFLASH Hello ,
I am facing an issue in connecting my target MSPM0G3519 with the debugger (trace 32 )
Error Message shown in both debuggers:
T32:
When connected with T32 debugger getting…
Part Number: MSPM0G3519 Hello,
I am implementing a CSC → application jump on MSPM0G3519, 9, based on the example reported in the Application Note "Flash Multi Bank Feature in MSPM0 Family":
static void start_app(uint32_t *vector_table)
{
/* Reset…
Part Number: MSPM0G3519 Hi Team, We are using the MSPM0G3519 MCU in our system with a total of 14 ADC channels configured as follows:
ADC12_0: 7 channels ADC12_1: 7 channels
Currently, ADC values are read every 500 ms using the ADC_GetRawValue(x,…
Part Number: MSPM0G3519-Q1 Other Parts Discussed in Thread: MSPM0G3519 , AES-128 Hello TI team,
I am wondering how we can store keys securely in the ECU (MSPM0G3519)?
Our use case is the following: We are in AUTOSAR context and want to store a key…
Part Number: MSPM0G3519 Hi,
I want to use the external Jlink debugger to flash and debug my project without using on board TI XDS Debugger.
After creating my project, I have changed the debugger option,
When I debug (F5) the project, I am getting…
Part Number: MSPM0G3519-Q1 Hello TI team,
in MCAL_MSPM0_00.02.05.00 (and still in MCAL_MSPM0_01.00.00.00) the variables/constants "eraseLoadFlashSize" and "eraseLoadFlashStart" in the file Fls_Ctrl.c are mapped to a wrong memory section.
Both are…
