David 'Miller' Lowe
2017-06-29 19:05:04 UTC
Hi List folks,
I have been using openocd.0.9.0 to flash and debug an NXP KL03Z processor
with an IBDAP CMSIS-DAP adaptor off my workstation for the past year or
so.
We are using the same setup off a beaglebone to load the image into the
KL03Z on our production line.
I recently updated to openocd.0.10.0 and noticed that I had to make the
same change in order to maintain my remedial openocd use.
in
src/flash/nor/kinetis.c
In kinetics_read_part_info() I had to add a 'case 0x01' to the
switch(fcfg1_nvmsize) around line 1373.
I arrived at the change by adding a bunch of logging and admit that I don't
remember the details of the change just that someone (more knowledgeable
than I) may want to investigate if it's a valid change to post upstream.
Miller
I have been using openocd.0.9.0 to flash and debug an NXP KL03Z processor
with an IBDAP CMSIS-DAP adaptor off my workstation for the past year or
so.
We are using the same setup off a beaglebone to load the image into the
KL03Z on our production line.
I recently updated to openocd.0.10.0 and noticed that I had to make the
same change in order to maintain my remedial openocd use.
in
src/flash/nor/kinetis.c
In kinetics_read_part_info() I had to add a 'case 0x01' to the
switch(fcfg1_nvmsize) around line 1373.
I arrived at the change by adding a bunch of logging and admit that I don't
remember the details of the change just that someone (more knowledgeable
than I) may want to investigate if it's a valid change to post upstream.
Miller