<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Steve,<div class=""><br class=""></div><div class="">Should be the same. An unplug is an unplug, and we are definitely using genuine CP2102 chips.</div><div class=""><br class=""></div><div class="">Can you do a test:</div><div class=""><br class=""></div><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">ls -l /dev/tty.*</blockquote><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">(And have a look for the tty.SLAB* file)</blockquote><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">make monitor</blockquote><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">(So you have an async console connection open to the board)</blockquote><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">Unplug the USB</blockquote><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">Watch the make monitor python error messages</blockquote><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">ls -l /dev/tty.*</blockquote><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">(And see if the tty.SLAB* file is still there - if it is, you have the problem)</blockquote><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">Plug back in the USB</blockquote><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">ls -l /dev/tty.*</blockquote><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">make monitor</blockquote><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">(And see if you can connect again)</blockquote><div class=""><br class=""></div><div class="">Maybe there is a difference between external HUBs and on-board USB ports?</div><div class=""><br class=""></div><div class="">What version of cp2102 driver are you running?</div><div class=""><br class=""></div><div class="">Regards, Mark</div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On 26 Sep 2017, at 7:01 PM, Stephen Casner <<a href="mailto:casner@acm.org" class="">casner@acm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Mark, I have not had any problem with the USB hanging in my<br class="">development work with the DEVKIT-C plugged directly into the MacBook<br class="">Pro. I have needed to unplug numerous times when something goes wrong<br class="">and "make flash" fails to sync. It the situation different with the<br class="">real OVMS board?<br class=""><br class=""> -- Steve<br class=""><br class="">On Tue, 26 Sep 2017, Mark Webb-Johnson wrote:<br class=""><br class=""><blockquote type="cite" class="">Seems that Silicon Labs have released a v5.0.1 version of the driver that works for me. It still suffers from the “don’t unplug the USB device while in terminal”, but at least it doesn’t crash any more. I’m trying it now.<br class=""><br class="">Regards, Mark<br class=""><br class=""><blockquote type="cite" class="">On 26 Sep 2017, at 5:18 PM, Edward Cheeseman <<a href="mailto:cheesemanedward@gmail.com" class="">cheesemanedward@gmail.com</a>> wrote:<br class=""><br class="">Small update. A reboot was all that was required to get the CP2102 driver going, and the EEPROM python script sees it. Getting the script to go required specifying the specific python2.7 instance (of the three and counting I have managed to install over the years).<br class=""><br class=""><blockquote type="cite" class="">On 26/09/2017, at 8:40 PM, Edward Cheeseman <<a href="mailto:cheesemanedward@gmail.com" class="">cheesemanedward@gmail.com</a> <<a href="mailto:cheesemanedward@gmail.com" class="">mailto:cheesemanedward@gmail.com</a>>> wrote:<br class=""><br class="">CP2102 is US$1.33 one off from Digikey.<br class="">Must be cheaper still the closer you get to China.<br class=""><br class="">It just so happens that a USB-CAN converter I bought off aliexpress a while back has a CP2102 and STM32. I wasn’t so interested in their software, just the USB connected micro with CAN attached.<br class="">I paid NZ$24 for it shipped. Store was "Electronic products concentrated shop"<br class=""><br class="">In the last couple of days I tried to get it going, using the latest OSX driver. I didn’t get a crash, but I didn’t get a tty port either (so, not going yet)<br class="">I might try the old driver and see if that goes.<br class=""><br class="">If it is of interest, I found an old project to burn the CP2102 EEPROM from *nix here: <a href="http://cp210x-program.sourceforge.net/" class="">http://cp210x-program.sourceforge.net/</a> <<a href="http://cp210x-program.sourceforge.net/" class="">http://cp210x-program.sourceforge.net/</a>><br class=""><br class=""><Image-1.jpg><br class=""><br class=""><br class=""><blockquote type="cite" class="">On 26/09/2017, at 6:30 PM, HONDA S-2000 <<a href="mailto:s2000@audiobanshee.com" class="">s2000@audiobanshee.com</a> <<a href="mailto:s2000@audiobanshee.com" class="">mailto:s2000@audiobanshee.com</a>>> wrote:<br class=""><br class="">I'm very surprised that a driver must be installed. In my experience, most hardware implements the USB Communications Device Class standard, and therefore does not need a driver with OSX. Does anyone know why Silicon Labs didn't just implement the standard CDC protocols?<br class=""><br class="">I assumed that the ESP32 processor would have a USB peripheral that would host the protocol, and therefore the OVMS v3 firmware would be in control. I guess I didn't look closely enough.<br class=""><br class="">What does the CP2102 cost in relation to something like a PIC with USB? Sorry for the question.<br class=""><br class="">Brian<br class=""><br class=""><br class="">On Sep 24, 2017, at 11:42 PM, Mark Webb-Johnson <<a href="mailto:mark@webb-johnson.net" class="">mark@webb-johnson.net</a> <<a href="mailto:mark@webb-johnson.net" class="">mailto:mark@webb-johnson.net</a>>> wrote:<br class=""><blockquote type="cite" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• The Silicon Labs driver for OSX seems pretty flaky. Linux seems much better, and I haven’t tried Windows. On OSX, I had horrendous problems with the v5 drivers crashing my whole machine (Sierra 10.12). In the installation package, there is a “Legacy MacVCP Driver” directory containing the older 4.11.2 version - using that older version at least works without crashes, but has one known issue. If you ‘make monitor’ and are in the console to the board, then unplug the board, you get left with a /dev.tty.SLAB* device hanging around that messes up that one USB port and future ‘make monitor’ connections. Workaround is to power off the USB hub, and then everything cleans out nicely. If you are directly connected to your MAC’s USB port, then you seem to need to reboot the whole machine to fix the issue. Getting used to being careful to disconnect from the terminal before unplugging (or simply not unplugging - which was happening a lot when I was working o!<br class=""></blockquote></blockquote></blockquote></blockquote></blockquote> n power optimisation, sleep modes, and external 12V power).<br class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><br class=""></blockquote>_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a> <<a href="mailto:OvmsDev@lists.teslaclub.hk" class="">mailto:OvmsDev@lists.teslaclub.hk</a>><br class=""><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a> <<a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>><br class=""></blockquote><br class="">Edward Cheeseman<br class="">Electrical Engineer<br class=""><a href="mailto:cheesemanedward@gmail.com" class="">cheesemanedward@gmail.com</a> <<a href="mailto:cheesemanedward@gmail.com" class="">mailto:cheesemanedward@gmail.com</a>><br class=""><br class=""></blockquote><br class="">Edward Cheeseman<br class="">Electrical Engineer<br class=""><a href="mailto:cheesemanedward@gmail.com" class="">cheesemanedward@gmail.com</a> <<a href="mailto:cheesemanedward@gmail.com" class="">mailto:cheesemanedward@gmail.com</a>><br class="">_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br class=""></blockquote><br class=""></blockquote>_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br class=""></div></div></blockquote></div><br class=""></body></html>