cancel
Showing results for 
Search instead for 
Did you mean: 

PSoC 6 MCU

StSc_1311791
New Contributor II

When I execute following command I get an error.  See attached log.  The init and create-keys commands worked as expected.

cysecuretools --target CY8CKIT-064B0S2-4343W --policy ./policy/ policy_single_CM0_CM4.json provision-device

0 Likes
1 Solution
Rakshith
Moderator
Moderator

Hi Stan,

Can you try running the following command to erase the flash and then provisioning the device? -

pyocd erase -s 0x10000000-0x101E0000

Please attach the log for both the operations.

Thanks and Regards,

Rakshith M B

Thanks and Regards,
Rakshith M B

View solution in original post

0 Likes
6 Replies
Rakshith
Moderator
Moderator

Hi StSc_1311791​,

The provisioning of the device is failing as flash is not empty. When the tool detects that the flash is not empty, it asks the user to erase it. Please try to run the provisioning again and select 'y' when the following user interactive prompt appears:

Erase user firmware running on chip? (y/n):

Please let me know your observations.

Thanks and Regards,

Rakshith M B

Thanks and Regards,
Rakshith M B
0 Likes
StSc_1311791
New Contributor II

Rakshith,

I am never asked that question.

Stan

Sent from Mail for Windows 10

0 Likes
Rakshith
Moderator
Moderator

Hi Stan,

Can you try running the following command to erase the flash and then provisioning the device? -

pyocd erase -s 0x10000000-0x101E0000

Please attach the log for both the operations.

Thanks and Regards,

Rakshith M B

Thanks and Regards,
Rakshith M B

View solution in original post

0 Likes
StSc_1311791
New Contributor II

Rakshith,

I attached the log for the provision-device command. It appears to have worked! Yea! The pyocd command generated output to the screen but no separate log file was generated, or at least I couldn’t find it.

Stan

Sent from Mail for Windows 10

0 Likes
StSc_1311791
New Contributor II

Perhaps you can help me with another issue.

I am trying to go through the Modus Toolbox section of the Secure Boot SDJ User Guide, revision *D. Everything appears to have worked until I try to run the program (page 32). I then get the following output:

Stan

Open On-Chip Debugger 0.10.0+dev-3.0.0.665 (2020-03-20-10:13)

Licensed under GNU GPL v2

For bug reports, read

http://openocd.org/doc/doxygen/bugs.html

    • Main Flash size limited to 0x1D0000 bytes

Info : auto-selecting first available session transport "swd". To override use 'transport select '.

adapter speed: 2000 kHz

    • Using ACQUIRE_TIMEOUT: 15000 ms

    • Using POWERUP_DELAY: 5000 ms

    • Using TARGET_AP: cm4_ap

Info : Using CMSIS loader 'CY8C6xxA_SMIF_S25FL512S' for bank 'psoc64_smif_cm4' (footprint 6928 bytes)

srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst

Warn : SFlash programming allowed for regions: USER, TOC, KEY

Error: unable to find CMSIS-DAP device

Error: No Valid JTAG Interface Configured.

Sent from Mail for Windows 10

0 Likes
Rakshith
Moderator
Moderator

Hi Stan,

I think the KitProg3 is still in DAPLink mode. This might help -

pastedImage_1.png

You can find this information on Page 40, in the Kit Guide. Please let me know if it helps.

Thanks and Regards,

Rakshith M B

Thanks and Regards,
Rakshith M B
0 Likes
Top labels