Hello,
i see, we are in the else section.
>From the Family Reference Manual:
For devices with FlexNVM: FlexRAM
For devices with program flash only: Programming acceleration RAM
So this needs an extra test if FlexRAM available and if so fall back to the
long word sequence!?
Regards,
Mathias
Hi Morgan,
On 08/03/12 18:37, Morgan Quigley wrote:
> I just wanted to toss this observation out there and see if others
> have noticed this. I am happy to submit a patch if there are no
> objections.
Please do, I can try to test it on both the TWRK60 board and the Kiwkstik.
Tomas
>
> Cheers,
Hi Matthias,
On 08/03/12 19:01, Mathias K. wrote:
> you need the ram to use the section command. If there is no flex ram
> available (read from the status
> word) the algorithm fall back to the long word programming.
I thought that was the case myself, hence the patch I made and was
committed to
Hello,
you need the ram to use the section command. If there is no flex ram available
(read from the status
word) the algorithm fall back to the long word programming.
You should check if the:
/* make flex ram available */
and
/* check if ram ready */
correct for your cpu.
On some devices t
Hello,
I was experiencing slow Kinetis K60 writes using Olimex and Amontec
FT2232-based dongles on a custom board I designed around a
PK60N512VMD188, and looked into it a little bit. The question deals
with the kinetis NOR flash driver.
I found that bypassing the logic which always causes program
