Hi, I wonder if someone can help me to figure out the issue as below described.
My application is based on the sample of Cortex_LM3SXXXX_IAR_Keil demo under FreeRTOS rev 5.4.2. It used to be booted by a serial boot loader and run just fine. Since I replaced it with an Ethernet boot loader, my application always stopped in midway during the booting. I use the on-board LED to trace the program and found the application ran and passed the hardware initialization code. After then it failed during a UART receive task creation. I use an EK-LM3S6965 Evaluation board to debug on it. It runs just fine with the debug mode. So I cannot find where or what is wrong. I have several quesitons.
Why the serial boot loader can boot the application fine, but Ethernet boot loader not? (Both have the same definition APP_START_ADDRESS = 0x1000)
Is it possible the application vector table has relocated and conflicted with Ethernet boot loader in SRAM?
Does debug mode just runs from the application vector table at the starting address (0x1000)? Because debug mode does not go through the boot loader, it did not have the problem. So the problem is in Ethernet boot loader, Is it true?
I was talking with Luminary tech support guys, they could not figure out what the cause is. I suspect the problem may relate to the FreeRTOS task priority or stack size settings. The UART receive task was set to the lowest priority that is tskIDLE_PRIORITY.
Any comments will be appreciated.