Swordfish

Thanks Jerry...

It needs to be the same - the compiler does not track ANY user changes

If some user code modifies BSR, the user code is responsible for restoring it.

I would say that the compiler should not really be allowing this comparison, as there is no internal mechanism for making the comparison (at least, not as far as a remember). There is a mechanism for strings, which are very similar in terms of comparing a block of data but not for structures. My onl...

You can find it here

http://www.firewing.info/pmwiki.php?n=F ... P8266-MQTT

I think Labcenter have gone down the route that everything should be centered around their IDE, which means they have pulled support for a standalone simulator (ISIS). I think the only viable future is source level debugging, as Jerry previously mentioned. This thread may also be of use: http://sfco...

$long-hex-filename$ => pass fully qualified hex filename to loader
-dPIC$target-device$ => PIC device
-iprogram => start programming, don't show loader interface
-b<baudrate> => COM buadrate
-c<COM> => COM port

The "UMC Firmware" button needs to be in the down state when using firmware designed for it...

I've posted the file here:

http://www.sfcompiler.co.uk/wiki/pmwiki ... ardLibrary

Thanks again for sharing...

Thanks for posting these changes. They look like they could be really useful. If you email me the new, modified library, I could post on the wiki for others to share..

This is also worth checking out

http://www.sfcompiler.co.uk/wiki/pmwiki ... User.W5500

I've also worked with the ESP8266 WiFi chip with Firewing with good results. Depends what you want to do I guess...

I haven't written a plugin for ages - John B used to be pretty adept, maybe try contacting him for tips...

http://sfcompiler.co.uk/phpBB3/memberli ... rofile&u=8

> are there any compiler constants for the size of the various variables I don't understand the question > Personally, I'd say this is the sort of check that would be better done in the IDE It would not work for all those people using MPLAB/X to compile their code. > wouldn't be picked up anyway unl...

The IDE is always still under development, should user demand require it. However, I think you can achieve what you want in code, which should work fine for byte and word size constants: #variable aval = 200 #variable bval = 56 #variable rval = aval + bval #if rval > $FF #warning "rval out of range"...

Top tip... You also have to be very careful using interrupts when "writing to globals", particularly if the data is greater than 8 bits (1 byte). For example, your main program may be reading the first byte of a 16 bit value then an ISR triggers. The word variable gets changed, you return to the mai...