This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP-L138 boot issues

Other Parts Discussed in Thread: OMAP-L138

Hi,

I'm working with custom hardware that is based on the OMAP-L138 experimenter board. I've been having problems connecting the UART2 pins to a external device (FPGA) and as a result, the Kernel is no longer booting. The bootloaders are still using UART2, but I disabled its usage in the Kernel. This seems to be working fine, so I don't expect this to be an issue. My only way to determine if the Kernel booted successfully is to see a USB device light up and then using SSH.

I'm trying to figure out where the Kernel is hanging to identify a possible hardware issue. Before interfacing the UART with the FPGA everything was working as expected. While testing the connection the SOM died (cause unknown) and now the Kernel will not boot when using a good SOM. UART2 is still working as expected because I see messages from the bootloaders. I tested the SOM on the EVM board and its still working, so I suspect a hardware issue.

I got JTAG debugging working with the XDS510USB and CSSv4, and I'm able to break on start_kernel with no problems. As I step through, I can't seem to get past the cpu_init function, which is called inside the setup_arch function. When I step out the cpu_init function,  the disassembly shows "andeq r0,r0,r0", which is a NOP. This happens on the custom and the EVM board.

Any suggestions would be helpful.

Thanks