MicroCode Studio oddity...

[Ioannis]

Thanks Norm. I will be looking forward to.

@ mtripoli: it is indeed very annoying when that happens. I learned my lesson and hit the Ctrl+S all the time. Almost annoyingly often .

Ioannis

[mtripoli]

Yeah... I hit the save key pretty often myself...

@Norm: I downloaded and am using your IDE; very impressive. I've been using it for about half an hour and it's been tooling right along.

I'm using the PICKIT3 programmer. I saw the setup string for firing the programmer, but when it comes up I still have to load the uC and program manually (I'm using a 16F1946). Anyone got any ideas on getting this to program automatically? I think my device declaration is wrong as well; I still don't have the declaration format correct for using Microchips programmers (@ DEVICE HS_OSC,WDT_OFF,BOD_OFF,LVP_OFF,PROTECT_OFF) doesn't work...

[Ioannis]

Are you using the stand alone software for Pickit3?

If yes, it has the auto import hex and write button. Just click it to turn on the feature.

Ioannis

[mtripoli]

Yes, I'm using the PICKIT3 software... and the "auto import". I'm referring to a way that the programmer starts and programs without having to hit the "auto import" button. I know that there is a command line version of the PICKIT2 available in which you can do this; I haven't looked yet for the same for the "3".

[HenrikOlsson]

Hi,
This is what I use from within MCSP:

-P$target-device$ -F$hex-filename$ -E -M -B -L -V5

And the exutable is called PK3Cmd.exe which I don't think is the same as the standalone programmer software for the PK3.

The -V5 is said to specify the voltage output on the Vdd line by the PICKit3 so be careful if you're using a 3.3V PIC etc.

/Henrik.

[mtripoli]

Thanks Henrik, that did the trick.

[Demon]

I also get the auto-correct oddity in MCSP since I updated (I had an old version).

(system specs below)