cancel
Showing results for 
Search instead for 
Did you mean: 

PSoC 4 MCU

Anonymous
Not applicable

I have a miniprog3 attached to a CYBLE-012011 PRoC 4 device. I can program the device with PSoC Creator and with the graphical PSoC Programmer - but I am running into trouble with the command line version. Even though I am setting the protocol to SWD it seems to fail with "Device is not in ISSP mode" error. 

Here is my console output: 

Windows PowerShell 
Copyright (C) 2016 Microsoft Corporation. All rights reserved. 

PS C:\Users\ba\firmware_server\factory> & 'C:\Program Files (x86)\Cypress\Programmer\ppcli' 

>OpenPort MiniProg3/1540BB000009 "C:\\Program Files (x86)\\Cypress\\Programmer" 

0 OK 
>HEX_ReadFile "c:\\Users\\ba\\firmware_server\\sumpit\\v2_cypress.hex" 
<0x00020000 
0 OK 
>SetAcquireMode "Reset" 

0 OK 
>SetProtocol 8 

0 OK 
>SetPowerVoltage 3.3 

0 OK 
>SetProtocolConnector 0 

0 OK 

>Acquire 

Device is not in ISSP mode. 
Acquire returned 80004005 
80004005 OK 
>

   

 

   

Am I doing something wrong?  I am surprised that it is trying to use ISSP mode since the manual says that protocol 8 is SWD.

0 Likes
Reply
1 Solution
RyanZhao
Moderator
Moderator

Hi Eric,

   

I didn't find how to upload picture....Here is an example of correct operation text:

   

>OpenPort MiniProg3/1519DD0007D9 .
<
0 OK
>SetProtocol 8
<
0 OK
>SetProtocolConnector 1
<
0 OK
>SetAcquireMode Reset
<
0 OK
>SetProtocolClock 152
<
0 OK
>SetPowerVoltage 5
<
0 OK
>PowerOn
<
0 OK
>DAP_Acquire
<
0 OK
>PSoC4_GetSiliconID
<0e 09 11 9e
0 OK
>PSoC4_ReadRow 0x00
<00 40 00 20 11 00 00 00 39 04 00 00 39 04 00 00 80 b5 00 af 00 f0 14 fa 80 b5 0
0 af 1e 4b 12 22 1a 60 01 f0 9f f9 1d 4b 18 1c 00 f0 ad ff 01 20 01 f0 a8 f9 0c
20 00 f0 d9 ff 19 4b 19 4a 1a 60 19 4b 80 22 d2 05 1a 60 18 4b 18 4a 12 68 02 21
 0a 43 1a 60 16 4b 17 4a 1a 60 17 4b 16 4a 12 68 08 21 8a 43 1a 60 fa 23 db 00 1
8 1c 01 f0 0a f8 12 4b 18 1c 01 f0 5a f8 11 4b 80 22 12 06 1a 60
0 OK
>ClosePort
<
0 OK
>quit
<OK

   

C:\Program Files (x86)\Cypress\Programmer>

   

 

   

Thanks,

   

ZRZ

View solution in original post

0 Likes
Reply
9 Replies
Anonymous
Not applicable

Hi,

   

This error is likely to occur when the power supplies are not proper. Can you please check the same. I understand that PSoC Programmer is working fine for you. But just in case, can you make sure if this is the case in your recent setup?

   

Regards,

   

- Madhu Sudhan

0 Likes
Reply
Anonymous
Not applicable

The power supply is a Hi-Link dc 5v 3watt power supply and it is run through a linear regulator to get to 3.3v, it isn't the problem.  If the power supply was the problem then PSoC creator and PSoC gui programmer would also fail.

0 Likes
Reply
RyanZhao
Moderator
Moderator

Hi,

   

Could you use command DAP_Acquire instead of Acquire to try again?

   

Thanks,

   

ZRZ

0 Likes
Reply
RyanZhao
Moderator
Moderator

Hi,

   

Forgot this:

   

With using MiniProg-3, reset mode, before useing DAP_Acquire, use PowerOn command.

   

 

   

Thanks,

   

ZRZ

0 Likes
Reply
Anonymous
Not applicable

PowerOn followed by DAP_Acquire seems to hang for a long time in the powershell window on the programming computer, and eventually return an error code of 80004005.   The PRoC device itself seems to go into a reboot loop, which is different from what happens when I use PSoC Creator or the graphical PSoC programmer (when I use those to program the device it pauses execution on the PRoC until the programming is done).

0 Likes
Reply
RyanZhao
Moderator
Moderator

Hi Eric,

   

I don't have kit for now. Tomorrow I will make a screen shot of successful operation.

   

Thanks,

   

ZRZ

0 Likes
Reply
RyanZhao
Moderator
Moderator

Hi Eric,

   

I didn't find how to upload picture....Here is an example of correct operation text:

   

>OpenPort MiniProg3/1519DD0007D9 .
<
0 OK
>SetProtocol 8
<
0 OK
>SetProtocolConnector 1
<
0 OK
>SetAcquireMode Reset
<
0 OK
>SetProtocolClock 152
<
0 OK
>SetPowerVoltage 5
<
0 OK
>PowerOn
<
0 OK
>DAP_Acquire
<
0 OK
>PSoC4_GetSiliconID
<0e 09 11 9e
0 OK
>PSoC4_ReadRow 0x00
<00 40 00 20 11 00 00 00 39 04 00 00 39 04 00 00 80 b5 00 af 00 f0 14 fa 80 b5 0
0 af 1e 4b 12 22 1a 60 01 f0 9f f9 1d 4b 18 1c 00 f0 ad ff 01 20 01 f0 a8 f9 0c
20 00 f0 d9 ff 19 4b 19 4a 1a 60 19 4b 80 22 d2 05 1a 60 18 4b 18 4a 12 68 02 21
 0a 43 1a 60 16 4b 17 4a 1a 60 17 4b 16 4a 12 68 08 21 8a 43 1a 60 fa 23 db 00 1
8 1c 01 f0 0a f8 12 4b 18 1c 01 f0 5a f8 11 4b 80 22 12 06 1a 60
0 OK
>ClosePort
<
0 OK
>quit
<OK

   

C:\Program Files (x86)\Cypress\Programmer>

   

 

   

Thanks,

   

ZRZ

View solution in original post

0 Likes
Reply
Anonymous
Not applicable

ZRZ - thanks!   that got me further, but not all the way.  My DAP_Acquire passes, but now I fail on calibrate with the same error message (Device is not in ISSP mode).

Here is the entire list of commands that I think I need to run:


OpenPort MiniProg3/1540BB000009 "C:\\Program Files (x86)\\Cypress\\Programmer"
HEX_ReadFile "c:\\Users\\ba\\firmware_server\\sumpit\\v2_cypress.hex"  
SetAcquireMode "Reset"  
SetProtocol 8  
SetPowerVoltage 3.3  
SetProtocolConnector 0  
SetProtocolClock 152
PowerOn
DAP_Acquire
Calibrate
EraseAll
Program
Verify
VerifyProtect
Protect
Checksum
HEX_ReadChecksum
ClosePort
 

   

>DAP_Acquire
<
0 OK
>Calibrate
E
Device is not in ISSP mode.
Calibrate returned 80004005
80004005 OK
>

0 Likes
Reply
RyanZhao
Moderator
Moderator

You're welcome. Calibrate command is not suitable for PRoC, please bypass it....

   

 

   

Thanks,

   

ZRZ