Hi All - 

Ran into a problem where programming my PSoC 5 works when programming from the Creator 2.1 environment over the miniprog, but fails when I program with a USB bootloader host application (both mine and the tool supplied with Creator 2.1). Digging in, the failure from CyWriteRowFull indicates CYRET_LOCKED.

The failure occurs on ArrayID 1, row 176. Coincidentally (actually,  not..), when programming from Creator using the miniprog, the programming pauses for about 1/2 second at block 452 (452-176 = 256 -- Array Id 1, row 176...).

We have dozens of units that program without issue, and two that present with this problem. All have the same bootloader.

Any ideas? 

Thanks!

Scott,

1.) If you have another PSoC 5 device, you can use the HSSP project provided in AN73054 at http://www.cypress.com/?rID=57435 to find out what exactly is the error code. The code in this AN uses a PSoC 5 as a programmer (like Miniprog3) to program the target PSoC 5 or PSoC 3 device. The code is modular enough for you to go in to the lower level and find the failure status.

2.) Also, I would recommend that you file a tech.support case to get this resolved as well. This would help us in identifying if this is a flash memory issue at the technology level for the device under consideration.

Regards,

Vivek

 Thanks Vivek - 

I will look into the appnote you suggested, and, after I look into a couple more things, will create a ticket as well.

One note - I have just rebuilt my application using the Creator 1.0 and loaded the bootloader using the miniprog. Using the same bootloader host application, I sucessfully programmed the device. Reprogrmming with the bootloader built with Creator 2.1, then programming the application with the Bootloader Host still failed as before.

Regards,

    - scott

 My last post is probably not relevant - I am finding that the failure appears to be data related.

Manually changing the record at that row I can force the programming to either pass or fail. For example, programming the row with all 0, 0xFF, or 0x55 completes sucessfully, Programming only the first byte with 0xA0, and the remainder of the row with 0x00 fails as previously indicated. 

I will submit a ticket for this. If I get a resolution, I will update this post. Thanks.