带有MSD BootLoader的PIC32MX USB主机

什么版本不是2.03B？什么硬件？你的？EVE板？你试过了吗？它工作在V1.11（排序）它应该在V2.xx工作。如果你是董事会。你有没有比较MHC设置到你的？代码BSP。比较程序是你的朋友。



      以下为原文

    What not Version 2.03b?
What Hardware? Yours? and Eval Board?
Have you tried it on and Eval Board?
It works in V1.11 (sort of)  It should work in V2.XX.
if it is you Board.
Did you compare the MHC settings to yours?
the Code the BSP.
The Program Beyond compare is you friend.
 

谢谢你的回复。这是我们的定制硬件。没有BSP。是的，我使用示例Bootloader文件作为起始位置，并将MHC设置复制到MIX中。这个项目从2.02B开始，我觉得没有必要更新。更改版本没有得到很好的记录。我刚刚下载和安装了1.11个你推荐的工作。Bootloader .c文件与我使用的版本2.02b相同。我仍然不知道它是如何工作的。这就是我的问题开始的地方。这在支持Bootloader的所有版本的Bootloader C中的第486行开始：CaseBootloadReWaITyFuxDeice附注：/*等待设备附加。当接收到附加事件*时，状态机将移动到下一个状态。* /打破；没有办法超越这个状态。评论是准确的，但没有代码来支持它。救命！



      以下为原文

    Thanks for the reply.  This is our custom hardware.  There's no BSP.  Yes, I used the example bootloader files as a starting place and duplicated the MHC settings into mine.  The project started with 2.02B and I haven't felt a need to update.  Changing versions is not well documented..  I just downloaded and installed 1.11 as you recommended as working.  The bootloader.c file is identical (WinMerge) with the one in Version 2.02B that I have been using.  I still don't see how it could work..  Here's where my problem starts.  This begins at line 486 in BootLoader.c in all versions that support BootLoaders:
        case BOOTLOADER_WAIT_FOR_DEVICE_ATTACH:
            /* Wait for device attach. The state machine will move
             * to the next state when the attach event
             * is received.  */
            break;
There's no way to advance beyond this state.  The comments are accurate, but no code to support it.  Help!

嗨，正如上面的一段评论清楚地陈述了它等待设备附加事件，我想你需要看一下是否正在检测和处理UBSHEVER事件。检查这个函数“BooDouthReuleUbBuxMsDevEnthDand”是否在“DATASERAMUSSBHEST.C”中被定义。因为这是一个事件，它引导引导程序状态并枚举附加的UBSHOST设备。您试过运行由和声提供的基本演示应用程序吗？如果不尝试运行，看看它是否对您的安装工作。



      以下为原文

    Hi,

As the above section comments clearly states it waits for the device attach event, i think you need to give a look on whether the USB_HOST events are being detected and handled.
 
Check if this function "Bootloader_USBHostMSDEventHandler"defined in "datastream_u***_host.c" is getting called. Because this is the event which moves the bootloader state forward and enumerates the USB_HOST device attached.
 
Have you tried running the basic demo application provided by harmony? if not try to run and see if it works on your setup.
 

非常感谢你的提示。它开辟了最终通向我们解决方案的道路。我没想到状态机会有外部进程的状态改变。我们的根本问题是USPPLL配置。一旦我们搞定了，事情就开始了。和谐主机2.02b中的USB主机引导加载程序好像广告一样工作。谢谢你的回复。



      以下为原文

    Thank you very much Optimus_jack for the hint.  It opened up the path that ultimately led to our solution.  I wasn't expecting the state machine to have state changes made by outside processes.  Our root problem turned out to be the USBPLL configuration.  Once we got that fixed, things started working.  The USB Host Bootloader in Harmony 2.02B seems to work as advertised.  Thanks for the replies.

不客气。



      以下为原文

    You are Welcome.