now let me ask you a very dumb question but i dont really know this.. what should be done in order to enter the pic into programming mode. ??
ok that is fine but my question is which pins of the pic16f877a should be connected to icsp while programming the pic chip??
also if i choose to use a usb port instead of com port since many laptops do not have a serial port..then the whole design changes..u have design for that?
In reference to general serial communications or a USB based PIC ICSP programmer/debugger
I'd recommend getting ICD2 compatible clone, very cheap and easily available... Mine happens to come from PIC16.com. JDM is great for programming, but to debug makes life much easier, and my MCD2 cost about the same as the parts would for a serial-port JDM
L
confusion
i saw some boards which uses isp cable for programming but how do i interface it with pic.
also if i choose to use a usb port instead of com port since many laptops do not have a serial port..then the whole design changes..u have design for that?
PICs can be *real* cheap ready programmed in bulk.... Look for BLOADER and there is bootloader stuff available for easy USB "firmware update" type setups (just like Arduino have, am I right?)All the diy programmers need a pic chip to be programmed up in the first place
Once you've got the 877 mastered, you'll see it is *so* useful you should just keep a few knocking around... The only shame is the need for an external crystal, there are others 88x line PICs with internal clocks that at least give you an MCU in 3 pins, 0, +, and the reset pin... Don't ever let the programmer set the chip to internal oscilator, (the MCD2 won't let you do it but the JDM programmer does!) and at the same time "ignore the MCLR/reset pin" (both in the "Config Register") on, on older chips especially, it "Locks them in time" as if one-time-programmable Some you can return with a "Vpp before Vdd" option on the standard MCDs, but I still have 3 or 4 16f628A's I try in vain to revive, that are just stuck playing the same routine forever now... Because the PORTB value is being altered by the running code, the programmer can't "get in" to talk to the chip and will never change, an annoyance but not the end of the world....
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?