Thanks for coming back.
Yes, have that plug-in. No C at all.
I've never used MCS to program directly. It will drive a picstart plus?
Thanks for coming back.
Yes, have that plug-in. No C at all.
I've never used MCS to program directly. It will drive a picstart plus?
Nope it won't drive PicStart directly. But now i see what you want to do....
With the latest MPLAB version, there's no more ways to launch PICStart from MCS. So what you need to do, is to compile in MCS, then in MPLAB, enable PICSTART, Choose your PIC device, then IMPORT the compiled .HEX file. Once done you just program your PIC.
It's sounds long to do but it works here.
OR you may try PICp...
http://home.pacbell.net/theposts/picmicro/
In theory it's suppose to work, but i've never tried it myself.
Don't give up, you're close!
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Well, that's part of the problem...
If I open blink.pbp and then hit compile and program, it all works fine. If I open mplab and import hex or open asm, it won't program.
when you says you import the .hex file, are you using File >> import in the MPLAB top menu?
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
OK, fixed it thanks to Mr Rentron.
It was the fuses in the include file. Whatever my old mplab settings were it used to burn fine. Now it's set up to use mpasm and I tweaked the include files to forward the settings.
With the right include settings it now works importing hex and building from asm.
I've ordered an MeLabs U2 to burn directly from MCS which should help get me away from the mplab upgrades.
Thanks for your help mister_e.
Bookmarks