After downloading the last svn and merging in a normal jallib pack directory structure, I did the compilation and got the same results:
jal 2.4l (compiled Aug 7 2009) generating p-code 0 errors, 0 warnings 2587 tokens, 163250 chars; 4541 lines; 5 files live variable analysis iterations: 3 generating PIC code pass 1 generating PIC code pass 2 writing result Code area: 2010 of 32768 used (bytes) Data area: 37 of 928 used Software stack available: 891 bytes Hardware stack depth 3 of 31 Now I must burn it and test. Vasi On Sep 9, 12:24 am, "a.faber" <[email protected]> wrote: > Yes please give it a try, hopefully you'll get the same hex file, just made > another small update in order to save some bytes (only checking the highest > byte in the user goto function), also i noticed there is a difference > between a pic1814k50 and a pic18f4550 (4 bytes), likely due to a different > register layout, below the compiler output of both: > > Compilation line is : D:\pic\projects\jallib_svn\compiler\jalv2.exe -s > D:\pic\projects\jallib_svn\include\device;D:\pic\projects\jallib_svn\include\peripheral\usb;D:\pic\projects\jallib_svn\include\peripheral\i2c;D:\pic\projects\jallib_svn\include\peripheral\usart;D:\pic\projects\jallib_svn\include\jal;D:\pic\projects\jallib_svn\include\external\lcd;D:\pic\projects\jallib_svn\include\peripheral\pwm;D:\pic\projects\jallib_svn\include\peripheral\adc;D:\pic\projects\jallib_svn\include\peripheral\data_eeprom > D:\pic\projects\jallib_svn\sample\18f4550_usb_bootloader_autostart.jal > jal 2.4l (compiled Aug 7 2009) > generating p-code > 0 errors, 0 warnings > 2587 tokens, 163250 chars; 4541 lines; 5 files > live variable analysis iterations: 3 > generating PIC code pass 1 > generating PIC code pass 2 > writing result > Code area: 2010 of 32768 used (bytes) > Data area: 37 of 928 used > Software stack available: 891 bytes > Hardware stack depth 3 of 31 > > Compilation line is : D:\pic\projects\jallib_svn\compiler\jalv2.exe -s > D:\pic\projects\jallib_svn\include\device;D:\pic\projects\jallib_svn\include\peripheral\usb;D:\pic\projects\jallib_svn\include\peripheral\i2c;D:\pic\projects\jallib_svn\include\peripheral\usart;D:\pic\projects\jallib_svn\include\jal;D:\pic\projects\jallib_svn\include\external\lcd;D:\pic\projects\jallib_svn\include\peripheral\pwm;D:\pic\projects\jallib_svn\include\peripheral\adc;D:\pic\projects\jallib_svn\include\peripheral\data_eeprom > D:\pic\projects\jallib_svn\sample\18f14k50_usb_bootloader_autostart.jal > jal 2.4l (compiled Aug 7 2009) > generating p-code > 0 errors, 0 warnings > 2587 tokens, 153954 chars; 4263 lines; 5 files > live variable analysis iterations: 3 > generating PIC code pass 1 > generating PIC code pass 2 > writing result > Code area: 2006 of 16384 used (bytes) > Data area: 37 of 672 used > Software stack available: 379 bytes > Hardware stack depth 3 of 31 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
