On Fri, 31 Jan 2014, Jeff Mitchell wrote:
# Excellent and many thanks! This will be enormously useful!
.. and it was; I was able to get an order of magnitude increase in
processing with this trick.
The DMA problem is still quite a nuisance though; there is other
work to be done
Excellent and many thanks! This will be enormously useful!
--
Have you played Atari today?
> On Jan 31, 2014, at 6:59 PM, Chuck McManis wrote:
>
> CCM isn't used by default. You can add it to the linker script and initialize
> the stack there but its important to realize that the internel peri
CCM isn't used by default. You can add it to the linker script and
initialize the stack there but its important to realize that the internel
peripherals cannot use it, so if you have a function
write_sd_card() {
char some_buf[512];
send_data(some_buf, 512)
...
}
And the send_data fu
Is CCM used by default with launchpad gcc?
I had assumed stack and unknowns are in there..
If we define it in linker can we go nuts in there?
That would make an excellent compositing buffer .. Do a lot of work in there
during dma then blit during vblank ..
Jeffphone
--
Have you played Atari to
On Fri, 31 Jan 2014, Chuck McManis wrote:
# You start running into contention for the AHB bus. This is exactly where
# I'm stuck between an FPGA and a hard place :-) Basically as you start
# running code, the fetches from RAM can interfere with the DMA. There are
# a few things you can do, One
You start running into contention for the AHB bus. This is exactly where
I'm stuck between an FPGA and a hard place :-)
Basically as you start running code, the fetches from RAM can interfere
with the DMA. There are a few things you can do, One there is a memory
space (CCM 64K) which isn't on any
I wonder if anyone has some ideas here, or can clear up some of my
observations.
Project here is a VGA display driven from STM32F4, currently on
the F429 disco board to make life a little easier. Its running great,
image is crisp and sharp, no blurr or jiggle going on (thanks t
