cancel
Showing results for 
Search instead for 
Did you mean: 

ModusToolbox™ General

Anonymous
Not applicable

Hello,

I tried to program my KitProg (PSoC® 6 Wifi-BT) using the PioneerKitApp, and I get a message:

Error: *********************************************************************************************

Error: * KitProg firmware is out of date, please update to the latest version using fw-loader tool *

Error: *********************************************************************************************

Error: No Valid JTAG Interface Configured.

Where do I find the fw-loader tool and latest firmware?

Enrico

0 Likes
1 Solution
mattl_01
Employee

Hey Enrico,

Sorry about that.  Everything you need is right there in the installation.

See Chapter 7 of the User Guide, starting on page 54. The first thing

you want to see if your kit has kitprog2 instead of kitprog3. It probably

does.

Assuming you are on windows, open a  cmd window. Then, run the command

fwloader --device-list

Yes, that is two dashes "--"

If it says something like Kitprog2 blah blah blah then, run the command

fwloader --update-kp3

Let me know if that doesn't work. By the way, fw-loader is in $CYSDK/tools/fw-loader-1.0/bin.

You can probably do all this without even opening up the User Guide.

If you want to then use that kit with PSoC Creator, you need to first run

fwloader --update-kp2

to go back down to kp2.  You wouldn't have to do this after the next release of Creator though.

There is one other issue regarding SW3 on the board, but try this first. It should fix you up.

--Matt

View solution in original post

7 Replies
mattl_01
Employee

Hey Enrico,

Sorry about that.  Everything you need is right there in the installation.

See Chapter 7 of the User Guide, starting on page 54. The first thing

you want to see if your kit has kitprog2 instead of kitprog3. It probably

does.

Assuming you are on windows, open a  cmd window. Then, run the command

fwloader --device-list

Yes, that is two dashes "--"

If it says something like Kitprog2 blah blah blah then, run the command

fwloader --update-kp3

Let me know if that doesn't work. By the way, fw-loader is in $CYSDK/tools/fw-loader-1.0/bin.

You can probably do all this without even opening up the User Guide.

If you want to then use that kit with PSoC Creator, you need to first run

fwloader --update-kp2

to go back down to kp2.  You wouldn't have to do this after the next release of Creator though.

There is one other issue regarding SW3 on the board, but try this first. It should fix you up.

--Matt

View solution in original post

Anonymous
Not applicable

I'm on a Mac.  I can see that it is mounted as KitProg2 on the desktop.

Here are the commands I used through Terminal:

/Applications/ModusToolbox_1.0/tools/fw-loader-1.0/bin/fw-loader --device-list

Result:

Cypress Firmware Updater, Version: 1.0.0.505

(C) Copyright 2018 by Cypress Semiconductor

All Rights Reserved

Info: Start API initialization

Info: Connected - KitProg2 CMSIS-DAP HID-XXXXXXXXXXXXXXXX <- to mask my HID

Info: Hardware initialization complete (465 ms)

No connected supported devices

Tried the --update-kp3 command and got the same result.  Doesn't seem to recognize the hardware.

Enrico

mattl_01
Employee

OK, give me a second. I don't want you to push that SW3 switch until I check the documentation one more time.

0 Likes
mattl_01
Employee

OK, first you need to get your kit out of "CMSIS-DAP HID" mode.  To do this, you press SW3 on your board.

SW3 is near the left-side, a little less than halfway up (I have my board oriented where the USB part connected

to the PSoC 5 used for programming is on the left-hand side and the CapSense area is on the bottom right).

After pressing that button, LED 2, right below the SW3, should go from OFF (which I hope it is now) to ON.

Now, you should be able to run fwloader --update-kp3

I think we need a blog post on this.  There is information in the User Guide, but that is a little inaccessible

and doesn't have enough on messages you might see.

0 Likes
Anonymous
Not applicable

Ok.  Here are my results once having used SW3 so that the LED is on.  My Mac (MacBook Pro 2013) indicated that the device was no longer connected.  I think this worked with your assistance.  Agree that the posts need to be a little more step by step for noobs like me. : )

Ran the following command in Terminal:

/Applications/ModusToolbox_1.0/tools/fw-loader-1.0/bin/fw-loader --device-list

Result:

Cypress Firmware Updater, Version: 1.0.0.505

(C) Copyright 2018 by Cypress Semiconductor

All Rights Reserved

Info: Start API initialization

Info: Connected - KitProg2-XXXXXXXXXXXXXXXX

Info: Hardware initialization complete (464 ms)

Connected supported devices:

  1: KitProg2-XXXXXXXXXXXXXXXX FW Version 1.5.0

It did recognize the device!

Ran the following command to update the firmware:

/Applications/ModusToolbox_1.0/tools/fw-loader-1.0/bin/fw-loader --update-kp3

Result:

Cypress Firmware Updater, Version: 1.0.0.505

(C) Copyright 2018 by Cypress Semiconductor

All Rights Reserved

Info: Start API initialization

Info: Connected - KitProg2-XXXXXXXXXXXXXXXX

Info: Hardware initialization complete (469 ms)

Device 'KitProg2-XXXXXXXXXXXXXXXX' opened successfully

Info: Kit FW is 'KitProg2' ver. 1.05 b000. Upgrade file is 'KitProg3' ver. 1.01 b158

Info: Disconnected - KitProg2-XXXXXXXXXXXXXXXX

Info: Connected - KitProg Bootloader-XXXXXXXXXXXXXXXX

Info: Bootloader Version: Major 1, Minor 1, Build 40

Info: FW Upgrade to version: 1.01 b158

Info: Bootloading ...

Info: Verifying ...

Info: FW Upgrade completed

Info: Connected - KitProg3 CMSIS-DAP BULK-XXXXXXXXXXXXXXXX

FW update completed successfully

Info: Disconnected - KitProg Bootloader-XXXXXXXXXXXXXXXX

I went back to Modus and tried to build and it appears to have completed successfully.

These were the last few lines in the build status window:

wrote 18432 bytes from file /Users/edepaolis/mtw/PioneerKitApp_mainapp/Debug/PioneerKitApp_mainapp_final.elf in 0.813853s (22.117 KiB/s)

** Programming Finished **

** Program operation completed successfully **

srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst

Info : SWD DPIDR 0x6ba02477

shutdown command invoked

I'll have to try the blinky app and see if that works as I am still learning all this stuff at this point and am not sure what the basic program I loaded is supposed to show.  I'll continue the testing tomorrow.  Thank you for assisting this far.

Enrico

Anonymous
Not applicable

I was able to load the Blinky app to the board so it appears to be working.  Thanks again for the assistance!

Enrico

0 Likes
mattl_01
Employee

Excellent, sorry for the difficulty.

0 Likes