I am having problems with initial bootup of a custom board. It is very similar to the OMAPL138 Zoom experimenter, but uses a different oscillator frequency -- 26 MHz instead of 24 MHz. The problem seems to be that some initialization of the Arm or PSC modules in either the ROM bootloader or the ubl code gets the Arm started correctly, but if the ubl code is loaded via an Arm based emulator, then the Arm CPU hangs waiting for PSC0_PSTAT.
I have been looking at the various PSC registers and have noted the following for the two cases where things are working or not:
Valid Init from ubl No ubl init
MDCTL[14] 0x00000100 0x00000100
MDCTL[15] 0x00000103 0x00000000
MDSTAT[14] 0x00021F03 0x00021F0A
MDSTAT[15] 0x00001D03 0x00000A00
PSC0_PSTAT 0x00000000 0x00000001
Note that MDSTAT[14], the Arm module status, shows the Arm in transition when the boot initialization code does not run. The Arm is correctly enabled after a valid init from the boot code. Also the DSP in enabled, but this should not matter for our purposes.
This does not occur when CCStudio and the BH-560USB-bp is used to connect to the Arm run code, but if an Arm-specific emulator like the Ronetix PEEDI si used I get the results above.
How do I get the Arm out of the state where MDSTAT[14] is 0x00021F0A? -- This is shown as "In Transition" in the SPRUgm7D.
