Hi
I am getting this error while i am using it in debugger mode.
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.
Hi Katie,
As of now, i am able to compile the code.Still unable to use the interrupts from the application code.
Facing the issues when using the _App_Proxy_Vector_Start and Vector table.
Want to know about the diag_suppress=Pe767, how this is calculated
#pragma diag_suppress=Pe767
*((uint16_t *)(_App_Proxy_Vector_Start + RTC_VECTOR - 59)) = (uint16_t)RTC_C_ISR; // here 59 stands for ?
*((uint16_t *)(_App_Proxy_Vector_Start + PORT4_VECTOR - 59)) = (uint16_t)Port_4;
In TI_MSPBoot_VecRed_FR5969 .. file BRA instruction (0x4030) followed by the address of each
vector routine. It will change for the 5994 or not, how this BRA instruction followed.
0x4030, (uint16_t)&_App_Reset_Vector[0], // APP_PROXY_VECTOR(0) // FFCC = AES256
0x4030, (uint16_t)&_App_Reset_Vector[0], // APP_PROXY_VECTOR(1) // FFCE = RTC
Thanks
Rachit
Hi Rachit,
It looks like you're trying to port MSPBoot to an MSP430FR5994. Is that correct?
MSPBoot was created mainly for flash devices and handles interrupts in a much different, more complex way due to flash segmentation. This involves the use of a proxy vector table like what you've described above. I would not recommend this as a starting place for you project. Even if you've already started developing your code this way, i encourage you to start with MSP430FRBoot instead.
MSP430FRBoot was made for FRAM devices including the MSP430FR5994 and does not require a proxy vector table for interrupts. This means there is no vector redirection and interrupt handling is almost the same as in a typical application. Using this as a starting place will solve the issues you're currently seeing with interrupts.
Here is a link to the MSP430FRBoot Application Report and code (Including MSP430FR5994): MSP430FRBoot 1_00_00_00
Best regards,
Caleb Overbay
Hi Caleb,
Hi Caleb,
I was having dependency of previous code,In previous code they have defined variables (macros) with different names and parameters and they were using the Boot_vector_table.
I have to use them,because they have dependency in complete code, that's why i have used this code only.
Even i have tried with your solution also, by calling one ISR from the boot_vector_table. it works fine.
Thanks & Regards
Rachit Choudhary
**Attention** This is a public forum