Unable to execute MPASMX

[HenrikOlsson]

Hands up those who'll throw $100 Charles way to support him.
If we'd setup some sort of crowdfunding compain, how much do you guys think we'd raise? My guess - enough to cover a couple of hours worth of work….Never the less, if it'll help Charles/MeLabs I'd certainly pitch in.

It sure looks like learning C is, by far, THE best bet if you're in this for the long run and want to keep up with new offerings. Until the day PBP goes subscription I'll keep hoping and be willing to support MeLabs by paying reasonable (which certainly has been the case this far) upgrade charges.

I did look at Swordfish and it had zero updates for YEARS (according to the version history), then all of a sudden it sprung to life again. I wonder if they rely on MPASM and how they'll this, same with MikroE - I don't know how their stuff "works" but something tells me they're not relying on MPASM and they certainly have more Resources available to stay compatible with Microschip.

[Ioannis]

I did look at Swordfish and it had zero updates for YEARS (according to the version history), then all of a sudden it sprung to life again. I wonder if they rely on MPASM and how they'll this, same with MikroE - I don't know how their stuff "works" but something tells me they're not relying on MPASM and they certainly have more Resources available to stay compatible with Microschip.

It seems that they rely on MPLBX: https://www.sfcompiler.co.uk/wiki/pm....SystemConvert but is a good option now they support it again.

As for the MikroE, previous versions had a lot of bugs. Also produces more code than PBP. So, for me it is a no at this moment.

Ioannis

[tumbleweed]

(swordfish) I wonder if they rely on MPASM

Yes they do, but since it's only for the PIC18F series it's a little easier for them.

I understand they'll be extending the existing MPASM to deal with new chips for a while, at least until mchip change something else
in the 18F that makes it not work anymore.