Hello,
My device is broken it starts until the Atmosphere screen then it stops with the blue LED continu on, no further activity.
-None of the resets helps
-New 'out of the box firmware.bin' does not help.
-Other .bin files from the NXP website will upload to the device but end in the same screen.
M 0060370000127D20
ID 410486749406069B
I know i was a early adapter but this lifetime is very short,
Greetings,
Hans Volbeda (Netherlands)
Eric,
THANKS! that was the trick, it works fine now but i don't understand how, how does the device know in what part of memory it must be and in what chip if i upload it just by dropping it by USB programming?
-I didn't try the KW41Z hybrid application because;
I tought that i needed a Hexiwear dockingstation in order to programm the bootloaders as i read in the manual here; 4.1.5. (Re)Programming of K64F and KW41Z Bootloaders.
In the attached picture i understood that you have to select the chip with the dip switches before programming, that did I understand, just dropping it in by usb i don't understand.
But thanks again, i am happy that it works again…..
Hans Volbeda.
Very glad to read it is fixed.
To answer your question:
Without docking station, K64 parses the binary and detects whether it is a K64 binary or a KW41 binary and passes on to KW41Z when applicable. As the only 'input' is USB directly to K64, K64 needs to mange this
On a docking station it goes though K20 first via USB and then, we can redistribute the signals directly to the right micro controler via the switches:
This also explains why it is very easy to overwrite bootloaders with a docking station while it is not easy when kit is directly plug to PC via USB
On my side I am not clear how you succeeded in corrupting KW41Z wo a docking station... you are the first user to my knowledge who achieved this :smileygrin:
