Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Hi, thank you so much for taking the time in replying. can you elaborate on the answer I have used the same code by modifying syntaxes for esp32 Arduino ide, but it is not able to achieve all the steps. can you suggest how can I move further.
I have only a relatively small knowledge about the ESP32. I'm not sure how I can help you. I was monitoring your original discussion about the ESP32 and the PSoC and found the link that MIGHT be related to your inquiry.
Len "Engineering is an Art. The Art of Compromise."
In your previous post, you mentioned that you were able to successfully program PSoC 5 LP device using another PSoC 5 LP. As you have a logic analyzer, comparing the traces to figure out at what point the process is failing might help.
You should verify esp32 is meeting the setup and hold time specification on the SWDIO pin relative to the SWDCLK pin. SWDIO timing is quite critical, especially when turning the direction of this bi-directional pin.
As Rakshith mentioned, you can compare 5LP to 5LP programming logic analyzer trace with that of esp32 to 5LP trace. With the two documents listed here, you'll be able to find exactly where the SWD programming protocol fails (since these doc's also show a successful trace).