CCS/CC1310: Reset problem

Hi Andrey,

To help you debug this issue, I would like to reproduce the scenario you are experiencing. You mentioned an example project. Which example project are you using? And what edits (if any) have you made to that example?

Regards,

Toby

Hi. I am using example from this folder ti\simplelink_cc13x0_sdk_1_40_00_10\examples\rtos\CC1310_LAUNCHXL\ti154stack\collector. This example for cc1310 7x7, but I have device with cc1310 4x4. 

I changed the settings of the file CC1310_LAUNCHXL.h for my cc1310 4x4, left 2 LEDs, button and UART (TX, RX)
#define Board_RLED IOID_8
#define Board_GLED IOID_9

#define Board_BTN1 IOID_5

#define Board_UART_RX IOID_7 / * RXD * /
#define Board_UART_TX IOID_6 / * TXD * /

Others I commented. When I start debugging, program is started from Void main () function. I click Run and my program stops in void Main_assertHandler (uint8_t assertReason). In CCS ROV marked as an undefined exception. Why is this exception occurs I did not understand. Then I read this document ti-15.4-stack-quick-start-guide.html in the Startup section says that "Reset the device using only hard resets. From the software, this reset can be accomplished using: HAL_SYSTEM_RESET()" or "In CCS, select Board Reset (automatic) from the reset menu - Board Reset (automatic)". And it realy help me, my device start from CPUwfi(void) and run normal. I think that this may be related need properly reset both core in cc1310?

 But there was another problem doing the reset so the program does not always start from CPUwfi(void) and crash (start main() function). I disconnected the debugger and checked the operation of the device. The device does not reset normally by the reset button. This can see from the LEDs and information on the COM port. I also noticed that the device works normally (LED information) if I do not connect the c1310 to the PC (through a converter cp2102). After program start I connect device to PC and it send information through COM port.  I know that the device can be powered from converters through protective diodes in the device ports. But how does this affect on the reset function, and the debugger's work?

I'm able to run the example on the CC1310 launchpad connected to PC (using USB cable), so perhaps it could be a hardware issue. Are you using a custom board that you designed yourself?