CY4532 kit not able to boot after loading modified firmware.

Announcements

Live Webinar: USB-C adoption. Simple & Cost-efficient solutions | April 18th @9am or 5pm CEST. Register now !

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

cross mob
Anonymous
Not applicable

I am currently using the CY4532 kit for USB-PD application.

I made some changes in the “CYPD 3171-24LQXQ-cla” firmware and tried flashing its hex using EZ-PD Configuration utility through the I2C Bootloader.

The device did not flash successfully, afterwards the device is not getting recognized also.

In the EZ-PD configuration utility the following message is coming.

0 HID devices found.

1 USB-Serial Bridge devices found.

Could not establish PD contract.

All the jumper settings are fine, I cross checked it. Even the original hex file also is not getting flashed now, because device is not getting recogniZed. The original configuration was getting flashed earlier without any issues.

I have already referred the AN218179 - GETTING STARTED WITH EZ-PD(TM) CCG3PA and verified all the jumper settings and configuration.

0 Likes
1 Solution
RajathB_01
Moderator
Moderator
Moderator
250 replies posted 100 replies posted 50 replies posted

There is a good probability that the board hardware is damaged, since everything else seems to be fine for SWD programming to work.

Trying on a new board is the only way out.

Regards,

Rajath

View solution in original post

0 Likes
15 Replies
RajathB_01
Moderator
Moderator
Moderator
250 replies posted 100 replies posted 50 replies posted

Hi,

Please provide these details -

What changes were made to the firmware?

What was the error seen after unsuccessful programming?

Have you tried to program the default firmware over the SWD header (J1) using miniprog3?

Regards,

Rajath

0 Likes
Anonymous
Not applicable

Hi Rajath,

  1. As we have to control an LED also using this same device so for checking itI disabled all the configurations inside int main() of main.c file. I enabled just 1 PWM to toggle at P2.1 (pin10). and also in configuration I disabled all the charging profiles,
  2. The error that came was

Error: The file/path provided does not appear to exist

Error: Failed to read from file ()

Error: Failed to find valid firmware file for update

Error: Flash update procedure failed

Error: DLL call returned error while flashing

     3. I tried to program default hex file using MiniProg3 but it is not detecting any controller on its SWD head.

0 Likes
RajathB_01
Moderator
Moderator
Moderator
250 replies posted 100 replies posted 50 replies posted

Hi,

Can you specify how you are loading HEX file in EZ-PD Config utility?

For firmware update using EZ-PD utility, use the CYACD file generated after building your project, which will be located at \CYPD3171-24LQXQ_cla\CYPD3171-24LQXQ_cla.cydsn\CortexM0\ARM_GCC_541\Debug\CYPD3171-24LQXQ_cla.cyacd

Browse to locate the firmware file instead of entering file path manually in the Firmware Path 1/2 field.

Does this still produce "Error: The file/path provided does not appear to exist"?

And with the miniprog3 and SWD, a previous unsuccessful firmware update would not be the reason for the device not being detected over SWD.

Re-check all the jumper settings (usually the culprit), make sure the board is not powered by any means, the chip will be powered by miniprog3 VTARG.

Ensure correct (default) settings are used in PSoC Programmer utility. Make sure Power (VTARG) is turned on.

Please also tell what error PSoC Programmer is showing.

Regards,

Rajath

0 Likes
Anonymous
Not applicable

hi,

Yes I am going to the same location at \CYPD3171-24LQXQ_cla\CYPD3171-24LQXQ_cla.cydsn\CortexM0\ARM_GCC_541\Debug\CYPD3171-24LQXQ_cla.cyacd.

I am loading the correct Firmware only. The issue is my controller is not getting detected in the system as I am getting the following message which I said earlier

0 HID devices found.

1 USB-Serial Bridge devices found.

Could not establish PD contract

Earlier PD contract error didn't use to come an it would show that 2 devices are connected,

Now it is showing only 1 device is connected.

0 Likes
lock attach
Attachments are accessible only for community members.
RajathB_01
Moderator
Moderator
Moderator
250 replies posted 100 replies posted 50 replies posted

