Hey folks,
Kinetis flash driver really needs more of your love. There's even a
known issue[1] for that. Please stand up and start sending patches,
as none of the active OpenOCD maintainers and users have enough time
and resources to do that without your participation.
[1] https://sourceforge.net/
Have you been able to reset the K64? We are using a KDS patched openocd
with some other modifications to support some of the newer K22 chips.
Unfortunately, the reset doesn't work and we don't know why. We see the
reset line toggle, but the device doesn't reset and just keeps executing at
the same
On Sat, May 16, 2015 at 8:00 AM, Peter Meerwald wrote:
> > This was all done with the openocd executable that I build locally. I
> > haven't actually been able to run the KDS openocd executable (which was
> > your original suggestion) because our interface scripts target the ft2232
> > and the
> >>> Thank you for the quick response. The openocd executable provided with
> >>> the KDS seems to expect a CMSIS-DAP device and driver. We are using the
> >>> Olimex ARM USB OCD H pod to connect directly to the JTAG pins on our MCU.
> >>> I have tried modifying their scripts to use the Olimex
On Fri, May 15, 2015 at 6:45 PM, nothing fire wrote:
> If we define additional banks in the kinetis configuration, we get to the
> same issue that we had originally:
>
> Error: ftfx command fialed FSTAT: A0 FCCOB: 0B00 0100
> Error: error writing to flash at address 0x at
If we define additional banks in the kinetis configuration, we get to the
same issue that we had originally:
Error: ftfx command fialed FSTAT: A0 FCCOB: 0B00 0100
Error: error writing to flash at address 0x at offset 0x
On Fri, May 15, 2015 at 6:43 PM, nothing fir
I am sorry, I misspoke. The error was not an unsupported CPU, it was that
the kinestis configuration only defines one flash bank so that when we
attempt to program it, the flash operation immediately fails.
The gdb console indicates that it attempted to load the .text section and
failed. When we
Thank you for the quick response. The openocd executable provided with the
KDS seems to expect a CMSIS-DAP device and driver. We are using the Olimex
ARM USB OCD H pod to connect directly to the JTAG pins on our MCU. I have
tried modifying their scripts to use the Olimex driver instead, but it g
Hello,
> The user manual for my MCU indicates that it has 4 blocks (512 KB each) of
> program flash consisting of 4 KB sectors. I set my board config file up
> like this:
>
> flash bank pflash.0 kinetis 0x 0x8 0 4 $_TARGETNAME
> flash bank pflash.1 kinetis 0x0008 0x8 0 4 $_TA
The user manual for my MCU indicates that it has 4 blocks (512 KB each) of
program flash consisting of 4 KB sectors. I set my board config file up
like this:
flash bank pflash.0 kinetis 0x 0x8 0 4 $_TARGETNAME
flash bank pflash.1 kinetis 0x0008 0x8 0 4 $_TARGETNAME
flash bank
10 matches
Mail list logo
