[OMAP3530] Mistral EVM and CCS

Chris Saulnier said:

I can connect to the EVM, I can compile my code, load it onto the board and then tell it to run. My problem is that when I try and view memory all of the locations are filled with zeros and I can not change the values manuially

This is fairly unusual, in general if you can load code to the board successfully it indicates that at least the memory you are loading to is writeable and readable, so you should be able to do the same with the view memory window, if you cant read/write the memory you will get a load error. Which memory in particular are you trying to access (i.e. internal RAM, DDR, etc.)?

Chris Saulnier said:

Any idea what I'm doing wrong?

 In general memory access problems in CCS tend to stem from the GEL file you are using in your CCS configuration, what GEL file are you using?

Thank you, you're right. That is a strange problem because it's not the problem I was having at all.

What I'm concerned with right now is trying to set up a McBSP so I was looking at the memory mapped addresses associated with that, which my code should be changing / I used to be able to change myself. Upon examining locations of memory which contained data things work just fine and as expected.

I guess I have to ask a different question, why is it I would be unable to setup the McBSP registers. It's a pretty generic qustion I know - but at least you got me on the right track!

Thanks,

Chris

Chris Saulnier said:

What I'm concerned with right now is trying to set up a McBSP so I was looking at the memory mapped addresses associated with that, which my code should be changing / I used to be able to change myself. Upon examining locations of memory which contained data things work just fine and as expected.

I am glad to hear the actual memory accesses are working, that clears things up.

Chris Saulnier said:

I guess I have to ask a different question, why is it I would be unable to setup the McBSP registers.

My suspicion would be that the McBSP you are using has not been powered up, that is, it is probably still in a low power state. The OMAP3 has a lot of power saving features, including the ability to have many of the peripherals effectively disabled to keep from wasting any power. Typically this initialization would be done by a boot loader or a driver so you may use these as reference for the initialization; if your board is not booting u-boot or a OS it is possible your particular McBSP was never powered up, for details on the power and clock management options in the OMAP please see the PRCM chapter of the TRM.

Hey,

As I mentioned before I had this project working in the past, and now I have a slightly different setup which is likely using a different .gel file that is no longer setting some register that I required.

I've gone through the McBSP and PRCM documentation and must be missing something.

I enable the functional clock (FLCKEN1_CORE |= 0x200) and I also enable the interface clock (ILCLKEN1_CORE |= 0x200) for McBSP1. However within the CM_IDLEST1_CORE register bit 9 does not turn off, meaning that the McBSP is still idle. 

I have code written to go through and enable DMA to use with the McBSP, and the DMA bit (2) turns off meaning that it becomes active.

Any idea as to what else I have to do to make the McBSP become active?

Thanks,

Chris