> It'll certainly take more memory then highly optimised ASM code (like Tiny > Bootloader).
Jalv2 allows ASM code with: assembler...end assembler, could this be a solution? The point to me is that we should not have to use another bootloader, we should use and support our own that works on a veriety of PIC's. As some say, there are disadvantages to bootloaders, can we overcome whaterver disadavantages they are? I'm sure there must be a way to reduce the chance of overwriting a bootloader. Why is there a jallib USB bootloader but not a serial bootloader? I'm not sure of the price of the Jaluino board, but if a programmer was not required for it, a lot more people would be interested. I know someone whom would like to try PIC's, he doesn't have much cash to get started so I was thinking about programming a bootloader onto a PIC for him. A PIC with a bootloader programmed would do the trick. Also people like me whom have an older programmer would be able to get a pre-programmed PIC with bootloader. Even new programmers are not able to program them all. I wish I could get a PIC like PIC18F97J60 with a bootloader, I see no programmers around that can program a PIC like this but if someone was able to put a bootloader on it for me I might buy it. I would not care how large the bootloader is on a huge PIC like this. This is the kind of PIC I would love to see on development boards. I tried to compile tiny bootloader with the current version of MPLAB and it didn't compile. I am assuming it needs MPLAB 6, but I can't find it anyways. A jalv2 bootloader would have it's advantages. Matt. -- 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.
