PSoC Programmer 3.28.x not working for PSoC6 with Generic DAPLINK hardware

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

cross mob
Kevin_Lo
Employee
Employee
50 sign-ins 10 likes given First comment on KBA

Hi Everyone,

Our customer was using generic DAPLINK hardware along with PSoC programmer 3.27.3 to program their own PSoC6 custom PCBA.

Working without issue until updated to 3.28.x which failed to access the PSoC6 with the same set of hardware worked with 3.27.3.

We would like to confirm if the backward compatibility for DAPlink (old?) is removed since PSoC Programmer 3.28.x

pastedImage_2.png

pastedImage_0.png

Thanks and Regards,

Kevin

0 Likes
1 Solution
DheerajK_81
Moderator
Moderator
Moderator
First comment on KBA First comment on blog 5 questions asked

Most likely it is related to new and changed transport algorithms in PP3.28 for KitProg3 and MiniProg4 support. Besides the older transports, we test MiniProg3/4, KitProg1/2/3 and ULINK2, but we do not test other hardware with PSoC Programmer. So we cannot comment on this since we don't test with this.

Please use the software provided by the generic DAPLink hardware if any.

Regards,

Dheeraj

View solution in original post

0 Likes
3 Replies
DheerajK_81
Moderator
Moderator
Moderator
First comment on KBA First comment on blog 5 questions asked

Can you please provide a screenshot of DAPLink mode being able to program in PSoC Programmer 3.27.3? I tried to test on both the versions 3.27 and 3.28 and was unable to program. Please provide more information on the hardware and the steps to recreate your error.

Regards,

Dheeraj

0 Likes

Hi Dheeraj,

When I using PSoC Programmer 3.27.3 with the same hardware set, I have no problem for accessing the PSoC6 on customer board with the DAPLINK.

pastedImage_0.png

attached photo of the DAPlink which is similar to generic DAPLINK with a USB2.0 Hub+ PL2503 +STM32F103

pastedImage_7.png

Thanks and Regards,

Kevin

0 Likes
DheerajK_81
Moderator
Moderator
Moderator
First comment on KBA First comment on blog 5 questions asked

Most likely it is related to new and changed transport algorithms in PP3.28 for KitProg3 and MiniProg4 support. Besides the older transports, we test MiniProg3/4, KitProg1/2/3 and ULINK2, but we do not test other hardware with PSoC Programmer. So we cannot comment on this since we don't test with this.

Please use the software provided by the generic DAPLink hardware if any.

Regards,

Dheeraj

0 Likes