Proton version list and previous version downloads?

[PicNoob]

Hey guys,

Old school ProtonIDE user here, most of my dev is on 3.5.0.6 (with the USB dongle). I've moved a few things over to 4.0.5.4, but I always eventually run into some annoying, difficult-to-troubleshoot bug. Like a byte or two in ram randomly changing values when it shouldn't (e.g. an overflow somewhere), or weird stuff with EEPROM scrambling despite doing writing one byte at a time, with a delay, etc. My programs are large and sort of complex, and the issues are somewhat intermittent, so usually it's difficult to properly troubleshoot. Just when I think I've found the issue, it pops up again somewhere else. And I'm forced to go back to 3.5.0.6 to resolve it.

I'm sure the issue with v4 is specific to something I'm doing somehow. But there are several versions between 3.5.0.6 and 4.0.5.4. Is there a list of the available versions and a way to download them so I can test each one?

[kcsl]

As far as I know, this is a complete list.
There's also 4.0.6.1 to add to the list.

[PicNoob]

As far as I know, this is a complete list.

Thanks! I started back in 2009? I think so I know the list goes a lot further back. Do you know if any of the versions are archived anywhere? First one I want to try is whatever the last version was that required the USB dongle.

[RGV250]

Hi John,
I have just emailed you a couple of files 3.7.1.5 and 3.7.5.5 (earliest and latest I have), all the versions make it too large to email.
Let me know if you want some of the ones in between.

Oops, spoke too soon, file too large, I will have to look at we transfer later on.

Bob

[Werwolf]

Hello,
There is a problem with the stability of "Positron16" during compilation. Approximately once in ten times, a different hex file checksum is obtained (in rare cases, a different hex file length is obtained) and the program malfunctions. This happens on two computers, so I can't suspect a computer malfunction. The programs are long (120K words). And this never happened with the old version of "Proton". I have been using "Proton/Positron" for more than 10 years (I have two USB dongles).

Best Regards
Alvydas

[Stephen Moss]

I'm sure the issue with v4 is specific to something I'm doing somehow. But there are several versions between 3.5.0.6 and 4.0.5.4. Is there a list of the available versions and a way to download them so I can test each one?

I could be wrong as my memory is a littel fuzzy, but as I recall 3.7.5.5 was the last version that required a dongle.
4.0.0.0 - 4.0.0.3 would use a dongel or you could paid for update to dongleless
4.0.0.4 Change to Positon, Proton no longer supported, correction updates and upgrades (new commands/devices) not compatible with Proton.

I presume you know that you cannot simply install Positron update over Proton, you have to purchase Positron. Also we are now at verion 4.0.6.1, try opening the Windows Contol panel, go to Programs and uninstalling all Positron Compiller Corrections updates and then then install 4.0.6.1 as it may be that the cause of some of your issues have been resolved in the latest version.
Additionally there have been a lot of changes since Proton support ceased, new commands added, some commands demoted to legacy to prevent the compiler throwing errors but should not longer be used as may not work with newer devices. I did write a program to perform some Proton-Positron conversion, from what you are describing I don't think it will help with your probelm but if you want to try it anyway there in information on what it does here.

If you have not tried it, it may be worth comparing the assembler files created by 3.5.0.6 and 4.0.5.4, if you use a program like WinMerge it will highlight the differnces for you so you won't have to scoure potentially hundereds of lines manually, if there is a difference that may at least help to quickly located where the issue is/the cause of it.

[Werwolf]

The problem in my case is different: when compiling the same unmodified program, sometimes an incorrect checksum is obtained (then there is a problem with the operation of the microcontroller program).

For example:
1st compilation - Hex file CRC 0x2B00
2nd compilation - Hex file CRC 0x2B00
3rd compilation - Hex file CRC 0x2B00
4th compilation - Hex file CRC 0x2B02
5th compilation - Hex file CRC 0x2B00
......

The strangest thing is that I didn't encounter this problem when using "Proton". Mysterious...

