Hi,
I did not set a part number since the OMAPL-137 (not the high temperature) is not listed in the drop down menu.
I'm currently dealing with a integration issues where I have code that works on the DSP side of the omapl137 using sysbios and when I launch the arm counterpart the dsp stops working. I think my issues is related to how I'm using the timers. The DSP is using timer0 as the sample clock for a adc. This is done in the generating pulse mode. This pulse also drives a GPIO interrupt and a SPI_RX interrupt. Both of these interrupts, the GPIO and the SPI_RX, control the pace of tasks using semaphores. If I connect to the target and launch just the DSP, I'm able to hit breaks points on all the tasks paced by this interrupts.
I've followed the instructions of the following thread and tried multiple combinations. Even though the suggestion is to make the arm the master, which I have also tried, the omapl137 is reversed. The dsp wakes up the arm, reason why I have tried both settings: DSP as master while ARM set to false, and vice-versa.
As soon as the arm .out is loaded, without even running it, the timer on the DSP register, timer0, changes to 0b101110111000000 = 24000 in decimal. This is different than the timer0 settings set by the dsp when initially launched and ran. I looked in the GEL and could not see anything on the arm side besides mapping memory sections.
Basically I'm trying to load and run code in the arm without disrupting the settings already set for the timer0 in the DSP.