I'm trying to build the UBW32 Firmware version 1.6.4. This is for an MX795 UBW32. I'm using MPLAB IDE v 8.92 with MAL v2013-02-15 (which as far as I can see has USB Stack 2.9i, which is what the release notes for Firmware v1.6.4 say it is built with).
I find if I use the hex files from the firmware zip files on the UBW32 home page (at http://www.schmalzhaus.com/UBW32/) then my 64-bit Windows 7 system identifies the resulting COM port as (for example) "Communications Port (COM16)".
I've tried v1.4, v1.6.2, v1.6.3, and v1.6.4 and they all show the same description for the COM port (though v1.6.4 responds to the V command by reporting it is 1.6.3).
However, when I built v1.6.4 from the sources, I could not get it to work at first. The UBW32 was appearing as (something like) "UBW Serial Port" - I didn't take careful note of the exact description.
Eventually, I updated the Windows driver using the files in UBW32_Inf in the 1.6.4 zip file, and now the firmware 1.6.4 I have built is working, but Windows Device Manager shows the device as "USB Serial (UBW-based) communications port (COM16)".
Is that the expected behaviour, or have I done something stupid?
USB PICs and the UBW
1 post • Page 1 of 1