Hi everyone,
I am using CCSv4 (trail version). Firstly, I created usb application with IAR Workbench for stellaris LM3S5R36. Then I debug and tested code on LM3S5R36. Everything is good up until here. After that, I built same project wtih CCSv4 and then downloaded the code in LM3S5R36 on debug mode. When I debug code with CCSv4 some interrupts(time, adc, gpio) are working and also USB connection(bulk device) is successful. But, When I sent command from GUI to LM3S5R36 on debug mode, the problem is occur.
//*****************************************************************************
// This is the code that gets called when the processor receives a fault
// interrupt. This simply enters an infinite loop, preserving the system state
// for examination by a debugger.
static void
FaultISR(void)
{
//
// Enter an infinite loop.
while(1)
}
I received a fault interrupt. I didn't understand, Why I didn't receive this problem on IAR...
Regards,
--Mehmet
Mehmet GULI created usb application with IAR Workbench ... I built same project wtih CCSv4
Unless you have specifically taken great care to ensure that your project is entirely portable, you cannot just take it from one one toolset onto another and expect it to "just work".
Especially on toolsets with entirely different compilers!
I used the post here (that points to another post): http://e2e.ti.com/support/microcontrollers/stellaris_arm_cortex-m3_microcontroller/f/471/p/63837/229960.aspx#229960 to debug a FreeRTOS + usb_dev_msc example on Code Red. Now that this is working, I am getting a similar failure on CCSv4 and will use the same technique to debug.
If I remember correctly, I was getting to FaultISR in CodeRed due to FreeRTOS stack sizes being too small for the usb and fatfs libraries.
Hi Joe,
I changed stack sizes and then fixed the problem. Thanks, for your help...