如何编写bootloader

谷歌是你的朋友，但你不是谷歌的朋友？HTTP://www. McCHIP.COM/FUMMS/M95188ASPXand当然还有很多其他信息在论坛上。



      以下为原文

    google is your friend, but you are not a friend of google ?
http://www.microchip.com/forums/m951888.aspx
and of course lots of other information in the forum.

这是为我阅读数据表，搜索或谷歌为我等：



      以下为原文

    This is along the line of read the datasheet for me, search or google it for me, etc. :(

如果你在谷歌搜索“Microchip应用笔记Bootloader”，有很多相关的文献，包括这个Bootloader生成器用户指南。



      以下为原文

   
If you search in Google "microchip application notes bootloader" there are plenty relevant literature, including this Bootloader Generator User's Guide. 

我总是问“为什么你认为你需要一个引导加载程序”（更不用说为什么你认为你可以写一个引导加载程序）！我的经验，Bootloader是非常有限的用途，除了当你有一个最终产品需要更新（可能的）未经培训的人。他们当然不是初学者（甚至是比我有更多经验的人）。你知道限制吗？使用Bootloader会带来什么？苏珊



      以下为原文

    I always ask 'why do you think you need a bootloader' (let alone 'why do you think you can write a bootloader'!)?
I my experience, a bootloader is of very limited use except when you have a final product that needs to be updated in the field by (possibly) untrained people.
They are certainly not for beginners (and even people with a bit more experience than that in my opinion).
Are you aware of the limitations that using a bootloader will entail?
Susan

引导加载程序是常见的请求特征。它可以用来帮助生产或现场更新。虽然基本概念是容易的，细节可以使它成为一个先进的项目。微芯片EZ Bootloader和MCC可以使PIC18更容易。



      以下为原文

    A bootloader is a common requested feature. It can be used to aid production or field updates. While the basic concept is easy the details can make it an advanced project.
The microchip ez bootloader and MCC May make it easier for a PIC18.

不，我对此一无所知。你能指出这些限制吗？对不起，我很晚才赶上论坛上的帖子。



      以下为原文

   
 
No. I have no idea about that. Can you point out some of those limitations?
Sorry for my very late catching up with my thread on the forum.
 

我以前从未使用过MCC。有没有教程或帮助提供“如何使用MCC来生成PIC18F46K22的引导加载程序”？对不起，我很晚才赶上论坛上的帖子。



      以下为原文

   

I have never used MCC before. Is there any tutorial or help available for 'How to use MCC to generate Bootloader for PIC18F46K22'?
Sorry for my very late catching up with my thread on the forum.
 

读第4页怎么样？



      以下为原文

    How about reading post #4?

我认为ARDUNO世界已经有了一个Bootloader的存在，对许多新用户的期望，因为大多数ARDUINO MCU板都带有一个预编程的引导加载程序和一个USB接口。



      以下为原文

    I think the arduino world has made the presence of a bootloader an expectation for many newer users, since most arduino mcu boards come with a preprogrammed bootloader and a u*** interface.

不仅仅是阿杜伊诺。每个人都需要引导程序。没有它们，更新是困难的。



      以下为原文

   
It is not just Arduino. Every one wants Bootloaders.  Updates are difficult without them.

转到MCC Page，查看它和EZ引导加载页。然后你就可以问问题了。



      以下为原文

    Go to the MCC Page, Look at it and the EZ Bootloader Page.  
Then you will be able to ask questions.
 

建议页面在这里：HTTPS://www. MyCHIP.COM/PROSP/8BIT-Bootloader和在页面底部链接的Bootloader用户指南。



      以下为原文

    Suggest the page here: https://www.microchip.com/promo/8-bit-bootloader
And the bootloader user's guide linked at the bottom of that page.

那是当前的那个吗？没有EZ Bootloader / MCC Bootloader？



      以下为原文

   
So that is the current one?
No EZ Bootloader / MCC Bootloader?

这是指向8位MCC Bootloader的链接。EZ Bootloader只支持16位族。



      以下为原文

    That's the link to the 8 bit MCC bootloader. 
EZ Bootloader only supports the 16 bit family.  
 
 

谢谢你提供的信息。



      以下为原文

   
Thank you for the Info.

至于Bootloader的局限性，有些是：你不能调试你的应用程序（除非Bootloader有这个能力，他们可能不应该）-它们占用空间：微控制器通常有足够的内存来执行所需的任务，并且添加引导加载程序使Flash重启。如果你想在Bootloader和主应用程序之间共享代码，那么大腿会变得很毛茸茸的，你可以在Flash中留下一个不可用的程序：我知道这一直是个问题，但通常你需要两倍的内存大小，这样你就可以一直确保ACCE。SS到一个工作版本，也许并不总是重要的，但真正的好主意，除非你想要一个交叉客户-引导装载程序代码必须绝对摇滚：你必须始终能够切换到引导装载程序（内部通过代码和外部通过一个按钮等），并使它工作；这可以是比你想象的要难！BooLoad有自己的位置，但是（我的观点）只针对已经在“标准”开发环境中进行了彻底测试和调试的软件的现场/客户升级。添加Bootloader应该是开发过程中的最后一步，而不是第一个步骤（尽管它需要在设计工作开始时被认为是正确的）。



      以下为原文

    As for the limitations of a bootloader, some are:
- you can't debug your application (unless the bootloader has this capability and they probably shouldn't)
- they take up room: microcontrollers typically have just enough memory to perform the task required and adding a bootloader makes the FLASH requirements that much bigger; and if you try to share code between the bootloader and the main app then thighs can get really hairy
- you can be left with an unusable program in FLASH: I know this is always a problem but typically you need twice the memory size of the app so you can always ensure access to a working version; perhaps not always important but a really good idea unless you want a cross customer
- the bootloader code has to be absolutely rock solid: you must always be able to switch to the bootloader (internally via code and externally via a button etc) and have it work; this can be harder than you might think!
Bootloaders have their place but (in my opinion) only for field/customer upgrades of software that has been thoroughly tested and debugged in a 'standard' development environment first. Adding a bootloader should be the last step in the development process, not one of the first (although it does need to be considered right at the start of the design effort).
Susan
 

…没有人想要这个！；）



      以下为原文

   
... and no-one wants that! ;)
 

谢谢。。这非常有帮助和帮助。



      以下为原文

   


Thanks a lot.. thats very informative and helpful.

嗨，我倾向于同意苏珊的观点。你可能想考虑我做了什么，我设计了一个小单元，它执行PACTIT3的“运行”功能。它读取十六进制文件的缩略图，并将其编程到主机设备。简单，不受引导加载程序的限制。



      以下为原文

    Hi,
I tend to agree with Susans view.
You may want to consider what I did, I designed a small unit that performs the 'On the Go' function of PicKit3. It reads a thumbdrive for a hex file and programs it into a host device.
Simple, without the limitations of a Bootloader.