> Some of your information sort of sounds good, I like the idea > of having a bootloader that doesn't include Flash programming > code for the reasons you mentioned. Yet I use the IAP Flash > programming calls from my application anyway, so leaving it > out of the bootloader is of no benefit to me. I must admit to being confused by this one. I would have thought for serial upgrading to work, Philips has to include flash routines somewhere (bootloader?) on the chip. For certain any field upgrades we do are via serial port, not via Jtag. I might be wrong but the loading to ram of dedicated Flash routines only works for Jtag upgrades ? Also, one of the reasons Robert gave for not wishing people to write their own bootloaders was to handle flash specifics in the bootloader. If the bootloader doesn't have the flash routines, then this benefit is probably lost. I guess the upgrade program could still "hide" these specifics and be upgraded every time the flash technology changes, but having the algorithms with the chip is a much neater way to handle this. Maybe you could have pseudo code specifics in the bootloader that a RAM program interprets, but this is starting to get messy. Much prefer a chip that can upgrade itself ! Cheers, Bruce PS: Trying to keep this on a technical level only !
Message
RE: [lpc2000] Re: trashed 2148 bootloader
2006-02-23 by Bruce Paterson
Attachments
- No local attachments were found for this message.