Microcode Studio Plus compile/assmebly errors

[mikehagans]

Thanks for the reply.

So far I've only been able to find settings for what folder microcode studio plus looks in for the compiler. It doesn't seem to want me to choose the program. So I made backup copy of pbp.exe and renamed pbpw.exe to pbp.exe... and used that, but when I tried to compile, I got the same "out of memory" and "bad argument" etc. errors...

So, at least based on this, PBPW doesn't appear to solve the issue.

Next I'll try to manually compile and assemble, using pbpw from the command line, and see what happens.

Any other ideas?

Best,

Mike

[mikehagans]

Well - thanks to your suggestion I tried using PBPW manually (no MCS+), and it worked.

C:\design\PBP245>pbpw -ac:\design\mpasm\mpasmwin.exe -p18f4620 x1-x10test.pbp

Produced no errors on the same file that had crashed during compile/assembly inside MicroCode Studio Plus.

Guess I need to get some Mecanique tech support!

Thanks for your help - I'll report back here with how their support works out.

Mike

[mikehagans]

Microcode Studio Plus apparently wants to see MPASM.exe, not MPASMWIN.exe.

My (downloaded through the link on MELABS site) MPASM folder only had MPASMWIN.exe in it. So MCS+ searched around my HD and found an old MPLAB installation with MPASM.exe in the folder! I guess that version or the accompanying inc files didn't support the 18F4620 - so it generated all kinds of bogus errors.

I renamed the (desired) MPASMWIN.exe to mpasm.exe and MCS+ stopped substituting the older version of MPASM, and all is good with the world now.

Thanks for pointing me in the right direction with the PBP.exe vs PBPW.exe. That doesn't seem to have been the issue, but it got me looking at the compiler/assembler settings. Now to gobble up all that newly realized program space! Sure beats the old 16c54!

Best,

Mike

[Archilochus]

Good to hear you got it working!