Live Update 3.3.3. for mikroPascal PRO for PIC32 released!

[anikolic]

Live Update 3.3.3. for mikroPascal PRO for PIC32 released!

Latest Live Update 3.3.3. is here. Make sure to update your Pascal compiler to get new features and improvements.



We have supported a new Touch Panel Controller found on the hot new mikromedia plus for PIC32MX7
via Touch Panel STMPE610 library. It works through I2C interface. Library for the new ILI9341 TFT controller
is added as well. I2C Library now has universal routines, just like SPI Library. You can just use the Set Active
function to select which I2C module you want to use, and then call these new universal routines.
This dramatically cuts coding time when you want to switch to another I2C module in your application.
We have implemented support for Hardware MAC Address on ENC24J600 Ethernet module.
Ethernet_Init is no longer a blocking function. In PortExpander Library new routines are added,
so you can now work with each single PORT pin.

We've added new sets of examples for mikromedia Plus for PIC32MX7 and
mikromedia for PIC32 9A (with new display MI0283QT_9A).

Minor improvements have been made in IDE, as well as ADC, Conversions, PS2 and USB libraries.

From this release, besides updating using Help->Check for updates option in your compiler you can
also download complete setup for mikroPascal PRO for PIC32. Receive all updates and improvements right away!

Yours sincerely,
mikroElektronika

[jpc]

after updating i get : There is no shadow set [ICS_AUTO] context saving can not be used, use [ICS_SOFT] instead irq_uart.mpas on this declaration

Code: Select all

procedure Timer1Int(); iv IVT_TIMER_1; ilevel 6; ics ICS_Auto;

, which worked ok before so i wonder what is wrong

[LGR]

I just did check for update for the first time from 3.3.0, and it found 3.3.1. Is this normal to go through the minor revisions one by one? Shouldn't it go directly to 3.3.3?

[dejan.odabasic]

Hello,

Could you please tell me which MCU are you using for your development?

Best regards.

[jpc]

Dejan,

the pic used is P32MX250F128D, in order to verify i went back through older versions, the same source that builds ok in verions 3.3.0 and 3.3.1 produces this error in 3.3.3

I hope you can fix this soon,

regards jpc

[dejan.odabasic]

Hello,

Unfortunately, this is not an error. Shadow register is not present on PIC32MX1XX/2XX devices.

Note: On PIC32MX1XX/2XX devices, the
dedicated shadow set is not present

This error message is implemented in the latest version of compiler in order to avoid the possible surprising behavior of the MCU.

Best regard.

[jpc]

ah, now that you say that i checked again in the datasheet and realize these are confusing, they mention the shadow set in several places but then i found a note saying that this dedicated shadow set is not present on these chips.
Thanks for explaining this, i now ask myself how it worked before .

Regards jpc

[jpc]

one little remark on this however, in my code i had the option ICS_Auto selected, would it not be possible that the compiler in this case just assigns the software context save/restore ? It seems to detect the situation right, it would be elegant if the AUTO in this situation would behave as such.

regards jpc

[dejan.odabasic]

Hello,

... i now ask myself how it worked before

...would it not be possible that the compiler in this case just assigns the software context save/restore

This was the case before update but we noticed that many users have experiencing some troubles because they were not aware that shadow register is missing.

Since only the ICS_SOFT option is available, we hope that disabling the ICS_SRS and ICS_AUTO will prevent the possible confusion.

Best regards.

[jpc]

i have my doubts about the 'many users' but can understand avoiding confusion. However for that it would be ok to throw a warning instead of disabling, i personally had no problem with the old system ( must admit i was unaware of the absence of the shadow-set) simply giving a warning that the compiler had decided to use soft_ics would be good enough i think.

Anyway, thanks for the full explanation