Byron A Jeff wrote:
> On Sat, Jun 26, 2004 at 11:08:33PM +0200, Kyrre Aalerud wrote:
>
>>Actually, my loader isn't tying up the usart at all.  It only uses it during
>>load.  Then the system itself can use it after boot to retrieve my logged
>>data etc...  No response from PC within a few ms means go and boot...
>
>
> I understand where you are coming from. In your case the load application and
> the application application share the same physical RS232 interface. But as
> I've pointed out elsewhere, it's no fun when the two conflict because the
> bootloader needs to be connected to the PC, while the application needs to
> be connected to something else.
>
> Kyrre, it's a design choice. It's the right choice in your particular
> application. I'm not knocking it. However I tend to view bootloading from
> a general development perspective. See my list of 9 items for the ideal
> bootloader in my other post for details.

Well said. Most of my apps WILL be general apps (no committed RS232),
Bryan, so I will use the modified PLoader; so I agree on that score.

But I'd like to use Kyrre's for this first app, though, because of the
program update capability it lends. That's all.

[[aside: This F88 Bootloader conversation has been the best we've had
here in months!]]

--Bob
--

Replier: Most attachments rejected
       --------------
         Bob Axtell
PIC Hardware & Firmware Dev
   http://beam.to/baxtell
       1-520-219-2363

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics