- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi PSoC6 enthusiasts!
after exciting experimenting with Pioneer kit and generally sucessfull tests of demo & examples
I decided to make a small "facelift" and change KitProg2 into KP3.
Thanks to clear instructions, additionally supported with community posts I went to KP3 smoothly.
To be precise I decided to upgrade KP to the most recent release, using quite handy fw-loader.
But here I encountered some issues/ surprises...
The first, most funny is the message from PSoC programmer:
Port Opened with Warnings KitProg3 version Expecting 1.01.158, but found 1.10.2946.
and... my bad luck - I had auto-upgrade selected thus my "hard work" with obtaining most current version was lost...
I realized that v1.01.158 is a bit...lame... Lack of DapLink support, unclear ... or faulty ... functionality of SW3 (mode selection)
forced me to the second attempt...
After disabling auto-upgrade I installed v1.10.2946 again
I started to enjoy the new tool. Easy availability of three modes: CMSIS-DAP Bulk + CMSIS-DAP HID + DapLink delights indeed!
Now I realized, that attempts of upload of selected firmware, using mass - storage (DapLink) fails:
FAIL.TXT
error: The hex file cannot be decoded. Checksum calculation failure occurred.
type: transient, user
As I wrote above: only selected, some .hex were accepted, remaining rejected...
These binaries came from tested, successful build and were accepted when programing directly from PSoC Creator or WICED
I'm afraid I need some fine-tuning around DapLink driver etc. but presently no idea what to fix...
and the last (minor) issue...
really... why? the kit is quite fresh!
If you have some thoughts in that matter(s) I will be grateful!
Marek
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I tested the "Drag-and-Drop Programming" feature of DAPLink mode just now, and found that the hex files generated by PSoC Creator are invalid to be used under DAPLink mode.
You have to use mbed to generate the required hex files. I guess there are some differences between the file formats.
Just follow the steps shown in the part "Getting Started with Mbed OS" of the following link - PSoC 6 BLE Pioneer Kit | Mbed