Question: for TM4C devices, is there anything in a SYS/BIOS application that initializes SysClk or any other part of the device hardware else prior to main? If so, is there any to change or disable this in the .cfg file? And how can I see what initialization is performed?
I have written an application for TM4C that I am trying to get running on a custom board. The application uses SYS/BIOS, NDK, Tivaware, thus far has been developed using the DK-TM4C129X development kit, and has generally worked well on the DK-TM4C129X.
There is a problem with the custom board in which the connection between the 25 MHz crystal and the OSC0 pin is broken. I have written an application that uses only the TivaWare libraries to blink LEDs and send data out a UART and that seems to work fine as long as I don’t call SysCtlClockFreqSet to change the SysClk configuration from using the precision internal osc to using the main osc or PLL.
However, I haven’t been able to get running on the custom board a SYS/BIOS application generated from the .cfg file compiled by XDC, even the simplest gpiointerrupt example application.
I’m using IAR to download and debug via the EK-TM4C124XL Launchpad. After downloading the application, there is a reset, and then the TM4C device just locks up. The debugger does not go to a breakpoint on main, debugger cannot read its memory, and I have to use the LM flash programmer to unlock the debug port.
TI-RTOS version 2.14.00.10, TivaWare 2.1.1.71b, BIOS 6.42.01.20
In my application, I have written the SYS/BIOS .cfg by hand, instead of using Code Composer, primarily because on the computer I’m using, when I attempt to open the .cfg file in CC, the GUI window does not open properly, and I get a java null pointer exception, but that is another issue..
Thanks for any help.
