From: Frans S. <fra...@gm...> - 2010-05-26 08:07:07
|
On 05/26/2010 05:35 AM, Jasper Wallace wrote: > On Tue, 25 May 2010, Frans Schreuder wrote: > > >> Dear Jasper Wallace, >> >> You are right, thank you for the patch! I have applied the changes in >> the subversion repos and in the 0.4.0 firmware release. >> > Thanks, if i use uc_code.hex from svn I can write the data ok! > > However now the 2nd config word has stoped working! > > I think the attached patch will work (I'm looking at the 39607c > datasheet). I wonder how it ever worked in the 1st place! > Hmm, this is weird... but your patch seems to be right. I have built it and put in the svn. Could you try again? > >> About the warnings, this is part of the Microchip usb stack, and I have >> seen them but let's just ignore those warnings. >> > yup, but the linker error means i can't generate firmware to test with :( > Also this is weird. Maybe the difference is in the student version. I did get a full version of the c18 compiler from a formal job (they didn't use it anymore). And now I am still able to upgrade with the latest upgrades. > I've using: > > mcc18: > > MPLAB C18 v3.35 academic Copyright 2000-2010 Microchip Technology Inc. > > mplink: > > MPLINK 4.35, Linker > > the linker command line is: > > wine mplink /k/ rm18f4550.lkr /l/home/jasper/.wine/drive_c/MCC18/lib/ > /ouc_code.cof /muc_code.map main.o usbdsc.o interrupt.o usbmmap.o usbgen.o > usb9.o usbctrltrf.o usbdrv.o upp.o prog.o prog_lolvl.o > > >>> Unfortunatly i cant test it beacause the C18 compiler failes to link >>> usbdsc.o with this error: >>> >>> Error - section '.romdata_usbdsc.o' can not fit the section. Section >>> '.romdata_usbdsc.o' length=0x000000ae >>> Errors : 1 >>> > > > > ------------------------------------------------------------------------------ > > > > > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > |