Log in

View Full Version : Command Line operation ni a BATCH file



flotulopex
- 16th February 2026, 20:02
Hi All,

I'd like to launch the compiler/assembler and the PICKit3 programmer, all in COMMAND LINE mode, in a DOS batch file.

Unfortunately, I'm getting error messages at compile/assemble time.

According to Melanie's posts, I have programmed my batch file as here (the PICKit part is left out for now):

Path C:\Program Files (x86)\PBP3_1;C:\Program Files (x86)\PBP3_1\temp
PBPX -p16F690 -aMPASMX Blink_16F690.pbp -v


Obviously, my PBP3 compiler's location is "C:\Program Files (x86)\PBP3_1" and the assembler's one is C:\Program Files (x86)\PBP3_1\temp.

Launching the BATCH file, I'll get these messages:
1003910040


I get 5 "Access violation" errror windows I can clear and at final, everything seems okay = every thing works (I get the HEX file I can send to the PIC).

Any idea how I can make things work the "clean way" please?

flotulopex
- 17th February 2026, 19:03
Problem solved: just needed to run the BATCH file with administrator's rights.

flotulopex
- 17th February 2026, 21:29
No, still not solved yet :frown:

When the batch file is launched with admin rights (I made a shortcut file to my batch to be able to launch it with admin rights), all HEX, ASM, etc files are not created?!?!?

flotulopex
- 18th February 2026, 17:02
I tried to move my batch file in the PBP folder but the problem still perists.

flotulopex
- 20th February 2026, 16:38
I'm now using MPASMWIN.EXE (even if the assembler's window says "MPASM v5.14") which solved the problem about the warnings.

Now, is there a way, like for Microcode Studio, to close this assembler's windows once done successfully?

10041


I can't find any command line argument doing this for me

richard
- 21st February 2026, 00:54
try an
echo/ after the mpasm line in your batch file