When try to acquire your board, has other target module on the board been removed?
Which BLE module are you using? Double-check the module number your are using is same with the target module.
There is no other target module on my custom PCB. You may be confusing the question with the CY8CKIT that I mentioned only for comparison's sake. My PCB consists of ONLY a CYC84248LQI-BL583 processor, an EEPROM, and some comm lines to a few sensors.
The possible reason is the hardware design/connection issues, such as the Bypass Caps at the power supply Vddx/Vccx pins(please check the device datasheet or CY8CKIT-042-BLEA kit design files for this). Also please refer to the article below if you can debug the issue.
Hi Ron -
Can you confirm you have the latest download of PSOC Programmer installed? Should be 3.28.0:
Within PSOC Programmer, you should be able to do a Checksum of the firmware in the part. Doesn't matter what is in the part, what you are looking for is that PSOC Programmer can identify your device properly. If it can, then PSOC Creator should be able to communicate with the device for debug, as it uses PSOC Programmer's drivers to communicate with the part.
Let's start there first and see the result.
1 of 1 people found this helpful
After a closer look at the design, it was determined that the VCCD OUTPUT from the PSOC 4 was tied to VDDD, but that VDDD was operated at > 1.8V. When this connection was removed, and the required capacitor was tied from the VCCD pin to ground, the part was identified, programmed, and operated properly.