Hi Matt, mattschinkel wrote: >> 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?
Possibly yes, but I thought you wanted a bootloader completely written in Jal. > 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. You cannot have a single hex file for all, there are many differences. Think of: type of PIC (the way different PICs write their own code memory), interface (serial/USB/other), type of oscillator, clock speed, speed of the link between PC and PIC-with-bootloader, configuration bit settings needed by the particular application program, and probably more. So in practice you need a dedicated bootloader for almost every project. You didn't react on my argument for a PC program. I admit when I heard about bootloaders for the first time I had the impression these were self-supporting, but in fact these things require a dedicated support program to work. So what you want sounds as re-inventing the wheel. Tiny Bootloader would fit here nicely. > 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. That may be true. In fact that is a situation comparable to where I use a bootloader in one of my projects. I want to be able to let a PIC program be replaced by anyone, without the need for a PIC programmer, only a cable and a piece of PC software (the bootloader support program). > 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. Chicken and egg problem: no programmer which can load the bootloader then no need for a bootloader. > 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. Agreed. > 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. GPASM of the GPutils package works fine for me. > A jalv2 bootloader would have it's advantages. Depends what how you define a 'JalV2 bootloader' exactly. When you get to know more about bootloaders your opinion may change. 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.