Please try flashing the default HEX firmware provided with the EZ-PD CCGx Power SDK binaries - EZ-PD CCGx Power SDK\CCGx\Firmware\binaries\CYPD3171-24LQXQ_cla\CYPD3171-24LQXQ_cla_3_2_0_1616_0_0_0_pa.hex (also attached) over SWD and miniprog3.

If it fails post the error message here.

Regards,

Rajath

0 Likes
Anonymous
Not applicable

i tried flashing the firmware and have uploaded the shown error from PSoC programmer.

It is showing the device is not powering up. But I tried powering it up, nothing happened.USB EZ-PD.jpg

I tried to rearrange the jumper settings, nothing worked up.

0 Likes
RajathB_01
Moderator
Moderator
Moderator
250 replies posted 100 replies posted 50 replies posted

Hi,

Please use the RESET programming mode and '5p' Connector in the programming parameters.

Check for power status: ON when programming. Use jumper settings as in kit guide and try again.

Example image:

example.JPG

Regards,

Rajath

0 Likes
Anonymous
Not applicable

Hi,

Discussed with Cypress team in US. They said that we need to use Power Cycle Mode only as the power is taken from the MiniProg3 device only. I connected using 5p connector only. The POWER status is also ON when programming but still the issue remains unfixed.

This issue got corrected once, now again the same problem is occurring.

Regards

Samved

0 Likes
RajathB_01
Moderator
Moderator
Moderator
250 replies posted 100 replies posted 50 replies posted

Hi Samved,

During flashing, can we measure and verify the following voltage levels:

- VDDD = 3.3 V (SWD VTARG) (Test Point TP2)

- VCCD = 1.8V (Test Point TP4)

Also please confirm Jumper J6 on Main board is shorting pin 2 and 3.

Regards,

Rajath

0 Likes
Anonymous
Not applicable

Hi Rajath,

I have the voltage lelvels at both Test Points are as follows:-

-VDDD= 3.28V

-VCCD= 1.83V

jumper at J6 is pointed at VTARG (PINS 2 & 3 shorted).

Still the same issue persists.

Regards

Samved Singh

0 Likes
RajathB_01
Moderator
Moderator
Moderator
250 replies posted 100 replies posted 50 replies posted

Hi Samved,

Also make sure J2, J3, J4, J5 and J7 are not connected (jumper removed).

Does it still say 'PSoC device not aquired' or is it showing a different error this time?

When programming -

> Do the 'Target Power' and 'Busy' LEDs on miniprog3 glow?

> Can you try reading the existing firmware from device (File > Read (F7))?

> Can you try reading the Checksum from device (File > Checksum (F6))?

Regards,

Rajath

0 Likes
Anonymous
Not applicable

Hi Rajath,

All the jumpers (except J6 whose 2 & 3 pins are shorted) are removed.

Target Power LED goes ON and OFF irregularly during whole operation.

BUSY LED doesn't glow at all in MiniProg3

in PSoC programmer it shows BUSY notification for almost 15-20 seconds and then it says

| FAILED! PSoC device is not acquired! Check connection of the chip to the programmer
| Please, check the following items:
|  - the connection between the programmer and the PSoC;
|  - the correct programming protocol is selected;
|  - the correct connector option is selected.

Regards

Samved

0 Likes
RajathB_01
Moderator
Moderator
Moderator
250 replies posted 100 replies posted 50 replies posted

Samved,

What about reading the existing firmware and checksum?

I am able to program, read the existing firmware and validate the checksum as well on my end.

Could you try seperating the Main Board from the Power Board and program the device?

Regards,

Rajath

0 Likes
Anonymous
Not applicable

Hi Rajath,

IMG_20181210_183149148.jpg

I have already separated the Main Board from the Power Board.

You can refer the image attached but still the same issue persists.

Same issue happened earlier but it got rectified as I had not powered up the device using Programmer Utility.

Now same issue has occurred but the previous method of using the Toggling power on PSoC programmer utility is not fixing the issue.

Regards,

Samved Singh

0 Likes
RajathB_01
Moderator
Moderator
Moderator
250 replies posted 100 replies posted 50 replies posted

There is a good probability that the board hardware is damaged, since everything else seems to be fine for SWD programming to work.

Trying on a new board is the only way out.

Regards,

Rajath

0 Likes