Quantcast
Channel: Processors forum - Recent Threads
Viewing all articles
Browse latest Browse all 17527

OMAP L138 Application running SPI Flash boot mode problems

$
0
0

Hello all,

I have a custom board with LogicPD OmapL138 SOM on it.
I use SYS\BIOS to run both of the ARM+DSP cores, the ARM core is in charge of waking the DSP (inside the code).
I used AIS generator to make a joint ARM+DSP ais file.
I flashed the SPI1 Flash for booting the device.
In my program the ARM core is talking to UART devices and I2C camera (+VPIF) and both of the cores are communicating through Notify and it is working OK in standalone mode.

I encountered the following problems:

1. While debugging the camera operation in standalone mode, I get exception for simple driver calls such as: VPIFInterruptEnable or VPIFInterruptDisable (doesn't happen in emulation mode) but the exceptions are gone when I just use the direct assertion s.a.: 

/* Enable VPIF interrupt */
HWREG(SOC_VPIF_0_REGS + INTEN) |= 0x00000003;
HWREG(SOC_VPIF_0_REGS + INTSET) |= 0x00000003;

2. Flashing of the facedetect program to the DSP (with the opencv libs) is taking forever and at the end, the arm core is stuck while booting never having the chance to wake up the DSP core (this is the same project as the working project I mentioned before but with the opncv libraries linked). The ais file size is: 2.5MB.

3. OLED screen using SPI1 communication doesn't work,  is it possible to use SPI1 when booting from SPI1 flash?

4. The current consumption of the SOM is about 50% higher when working in standalone mode.

Can anyone enlighten me on those subjects?

Thanks,
Yoel 


Viewing all articles
Browse latest Browse all 17527

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>