USB Bootloader读取失败

大家好！我正在使用一个USB初学者工具包2，并结合“基本”（Bootloader）和“HythBasic”（USB）演示文稿提供的不协调V2.05.01编译成XC32 1.43。我匹配了项目之间的设备配置，并让它加载。到目前为止非常好。我可以用VB从USB应用程序进行通信，如果我在开机之前按下SW1，LED开始闪烁，引导加载程序就绪。所以这两个特性似乎都在起作用。我正在解决的问题是改变十六进制。我已经尝试了AN1388 PIC32 UBL Bootloader，也尝试了UNIFIEDHOST-0.1.8。在加载Bootloader时，PC应用程序都无法通信。但是他们都看到了设备，当组合。PIC32 UBL要求重置设备加载Bootloader，但这样做会删除设备并失去连接。UNIFIEDHOST-0.1.8试图读取Bootloader版本并失败。要传递新的HEX的过程是什么？Bootloader是否有USB代码？这样，可以建立USB连接吗？或者应该将新的十六进制转移到特定的内存位置，引导引导器查看重置？我想我对使用的策略不太清楚，演示应用程序不起作用，我找不到他们的文档。有人走下这条路，关心分享他们的经验吗？非常感谢！彼得



      以下为原文

    Hi All!

I'm working with a u*** starter kit 2 and combining the 'basic' (bootloader) with the 'hid_basic' (u***) demos offered in hARMony v2.05.01 compiled with xc32 1.43.

As instructed, I put the bootloader as a loadable to hid_basic. I matched up the Device Configurations between the projects, and got it to load. So far so great. I can communicate by u*** from a VB app, and if I hold down SW1 before power on, the led starts blinking for bootloader ready. So both features seem to be working.

The issue I'm having is changing the .hex. I've tried the AN1388 PIC32UBL Bootloader, and also the UnifiedHost-0.1.8. Neither PC apps can communicate when only the bootloader is loaded. But they both see the device when the combined .hex is loaded. The PIC32UBL asks to reset the device to load the bootloader but doing so removes the device and loses the connection. And UnifiedHost-0.1.8 tries to read the bootloader version and fails.

What is the process to transfer the new .hex? Should the bootloader have the u*** code in it? That way, a u*** connection can be established?

Or should the new .hex be transferred to a specific memory location where the bootloader looks upon a reset?

I guess I'm not too clear on the strategy to use, and the demo apps are not working and I can't find the documentation on them.

Anyone been down this path and care to share their experience?

Much appreciate in advance!
Peter