Hi Albert, Last night I finished my first "blink a LED" test in SDCC 2.9.7 without destroying your bootloader. Next step (and without this, I would not take SDCC into consideration) is to convert your USB libraries (I don't touch the headers in any way) but I'm a little scared by the task. Anyway, I must start somewhere...
I also successfully tested a modified version of Diolan USB HID Bootloader from which XTEA encoding part was removed (same memory space occupied - 2Kb) but this is another story ( I found this version of bootloader in this project: http://dangerousprototypes.com/2010/01/29/prototype-usb-infrared-remote-control-receivertransmitter/ ) Vasi(funlw65) On Mar 18, 4:33 am, AlbertF <[email protected]> wrote: > On Mar 18, 4:37 am, mattschinkel <[email protected]> wrote: > > > I think this can be a jallib topic, since our work will be affected. > > > > The ultimate goal: use the AST to implement a JALV2 input to C output > > > translator or 'compiler' which could be targeted to other chips, like > > > the 34F, 30F, ARM9. > > > > William > > Why converting to C? I would rather spend the effort on creating a > front-end > for GCC, so JAL can support PIC32, ARM, dsPIC targets. Once you have > the AST > it should be fairly easy to generate the intermediate GCC format > (GENERIC or GIMPLE) > > Albert -- 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.
