Proteus don't show all variables

aphawk · Joined: 23 Jan 2010 Posts: 168 Location: Brazil

Hi,

I can confirm now that there are some compatibility problem with the object files from BASCOM 2.085 and PROTEUS VSM STUDIO.

I have some files archived with Bascom source and objects files, with Proteus simulation, made in 2020.

I openned this old files with Proteus 8.9 SP0 , and all variables are showing correctly.

But if I recompile the source with Bascom 2.085, and reuse then to simulate in Proteus 8.9 , the FLAG type variables and all the INTERNAL type variables are not showed !

I don't know from what BASCOM version this happens, but my object files had this date : 15 february 2020.

Someone can verify this ?

Paulo

albertsm · Joined: 09 Apr 2004 Posts: 5921 Location: Holland

we shared info about the DBG format with the developer of Proteus and they added support for watching variables.
We always got a license to test things.
But since some years we do not get a license anymore (emails to developer are unanswered).
So we stopped support for proteus/isis. Which means when we change the DBG format when required (longer field lengths for Xtiny register names for example), proteus probably has some problems.
I consider this is a proteus problem and it should be addressed at labcenter.

they did not implement xmega and i doubt (but did not checked) if they will support xtiny/megax/avrx.

aphawk · Joined: 23 Jan 2010 Posts: 168 Location: Brazil

Hi Mark ,

Thanks for the precise answer about the problem.
I will send email to Proteus support about this.

Paulo

aphawk · Joined: 23 Jan 2010 Posts: 168 Location: Brazil

I found that the last Bascom version that maintain full compatibility with Proteus is 2.0.8.3.

Paulo

albertsm · Joined: 09 Apr 2004 Posts: 5921 Location: Holland

while MCS supports Xmega, xtiny etc. labview did not(did not checked if they do now). So we extend bascom for new AVR processors and need to make changes in OUR DBG structure to support longer register names for example.

It is proteus which is incompatible to bascom not the other way around !
Next time open a ticket at labview.