I found an app note 3897 here: http://cache.freescale.com/files/32bit/doc/app_note/AN3897.pdf
It references: "Download the source files for the EzPORTSoftwareDemo (EzPORTSoftwareDemo.zip)". Can I please get a copy of this demo?
I'm looking for examples of using the QSPI on a coldfire 5271 in wraparound mode, which this app note refers to.
If you have any other examples of the coldfire QSPI being used in wraparound mode I'd settle for those...
Thanks
Thanks, we'll take a look at the qspi code...
Thank you.
Now I know the file name, searching for "AN3897SW.zip" on Freescale's site brings up this link:
http://cache.freescale.com/files/32bit/doc/app_note/AN3897SW.zip
That has a "EzPORT/Source/driver/qspi.c" file in it that might tell you what you need to know.
Tom
I use STICKOS to download .s19 files using QSPI. I'm not sure if it supports your board, but it's the only thing I could find that lets you do it.
I can't find "EzPORTSoftwareDemo.zip" anywhere. Google can't find it. I can't even find it on archive.org. I'm guessing it has been removed because it was 'developed and tested with CodeWarrior for Coldfire v6.4 and v7.0", and since they're no longer available, you can't compile it any more. So rather than update the example software, they've removed it.
You only hope is if someone reading your post has a copy hidden away somewhere, and you can get CW7.0, can spend time converting it, or you just want to read the sources for hints.
> If you have any other examples of the coldfire QSPI being used in wraparound mode I'd settle for those...
Wraparound mode is documented in the Reference Manual. It allows the SPI to keep going. From the App Note: "The SPI code implements the wraparound mode avoiding chip select deassertion". The problem with that would be keeping the data up to the QSPI so it doesn't run ahead. Maybe they're using the "HALT" bit to try and control the speed. I don't know why they're doing this. It should be far simpler to just reprogram the Chip Select as a GPIO and drive it from software instead of trying to get the QSPI to do this.
I guess you need to look at the code to work that out.
The App Note also says: "The first half of the queue is send and receive, while the other half is read and write. Then both halves continuously alternate functions.".
I have no idea what that means. From my understanding of the QSPI it doesn't make any sense.
From your post it doesn't look like you're trying to download using EzPort; you're just looking for a "Wraparound" example. I'd suggest reading the QSPI chapter in the manual a few more times.
Using Wraparound is as simple as just setting the WREN bit. Then your software just has to keep ahead of the QSPI, loading new data into the RAM and reading data out of it. If you're using the QSPI to simply read some external ADCs, then you can simply read the returned results when your code needs the latest value from the RAM. Set-and-forget.
Tom