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.

Spectrum Digital User Interface Board for DA830 EVM DA830 EVM / OMAP-L137 Starter Kit) and /dsplink/dsp/scr/samples/scale project

Other Parts Discussed in Thread: OMAP-L137

Hello I am trying to add User interface LCD support
(I.E. using the Spectrum Digital User Interface Board for DA830 EVM DA830 EVM / OMAP-L137 Starter Kit)
on my MAP-L137 Starter Kit.
I have successfully built and run the Spectrum Digital DSKDA830 User Interface Board Test Code
uiboard/lcd lcd.pjt.

I am now trying to merge this LCD test code into the /dsplink/dsp/scr/samples/scale project, i.e on the dsp side...

(Actually, I'd like to have it reside on the gpp side, but that's another question.)

I have managed to compile it and attempt to run it and it is crashing at the
void plot(Uint16 x, Uint16 y, Uint16 pixeldata)
{
    *((Uint16 *)(FRAMEBUF_BASE + 32 + y * 640 + (x << 1))) = pixeldata;
}
function in lcd_test.c

I am theorising there is some conflict somewhere with the FRAMEBUF_BASE being located at
#define FRAMEBUF_BASE 0xc0000000..

Maybe? 
How would I even begin to debug or track down how to fix the problem, if indeed it is where the trouble is located?
I wish there was more documentation on the Spectrum Digital User Interface Board for DA830 EVM DA830 EVM / OMAP-L137 Starter Kit,
i.e. why is the
FRAMEBUF_BASE 0xc0000000
hard-coded and located hear.

Any help would be greatly appreciated... Thanks Brian

  • Hi Brian,

    LCD uses the SDRAM to store the buffers and on OMAP-L137 SDRAM is mapped to 0xc0000000. So FRAMEBUF_BASE is set to 0xc0000000.

    By default, lcd.pjt test code works on the DSP side. So DSP should not have any problem in accessing the address 0xc0000000. I am not sure whether you need to take care of anything else from the dsplink perspective to get it working.

    Regards, Sudhakar

  •  

    Thanks Sudhakar

    So is it true as long as I locate FRAMEBUF_BASE somewhere in SDRAM and have enough space to accommodate the FRAMEBUF_BASE + size that I can change it?

    Thanks Brian