Thanks Thomas.
Your K22FN512 has DIEID 0x1d as described in
http://cache.freescale.com/files/microcontrollers/doc/eng_bulletin/EB811.pdf
kinetis_read_part_info() should check DIEID and distinguish FTFA versions
from FTFE ones for chips with new ID in similar way as it does for old ID.
As #2867 has been reviewed I'm not going to put more changes into it.
Please upload your own change for review.
And if you want to help, http://openocd.zylin.com/#/c/2958/
needs a review - it is kind of trivial change and I'd like to have it
merged before I upload
new work: I fixed FlexNVM/data flash handling in Kinetis driver.
Tom
On 25.09.2015 17:47, Thomas Schmid wrote:
Oh, I am not worried about the chip. I have done this before while
trying to fix openocd. I just used my PE Micro debugger to reflash it.
Needed a full chip erase to get back.
And for the openocd hardware, we are using the Olimex ARM-USB-TINY-H
with the SWD adapter.
For the SDID:
> mdw 0x40048024
0x40048024: 22001e95
These are all recently bought K22FN512's, so I guess they moved to the
new format with this rev.
Attached is the debug for a connect, some "reset halt" the mdw, and
then an attempt at programming it.
And I just tried to program a KL16FN128. Worked like a charm!
- Thomas
On Thu, Sep 24, 2015 at 11:08 PM, Tomas Vanek
<[email protected] <mailto:[email protected]>>
wrote:
Thanks for offer.
KL parts mostly use one flash configuration so they should work.
I let you know if we need your kits for testing.
Tom
On 25.09.2015 2:56, Pink Boy wrote:
> On Thu, Sep 24, 2015, at 06:29 AM, Tomas Vanek wrote:
>
>> But the basic problem remains: absolute lack of testers, no
support from
>> Freescale and therefore low motivation for me and other developers.
> I could test this stuff, however, have never been very sure which
> debuggers to use for Kinetis.
>
> I do have a P&E Micro Multitec which 'works' And a Segger whatever
> which I could never get to work.
>
> Currently I've been working with KL15/16 and KL36 parts using a
USBDM
> programmer/debugger. That's worked well enough for now.
>
> Matt
>
>
------------------------------------------------------------------------------
> _______________________________________________
> OpenOCD-devel mailing list
> [email protected]
<mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/openocd-devel
>
------------------------------------------------------------------------------
_______________________________________________
OpenOCD-devel mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/openocd-devel
------------------------------------------------------------------------------
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
