 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : Firmware Upgrade
| Author | Message | ||||
| Malibu Senior Member  Joined: 07/07/2018 Location: AustraliaPosts: 260 |
Ok, I'm not having much luck lately!  I thought I'd try a firmware upgrade for my current MM+ 5.04.08 to 5.04.10(Beta 4) Unfortunately I get a USB/Comms error when configuring the screen (OPTION LCDPANEL ILI9341, LANDSCAPE, 44, 43, 42) As soon as I send that command and restart, I lose the USB Port configuration and need to reflash with the original 5.04.08 to get the port back again. I tried this last week with 5.04.09 (I think that was the version number) and had the same issue. This is the same screen config I have in 5.04.08 and it works great... As far as I know, I'm making the right moves, but maybe I've missed something? Here's a quick video of the entire process that I go through (The problem comes in at around 5:15 if you want to jump ahead) Keep your eye on the Devices window and you'll see the USB port on the bottom that's giving me problems. Upgrade Problem (Edit: Sorry, forgot to put a link) (I'm not worried with the 'display not configured' error. That's to be expected) Any clues on this latest problem I have? John John |
||||
TassyJim Guru  Joined: 07/08/2011 Location: AustraliaPosts: 6283 |
I don't have any display set up but this is what I get when trying your configuration Using Windows 10 This was using the USB connection, something I never do. To reset, I close my terminal program. unplug the USB power down the MM+ reapply power to the MM+ reinsert the USB restart my terminal program (MMEdit but it applies to most terminal programs) It is MUCH easier to use an external USB-TTL adapter so you can do all the resetting and power cycling without having USB problems. Jim VK7JH MMedit |
||||
| Malibu Senior Member Joined: 07/07/2018 Location: AustraliaPosts: 260 |
Thanks for having a try Jim Yeah, no arguments from me on that one  I don't have a TTL-USB adapter so I can only do it the way I have been. The end result is the same, but I just need to do a lot more steps in achieving the outcome. I seem to remember reading that Win10 doesn't need the SC port driver. I should have mentioned I'm running Win7 so it appears I need the SC driver. Here's a few more screen shots -  The Devices and Printers showing the normal (Ver 5.04.08) driver  The failed port notification after entering the screen OPTION LCDPANEL command in V5.04.10  Device properties on the USB port after OPTION LCDPANEL command It's really strange to me that when I go through the steps to install 5.04.10, the MM+ works (it runs code) but the windows driver faults out after configuring the screen, yet, when I go through the same steps to install 5.04.08 it happily accepts the same screen command with the same screen configuration that I've had since first install. I don't see how the screen config could be related to the USB driver on the PIC32 (presumably that's what is causing the windows driver to fault) but there appears to be some sort of correlation between the two.. No, I don't either at the moment... screen has been unplugged and the SD Card is removed. The only extra I have is the screen wires with a resistor from VCC to LED at the screen end. It's very baffling... John John |
||||
| TassyJim Guru Joined: 07/08/2011 Location: AustraliaPosts: 6283 |
Do you get the message "Restart the Micromite+" after you set the display option and before you restart or does the driver immediately fail? After you get the Windows driver error, have you gone through the disconnect, power down, re-power, reconnect process? I don't have any suitable W7 PCs to test with. USB-TTL adapters are cheap. Jim VK7JH MMedit |
||||
| Malibu Senior Member Joined: 07/07/2018 Location: AustraliaPosts: 260 |
Problem fixed. With a lot more swapping, changing, plugging, setting and hair pulling... I had a brief wonder about the USB extension cable I was using and maybe it could be giving me grief. Unplugged the MM and for convenience, plugged it in to another USB port on the front of the PC. Still didn't work, so I plugged into another front one and hey presto! There it is! (Port 15 this time...) So, unplugged it, plugged the extension cable into that same port and the MM into the extension cable - There it is again  The difference between the original port, the 2nd port and the one that works is that the 3rd port is USB 3.0 and the others are USB 2 Maybe Geoff could confirm if the later versions of MM basic need a USB 3 connection? (I don't recall seeing a spec on what generation of USB was needed) Anyway, all's well that ends with a full head of hair! John John |
||||
| Malibu Senior Member Joined: 07/07/2018 Location: AustraliaPosts: 260 |
Sorry Jim, you must have replied while I was typing my last post... As I said, it seems to be ok now, but in the case it might help someone else out - Got the message to restart, so I disconnected the USB to reset the MM. When it gets powered up again, there's a long windows delay (10 seconds?) before I get the Device Not Recognised Fault Yep, many times  I even uninstalled/scan for changes/reinstall the SC drivers. I know... don't have one on hand at the moment  Thanks for your help Jim John John |
||||
bigmik Guru Joined: 20/06/2011 Location: AustraliaPosts: 2950 |
Hi John, I think that is your answer... USB 2 is max 500mA whereas USB 3 can source 3A. I would say it is due to your cables being either too long and/or a bit too thin.. the fact that USB 3 is designed for supplying a greater power would be the difference.. Try a shorter cable and use high quality thicker cables (these can be hard to be certain as they could have thick insulation to look like high quality ones.) Regards, Mick Mick's uMite Stuff can be found >>> HERE (Kindly hosted by Dontronics) <<< |
||||
Azure Guru Joined: 09/11/2017 Location: AustraliaPosts: 446 |
Just to add to bigmik. Some regular PC USB ports will not deliver the required current as they age and are repeatedely overloaded. I don't thinkwas made clear in the posts but that is a feature of using the USB port in that it will require unplugging and reconnecting to be detected when a reset is required. I highly recommend getting or making a microbridge module, does both serial comms and firmware loading without dropping the USB driver connection in the process (you do need to disconnect the serial comms program, do the firmware upgrade and reconnect the serial comms program. That is one advantage of the SC MM Mk2 that has not yet been added to the SC MM Plus 64 LCD Backpack. It would be a great addition. I am sure other TBS members that provide boards have something available. |
||||
| Malibu Senior Member Joined: 07/07/2018 Location: AustraliaPosts: 260 |
Problem not fixed... There's still something strange happening in that yes, windows USB3 does pick up the MM and load the driver (it takes around 10 seconds to do so), but it will only do so around 1/4 of the time. I loaded 4.05.08 back into the MM and windows picks it up first time, every time. Looks like I'm stuck with that until I get organised with an adapter John John |
||||
Grogster Admin Group  Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
Are you using ports directly on the PC, or are you using USB3 ports on a USB3 hub? I often get those errors when plugging MM's into my USB3 hub. I always get the MM back, if I unplug the hub, and plug it back in again. Windoze seems to have a rather touchy USB handler these days, and it does not take much to upset it.  You are correct - Windoze 10 should have native support for the MM+ USB or the 1455 USB chip that just about every new MM these days uses by default. Windoze XP/7/8/8.1 all need the driver for the 1455, and the Silicon Chip driver if you are using an Explore-64 or Explore-100 1B or 1C. The E100 version 1D has provision for the 1455 USB chip, and the PIC32 USB interface was dropped on the E100 from that point. The E64 never received the 1455 chip upgrade, and I doubt it ever will. The E64 really has been succeeded by the MMX or ARM-mite series of chips, and boards for those already have the 1455 USB interface as standard. I'm not aware of Geoff doing anything around the USB stack in the MM+ between 5.04.08 and 5.04.09, but perhaps he did tweak something that is upsetting Bill on your PC? Smoke makes things work. When the smoke gets out, it stops! |
||||
| Malibu Senior Member Joined: 07/07/2018 Location: AustraliaPosts: 260 |
The USB3 is a powered PCI card internal to the PC... It's only new, so I don't know it's quirks (if any). All the USB2's are directly from the motherboard but I was fast running out of ports - hence the new USB card. It's a pretty old PC - maybe 8 or 10 years old; but it's served me well so far. I wouldn't have thought he would have any reason to twiddle with something that already works, so I would agree with you there. It took me a few moments to figure out who Bill was, but yeah it doesn't take much to upset the Window$ apple-cart. Oh, bring back DOS 3.1! John |
||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
