Hi Matt, mattschinkel wrote: > In my opinion, the serial port will always be supported because there > will always be USB to serial adapters.
Reversed cause/consequence: these adapters are there because of investements in devices using RS232. When these devices disappear in favour of USB then no need anymore. > My issue with USB is the driver > required although I'm sure microchip will always come out with drivers > for new operating systems. Microchip knows only about Windoze.... > Serial port hardware does not need drivers. Wrong! All OS-s need drivers for serial ports (DOS came with none, so DOS communications programs needed to include some sort of driver). > Maybe a bootloader for jalv2 would be written in ASM, but you could > have one file with jal constants to choose your PIC. In the long term, > a lot of PIC's could be supported. Maybe there is not enouf interest > right now. > > If a bootloader was written in jalv2 instead of ASM, it would support > all PIC's (I think), because you would just change the device include. Wrong! The device files contain info about memory size, but nothing about how to write code memory. And there are many differences between the PICs (one of the reasons we don't have a library to read/wrte code memory)! You might have a look at the firmware for the Wisp648 programmer (written in Jal!) to understand that it is not as easy as you may think. > even more, you could have some ASM code + some jal code. If you choose > a PIC that is not supported in ASM, it would automatically use JAL > code which takes more space. Wishfull thinking. Regards, Rob. -- Rob Hamerling, Vianen, NL (http://www.robh.nl/) -- 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.
