My guess is that Dani needs off-chip xdata access too, otherwise he would not ask for it.
But if he doesn't know what he wants, I don't see how we could help much. And even without interrupts I don't see how checking DMA0XBY and then setting DMA0HLT is an atomic action where the DMA engine cannot get in between. IMO they should have made use of the JBC instruction to capture a combination of these two flags. Finally leaving interrupts on could be a good thing. If you enable the DMA overflow warning interrupt, you could (if fast enough) enable the DMA engine until the warning disappears and then halt it again and return from interrupt. Maarten > Hi Dani, > > List schrieb: > > I'm not sure yet what I want :-) > > :) > > > The problem is that during the dma the on-chip xram does not need any > > special threatment, while the off-chip xram does. > > Would it be correct to say: if you limit DMA to on-chip xram > then according to section 6.3 of: > > http://www.silabs.com/public/documents/tpub_doc/dsheet/Microcontrollers/Precision_Mixed-Signal/en/C8051F06x.pdf > no modification would be needed at all? > Does your application allow for that? > > > I guess section 6.3 probably fails to mention that no IRQ > is supposed to occur between checking DMA0XBY and setting _DMA0HLT ? > > Greetings, > Frieder ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sdcc-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sdcc-user
