• Locked Locked
  • Replies 4 replies
  • Subscribers 100 subscribers
  • Views 485 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

OMAP3530 - Quick BeagleBoard c64x+ Ext Memory Mapping?

Joe Engineer
Prodigy 30 points
Other Parts Discussed in Thread: OMAP3530

I'm an experienced c64x/c64x+ developer but am new to the OMAP. I got a BeagleBoard and (using CCS + SD XDS510USB+)  I can load/run small c64x+ programs from L1/L2  DSP RAM.  At the moment  I don't care about the ARM. My next step is to run a larger/full c64x+ application from external memory w/cache enabled.  I assume I need to configure the memory controller to map the external memory to the c64x memory space either through GEL commands or from a simple ARM stub program (if possible c64x code would be better).  All I need is a few lines of code/gel commands to map the memory (possibly configure wait states) and/or know the c64x address spaces the memory gets mapped to. I see from an earlier post that the GEL \cc\gel\omap3430_sdrc_configs.gel has the setup for the Micron DDR memory on the Beagle. Will this also map it to the DSP space, if so where (what address ranges)?    Unfortunately the Beagle sites are all very ARM-centric and the Projects are very complex and huge.  I just want the c64x core to be able to access the external memory so I can load/run my DSP application. Seems trivial but I've spent hours on it so far with no luck. What I'm doing seems like the logical first step for someone transitioning from  a standalone c64x to the OMAP so I'm sure someone has quick solution.

  • TI__Mastermind 41665 points

    Joe Engineer said:
    Will this also map it to the DSP space, if so where (what address ranges)?

    The DSP by default has the MMU disabled so it is directly connected to the physical memory map within the device, therefore DDR is in the same place as it is for the ARM, starting at 0x80000000, so when you initialized the DDR with the GEL file you should be good to go for both ARM and DSP to access it.

    Essentially you should be able to run the GEL file to configure the DDR (assuming the Beagle Micron DDR uses the same config) and than access memory locations starting at 0x80000000, I have yet to try connecting to Beagle with CCS but I have done it with the Mistral EVM and was able to get it to work.

     

  • Prodigy 70 points

    Hi Joe,

    I am newbie to OMAP, BB and TI processor. I bought beagle board. I am planning to use this as development platform first as I am new to this TI world, after familiarizing I will start some simple audio application.

    Here I have queries

    1. Can I use Beagle board as ref. platform for developing audio algorithms or simple applications for TMS320C64x+ DSP( which is in OMAP3530 ) ignoring ARM

    2. What are the hardware and software tools required to start the development and learn things on TI ( I heard CCS is one such tool )

    3. how I can test any algorithm/application developed

    4. Please suggest whether I can use BB as starter or is there any other alternative for starting algorithm/application development
    5. it will great if you can tell what are the IDE and other tools required to start learning the work on TMS320C64x+ ( which is on OMAP3)

    It will be great help for me to learn TI and proceed further. Please point me to right direction.

    Thanks in advance

    Hari

  • in reply to emperor410
    TI__Mastermind 37340 points

    Hari,

    I believe I just answered the same questions here: http://e2e.ti.com/forums/p/7458/28891.aspx#28891

  • in reply to Juan Gonzales
    Prodigy 70 points

    Jaun,

    Yes, I saw the message. Actually I posted my query in seperate thread and then while browsing I saw this thread is some waht relavent to my requirement. So I also posted here to get quick response.

    Sorry if any inconvenience caused.

    Thank you.