Compiler Positron16 ver. 1.1.3.1 (although this was also observed in previous versions). Controllers PIC24FJ256GB106, PIC24FJ256GB110.
Computers (Lenovo):
1. i9-14900K, 64 GB RAM, WIN11
2. i7-8750H, 32 GB RAM, WIN11

Best Regars
Alvydas

P.S. All the specifics of purchasing Positron are well known, no need to remind anyone

[PicNoob]

Hi John,
I have just emailed you a couple of files 3.7.1.5 and 3.7.5.5 (earliest and latest I have), all the versions make it too large to email.
Let me know if you want some of the ones in between.

Oops, spoke too soon, file too large, I will have to look at we transfer later on.

Bob

Perfect if you could message or email me a link that would be great! Google drive and drop box are both popular and easy to use.

[PicNoob]

I'm sure the issue with v4 is specific to something I'm doing somehow. But there are several versions between 3.5.0.6 and 4.0.5.4. Is there a list of the available versions and a way to download them so I can test each one?

I could be wrong as my memory is a littel fuzzy, but as I recall 3.7.5.5 was the last version that required a dongle.
4.0.0.0 - 4.0.0.3 would use a dongel or you could paid for update to dongleless
4.0.0.4 Change to Positon, Proton no longer supported, correction updates and upgrades (new commands/devices) not compatible with Proton.

I presume you know that you cannot simply install Positron update over Proton, you have to purchase Positron. Also we are now at verion 4.0.6.1, try opening the Windows Contol panel, go to Programs and uninstalling all Positron Compiller Corrections updates and then then install 4.0.6.1 as it may be that the cause of some of your issues have been resolved in the latest version.
Additionally there have been a lot of changes since Proton support ceased, new commands added, some commands demoted to legacy to prevent the compiler throwing errors but should not longer be used as may not work with newer devices. I did write a program to perform some Proton-Positron conversion, from what you are describing I don't think it will help with your probelm but if you want to try it anyway there in information on what it does here.

If you have not tried it, it may be worth comparing the assembler files created by 3.5.0.6 and 4.0.5.4, if you use a program like WinMerge it will highlight the differnces for you so you won't have to scoure potentially hundereds of lines manually, if there is a difference that may at least help to quickly located where the issue is/the cause of it.

On my main development PC I have two folders, Proton_NEW with 4.0.5.4 and Proton_OLD with 3.5.0.6. Both execute a ProtonIDE that looks similar but of course, a few commands are different in the 3.5 version, and some newer commands like dim variable as byte = 0 are not supported on the old version. Only one can be open at a time. What is strange is that if I open a program in 3.5 and close it, and open 4.0, that program is still open. So they are somehow linked to some common cache somewhere.

I only use this environment for 18F devices, lately the 26K80 family. For 16bit like 33EV I started in MPLAB (I hate it!) and just stuck with it, as back then there was no Proton support. I know they have since added it with this newer Positron compiler, but I've never tried it. Migrating all the code over sounds daunting, similar to trying to migrate my 8bit code over to MPLAB, which I would never want to do as I prefer to work in the Proton interface. 

For assembly comparison, I've tried it and the outputs of each version are dramatically different. Once I isolated the ram memory location that was being corrupted with a specific v4 build and still couldn't find what was causing the overflow into that memory location, tracing through the assembly output.

[PicNoob]

The problem in my case is different: when compiling the same unmodified program, sometimes an incorrect checksum is obtained (then there is a problem with the operation of the microcontroller program).

That is interesting. I don't check the checksum on mine since compiled firmware is loaded via a custom interface to the device, but different versions will produce different assembly code, which should have a different checksum. If you are not changing versions between that is strange, but you could be able to compare the assembly outputs in that case to see what happened.

[RGV250]

Hi John,

Perfect if you could message or email me a link that would be great! Google drive and drop box are both popular and easy to use.

Did you get the link, I sent it to the jk** one.

Bob

[PicNoob]

RG to the rescue! I now have all the way through 3.7.5.5, which I'm testing now. It produces a code size similar to the v4 series and compiles nice and quick which is great. Now I just need to see if the ram bugs come back! Will update everyone when I know.