Timeline for Is it fairly common to fry a programmer during the learning process of PIC programming development?
Current License: CC BY-SA 3.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Dec 12, 2012 at 20:52 | vote | accept | sacredfaith | ||
Dec 12, 2012 at 20:51 | vote | accept | sacredfaith | ||
Dec 12, 2012 at 20:52 | |||||
Dec 12, 2012 at 19:21 | answer | added | tcrosley | timeline score: 1 | |
Dec 12, 2012 at 19:02 | answer | added | Adam Lawrence | timeline score: 1 | |
Dec 12, 2012 at 16:42 | comment | added | user3624 | I assume that by "fry a programmer", you are referring to people who write MCU code and not a little thing that interfaces your computer to the debug port on the MCU. Given that: Yes it is common to fry a programmer for each project. It appeases the hardware gods and makes it easier to get through EMI/ESD testing. | |
Dec 12, 2012 at 16:23 | answer | added | markrages | timeline score: 3 | |
Dec 12, 2012 at 15:37 | answer | added | Scott Seidman | timeline score: 0 | |
Dec 12, 2012 at 15:07 | review | First posts | |||
Dec 12, 2012 at 15:33 | |||||
Dec 12, 2012 at 15:00 | comment | added | pjc50 | I've never blown up a programmer, because I've always left the programming pins dedicated to programming. The PICKIT is pretty capable and robust. | |
Dec 12, 2012 at 14:51 | history | asked | sacredfaith | CC BY-SA 3.0 |