6 Replies Latest reply on May 21, 2015 2:05 PM by user_14586677

    PSOC5LP programing flakiness w/miniprog3 rev B on custom hardware

    content.librarian

      When I attempt to program a PSOC5LP (from PSOC Creator 3.1) using the Rev B miniprog3, the Program operation often halts/does nothing (indefinatly).  Unpluging the USB cable to MiniProg3 releases the stuck program operation.

         

      Similarlay, the Select Debug Target dialog is generally rather slow / non-responsive.  (Eg selecting the window and relocating on the screen, or selecting port properties can take 10 seconds to update)  Often to get anything this to work, each time I try to program, I have to first unplug/plug in the MiniProg USB.  Then select debug target and connect, and then go to program.   This works 25% of the time. 

         

      Programming mode is SWD protocol with reset acquire mode, external power, and 5 pin connector.  Clock speed has been lowered to 200kHz.

         

      I suspect the problem is my prototype hardware with the PSOC, but have no idea what - as flakiy behavior isn't much of a guide to root causing the problem!

         

      My PSOC hardware has 3.1V applied to Vddd, Vio, and Vdda.  1.8V is applied to Vccd and Vcca.  I *believe* power is applied to all pins and they are properly bypassed.   (The package is 68 DFN - which was very difficult to handsolder.  I've inspected w/microscope and believe all the pins are soldered.)  My hardware also lacks a proper programming header, thus I've place the 5 pin connector on the end of the miniprog3 and have 3 inch wirewrap wires going to the hardware.    Miniprog3 is connected to the PSOC pins labeled Vddio1, SWDIO, SWDCK, CFG-XRES, and GND (VssD, VssA).

         

      Once programmed, thus far my rather simple programs (LEDs and UART output) seem to always startup as expected with power cycle, or when the miniprog releases reset.

         

      I know there are lots of unknowns here - but possibly others with more than a few days PSOC experience have tips other than re-run the PCB.  (That will happen once I know most of what is wrong with in....)

         

       

         

      TIA.

         

      Chris