 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 : Explore64 - Device not recognised
| Author | Message | ||||
| circuit Senior Member  Joined: 10/01/2016 Location: United KingdomPosts: 277 |
I am somewhat baffled by a problem that has arisen with my Micromite+ Explore64 board. It has been working perfectly with an ILI9341 display, all properly mounted on a perf board. I have been loading images, saving files, using touch screen etc. without problems for months. A couple of days ago I re-flashed the firmware to the latest plus beta and the device chatted away happily to me on MMEdit as usual. Then I reset the display driver with the usual OPTION directive and restarted the thing. Immediately I received a message from Windows 10 ; USB device not recognised. Puzzled, I reflashed the firmware and the thing chatted away again without problems...until I once again tried the display driver directive. Again, USB device not recognised. Third time, the same dropout when the display driver directive is given. I tried loading the release version of Micromite+ but the same issue happens. I am using the same OPTION directive as I have always used (all pins correct and checked) and, indeed, the screen blanks dark when the option loads suggesting that the Micromite is happy, but the USB comms drop out every time. Any suggestions to what I am doing wrongly? |
||||
| Phil23 Guru  Joined: 27/03/2016 Location: AustraliaPosts: 1667 |
Seen a similar situation on my E100's when the USB supplied power is marginal. Tore my hair for a bit as I swapped 2 screens between 2 E100's before I realised that the power was an issue. Phil. |
||||
| circuit Senior Member Joined: 10/01/2016 Location: United KingdomPosts: 277 |
The problem is that I am using the same board, same screen and same computer that has all worked fine for months so I cannot see that becoming an issue de novo. But thank you for the suggestion. Addendum; My screen is socketed to the board; removing the screen and rebooting the Explore64 still results in a USB Device not recognised error message. So until I reload the firmware I cannot access the Explore64. As soon as the firmware is reflashed everything is back to normal with MMEdit comms. |
||||
TassyJim Guru Joined: 07/08/2011 Location: AustraliaPosts: 6283 |
Let me guess - Windows 7? If so, there is a known issue with the USB code on MMPlus when using Windows7. It works OK on W10. There were posts about it here not long ago. I will try and find them for you later but no time now. The best solution is to use an external USB-TTL converter. Jim VK7JH MMedit |
||||
| circuit Senior Member Joined: 10/01/2016 Location: United KingdomPosts: 277 |
Alas, I think this is not the problem either. I am running Windows 10 Home edition. But it does make me wonder if a recent Windows maintenance update might not be a problem. Though if no one else is experiencing the same then I guess not. |
||||
Grogster Admin Group  Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
If you are using a USB hub to connect to the E64, then either bypass the hub and plug DIRECTLY into the computer USB port, or pull out the USB plug to the hub, wait a few seconds, and plug the hub back in again. Then try to reconnect. I'm on W10, and I see that problem quite often when connecting via a USB hub. It works fine for a while, then at plug-insertion X, W10 just starts saying 'Unknown device', or 'This device has malfunctioned and Windows does not recognise it.' Reset the USB hub(or bypass it completely), and it's away again just fine. I don't know why that should be, and it usually works fine via the hub for about 8-10 different connections, THEN it starts to complain, and no amount of re-plugging into the hub will get you past that. Unplug and re-plug the hub itself, and that fixes it for me - must reinitialize the stack for the hub or something. This happens with me on ALL MM series units, including the E28 with it's separate 1455 USB interface chip. Smoke makes things work. When the smoke gets out, it stops! |
||||
| lizby Guru Joined: 17/05/2016 Location: United StatesPosts: 3378 |
I recently had all sorts of problems connecting to an E-64 with the on-board USB connector. It would work and then it wouldn't--with MMEdit, Teraterm, putty. This was with Win7. Someone suggested using a CH340 usb/serial module to connect to the console pins and to provide power (3.3 volts only!). All gold since then. PicoMite, Armmite F4, SensorKits, MMBasic Hardware, Games, etc. on fruitoftheshed |
||||
| TassyJim Guru Joined: 07/08/2011 Location: AustraliaPosts: 6283 |
My E64 has been permanently modified to use a 1455 USB so unable to test the latest W10 update with the original. But the error looks very much like the W7 one. Try going back to V5.4.8 or earlier and see what happens. Jim VK7JH MMedit |
||||
| lizby Guru Joined: 17/05/2016 Location: United StatesPosts: 3378 |
I misremembered about the 3.3 volts only. That was for an MM-44. For the E-64 I ran 5V from the CH340 to the 5V input on the E-64, and then E-64 output 3.3V to the breadboard power bus. PicoMite, Armmite F4, SensorKits, MMBasic Hardware, Games, etc. on fruitoftheshed |
||||
| circuit Senior Member Joined: 10/01/2016 Location: United KingdomPosts: 277 |
And... yes, that works! Firstly I tried the Explore64 with the latest firmware on another machine and got the same "USB Device not recognised" response yet again. (Another Win10 machine). Then I reflashed the Explore64 with version 5.2 as suggested and comms are back up and running. I then issued the directive OPTION for the ILI9341 display panel and rebooted the Explore64. Now the thing is working just fine on any of my computers. This suggests that is it is not a power issue (the total consumption is well below that stated for my USB ports). It appears to be an issue with the latest firmware not providing the correct, or perhaps a corrupted, device identifier to the USB system on the Explore64 after the ILI9341 device driver is loaded. I have repeated my various steps and I seem to get an absolutely consistent picture. There is no change in any of my hardware, just the various updates to Win 10 and the latest versions of Micromite Basic. As the swap to an earlier version of Micromite Basic fixed the issue completely I assume that I am encountering a bug in the latest firmware. |
||||
| TassyJim Guru Joined: 07/08/2011 Location: AustraliaPosts: 6283 |
This is the thread that describes a very similar problem. https://www.thebackshed.com/forum/forum_posts.asp?TID=10722&PN=6 It was with W7 but the latest W10 update might have done something. It was back in August when I finally converted my E64 to the microbridge and totally disabled the USB which stops me from doing any tests. Something for Geoff to ponder on when he finishes his holidays. Jim VK7JH MMedit |
||||
| circuit Senior Member Joined: 10/01/2016 Location: United KingdomPosts: 277 |
Yes, there seems to a scattering of the same problem. In the link that you sent, #Malibu reports "My problems ONLY happened when I configured the LCD Panel with the OPTION command." This would seem to confirm an issue with the USB comms and the LCD panel driver. I think that it is "over to Geoff" as you suggest |
||||
| Malibu Senior Member Joined: 07/07/2018 Location: AustraliaPosts: 260 |
I understand your frustration!  My original MMBasic version that came pre-programmed from SC was 5.04.08 (from memory) and your exact problem occurred when I upgraded to 5.04.09 onwards (Using W7) In the end, the problem 'appeared' to have been fixed once I started using a USB3.0 port, although, I'm still not convinced that was the solution. Here's my original thread if it helps - https://www.thebackshed.com/forum/forum_posts.asp?TID=10686&PN=3 It's been a while since I fired up the MM (other things to concentrate on) but I presume my setup is still working  John |
||||
| Pluto Guru Joined: 09/06/2017 Location: FinlandPosts: 375 |
I have the same problem with 64 pin uMite. (Firmware: Micromite_Plus_V5.04.09.hex). When I first started up, I used a CP2102 USB to TTL adapter to connect to the computer (Windows 10). Everything worked perfectly. I decided then to try powering from USB. Windows does not recognize uMite. However, if the uMite is externally powered before the USB is connected, then Windows correctly identifies the uMite. When connecting only USB there is a delay of approx. 500 us between (sharp) rise of +5V and (slow) rise of 3.3V supply to a level of 3.0V. Can it be that the PIC is not happy with first having it's USB block powered before the rest of the chip is getting sufficient power to start? In my connection the 3.3V regulator is MCP1700-3302E/TO with 10uF on both input and output. Smaller capacitors would decrese the delay, but what would be an acceptable delay between +5V and 3.3V rise? If my "theory" is correct, are there any firmware possibilities for keeping PIC's USB block waiting a bit before it connects to Windows? |
||||
| Pluto Guru Joined: 09/06/2017 Location: FinlandPosts: 375 |
In addition to my earlier post.  Blue trace: 3.3V powerline for PIC Red trace: USB powerline time scale in ms. Vertical cursors: 1) Connecting USB, 2) PIC's power at 2.3V (min operation voltage for PIC). 488.6 us before we have 2.3V. /Fred |
||||
plover Guru Joined: 18/04/2013 Location: AustraliaPosts: 306 |
Pluto I am interested in your recording 'device' can you give some details about your recorder? |
||||
| Pluto Guru Joined: 09/06/2017 Location: FinlandPosts: 375 |
It is a PICOSCOPE 3224. 2 channel 10MHz oscilloscope. USB connected. Useful also for decoding I2C and SPI. |
||||
Zonker Guru Joined: 18/08/2012 Location: United StatesPosts: 767 |
Try Micromite_V5.04.10_Beta_13 on Geoff's site now... For me and others, this new version fixed the problems...  |
||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
