Freesoc programmer

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Oldfox
Level 1
Level 1
First solution authored First reply posted First question asked

Hi all,

i am using Sparkfuns Freesoc2.

there is a problem with the programmer (Kitprog).

no Kitprog-comport is availible on my win-PC.

for test, i have connected another FreeSoc2 and started PSoc Programmer 3.29.1.

The first is OK, the marked KitProg(CMSIS...)  should be the same Kitprog, but has another name , is passed and connected but NOT powered !!??

Download to target works after debugger-reset, but no com-Port ist availible.

Upgrade Firmware doesnt work for this Kitprog.

 

2xKitprog, 1st OK, 2nd no Com2xKitprog, 1st OK, 2nd no Com

So, what can i do, to get the 2nd Freesoc-debugger to work.

Many thanks forwardly

 Peter

Peda
0 Likes
1 Solution
Hello Len,
 
i have fixed the problem. 🙂
 
The debugger was switched to CMSIS-DAP-Mode by pressing the target-reset for more than 6 seconds.(ok, why i dont know, maybe from a previous user)
Debugger-led starts fading (not blinking)  on/off
At this state the debugger can be switched back to normal mode by pressing the target-reset for more than 6 seconds.
BUT after a short time the debugger-led stays still on, after the fading-state.
Then mode-switching via target-reset doesnt work anymore. !!
Fix1:
- press debugger-reset
- immediately press and hold target-reset while debugger-led is fading on/off
- after about 6 seconds debugger-led shows a short flash and then it is off.
- debugger ist back to normal mode
 
Fix2:
- Started Psoc Programmer
- press target-reset for more than 6 seconds
- debugger returns to normal mode
 
i hope, this info will help other Freesoc, Kitprog users.
 
thanks for your tips
bye
 
OldFox
Peda

View solution in original post

0 Likes
6 Replies
Len_CONSULTRON
Level 9
Level 9
Beta tester 500 solutions authored 1000 replies posted

Peda,

I'm not that familiar with the SparkFun FreesSoc2.  However if it uses the Cypress KitProg firmware (which it looks like it does), you somehow got it into the second of two modes that the KitProg supports.  This mode is the CMSIS-DAP mode.   You want it in the first mode to programming and debugging.

I couldn't find any info on the SparkFun site about this mode and how to get into and out of it.  Let's try a couple of simple things knowing how the KitProg works on the Cy8CKIT-059.

I noticed on the SparkFun  site two buttons:  A "Debugger BTN" and "Debugger RESET".   

Experiment #1:

  • With the Debugger USB port plugged in and powered, press the "Debugger BTN"  for 6 seconds.  If all goes well the PSoC Programmer will no longer list the CMSIS-DAP next to the KitProg.

If this didn't work ...

Experiment #2:

  • With the Debugger USB port plugged in and powered, press the "Debugger RESET"  for 6 seconds.  If all goes well the PSoC Programmer will no longer list the CMSIS-DAP next to the KitProg.

If neither of these experiments worked, I'm at a loss at this time.

 

Len
"Engineering is an Art. The Art of Compromise."
0 Likes

Hi Len_Consultron,

many thanks for your fast answer.

i tried out all two experiments without sucsess.

but may be your info will helf, if i do a call to sparkfun.

thanks

 peda

Peda
0 Likes

Peda,

You're welcome.   I don't have a FreeSoc2 board so my further help may be limited.

Len
"Engineering is an Art. The Art of Compromise."
0 Likes

sparkfun has answered, but actual no real solution.

we do our best and stay in contact.

thanks

Peda
0 Likes

Peda,

I have one more suggestion to try.

Normally in CMSIS-DAP mode, a new virtual drive appears on your computer.  In this case it would be called "KitProg"  It will also have a drive letter associated with it.

See the pic below how it appears on my computer in the Explorer window.

Len_CONSULTRON_0-1624615899513.png

It you click on the drive to open it you get a file listed as "STATUS.TXT".

Len_CONSULTRON_1-1624616028657.png

Here's the experiment:

Find the compiled code for your project.  It should be in the 

<project_folder>\<project_name>.cydsn\CortexM3\ARM_GCC_541\Debug\<project_name>.hex      or

<project_folder>\<project_name>.cydsn\CortexM3\ARM_GCC_541\Release\<project_name>.hex 

Drop this file onto the KitProg drive.  It should try to download the binary for the project into the FreeSoC2 target CPU.   It may not work.  According to the "STATUS.TXT" file, this works on the PSoC4 family only.  I figure it is worth a try.

I'm not sure you can debug in this mode though.

Len
"Engineering is an Art. The Art of Compromise."
0 Likes
Hello Len,
 
i have fixed the problem. 🙂
 
The debugger was switched to CMSIS-DAP-Mode by pressing the target-reset for more than 6 seconds.(ok, why i dont know, maybe from a previous user)
Debugger-led starts fading (not blinking)  on/off
At this state the debugger can be switched back to normal mode by pressing the target-reset for more than 6 seconds.
BUT after a short time the debugger-led stays still on, after the fading-state.
Then mode-switching via target-reset doesnt work anymore. !!
Fix1:
- press debugger-reset
- immediately press and hold target-reset while debugger-led is fading on/off
- after about 6 seconds debugger-led shows a short flash and then it is off.
- debugger ist back to normal mode
 
Fix2:
- Started Psoc Programmer
- press target-reset for more than 6 seconds
- debugger returns to normal mode
 
i hope, this info will help other Freesoc, Kitprog users.
 
thanks for your tips
bye
 
OldFox
Peda
0 Likes