Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About NoFuture

  • Rank
  1. Finally figured it out... The culprit was my JDM programmer. With new pics with internal oscillators. The programmer would raise VDD and VPP at the same time, starting the program that was just encoded in the chip, the program counter would increase, rendering programming impossible. All that was needed was to modify the circuit so that the programmer would have control when to raise VDD or VPP. Here is the solution: http://users.tpg.com.au/btkelly/jdm_b.htm Very simple and cheap... Thanks for your help guys...
  2. Here it is... #pragma DATA _CONFIG, _PWRTE_ON & _WDT_OFF & _CP_OFF I see that you are supposed to have hex code right after the DATA, is it possible that BoostC thought the "_CONFIG_" was the config word ???? If DATA is for the config word, then why do you add _WDT_OFF and stuff after ???
  3. I used BoostC. ic-prog told me that there was no configuration word and then offered me to set my own within the program. The programming worked and then, I tried the chip on the beadboard and it did what it was supposed to do. When I tried to reprogram it with a corrected version of the program i'm working on, ic-prog (and other programming software) would act like there was no chip plugged in the programmer. Anyway, I'm starting to think I'm the one who screwed up by taking for granted that the program would do everything for me.
  4. I checked the Mclr pin with a multimeter and it goes up to 13v. Still can't figure out what the problem is. I'm starting to think that I got a bad batch of chips. I one week I'll be able to try with another programmer so we will see.
  5. I tried bulk erasing the chip but it did not work. I think I will juste blame it on my cheap programmer (15USD on ebay) and build myself another one when I get the time and money. In the meantime, I will just wait for my other chips to arrive. Thanks anyway
  6. I don't really know precisely what happened but now, I cant reprogram my three PIC16F628A chips. I think it has something to do with SourceBoost (or me ) because all 3 became write/read protected right after I programmed them using the .HEX file Sourceboost produced. They were working correctly when I was using .HEX files from MPLab or MikroC. I am using a JDM (serial) programmer and ic-prog and I am sure that the CP fuse was not enabled because I always check all fuses in ic-prog just to make sure. The only problem is that it took me a while to figure out where the fuses were in the Sourceboost IDE, so they were not set to my specifications (but CP is always OFF anyways) at the time of build. I was not a big deal to me because ic-prog would let me set the fuses anyway. I even tried on other computers and with Winpic... Anybody knows why ?? Is there a way to erase the whole chip ??? Thanks
  • Create New...