On Mon, Sep 22, 2014 at 12:11 PM, AF <[email protected]> wrote:
> Ytai, > > Thank you for your answer. > > Always "A" position from now on [checked]. > No need for external supply [checked]. > > When you say "should not do any permanent damage (except that the IOIO > will not work in a device role)" do you mean it will not never work in > device role again after "making the mistake" of flashing in "H" mode? Or do > you mean that it simply will not work in device role when in "H" mode and > that if we flash it in this mode it will not do any damage? I guess you > mean this last one. > Yes. There should be no permanent damage. > > And about the USB cable just to make clear: one should use a simple "USB > type A to micro-USB type A or B" cable right? No need for OTG on one of the > ends of the cable right? > Yes, A on the PC side to micro-B on the IOIO side (NOT A to micro-A, because that would be equivalent to forcing the host mode switch to the "H" position). > > About IOIO not enumerating correctly in non-bootloader mode I think you > are totally right. Sometimes it is not recognized as COM Port but as an > Unknown USB Device. Also, sometimes I have to keep pluging it in and out > and "Find new hardware on Windows" and then "Update driver" using ioio.inf. > After doing that it is recognized as COM Port but ioiodude still can't show > anything in this mode (non-bootloader). When I plug it out and then in > again Windows may recognize it or not and I have to do this process again. > Another thing to look at is that if you have a USB hub in the middle, maybe bypassing it might help. > Ytai, I am going to try on a different computer very soon and post > updates. Once again, thank you for your answer. > Great. Thanks! > > > Segunda-feira, 22 de Setembro de 2014 18:21:18 UTC+1, Ytai escreveu: >> >> A few comments regarding the latest posts: >> >> 1. I see no evidence that we have any problems here related to >> programming not succeeding. I believe the comments made earlier about >> having a stable high-voltage supply are completely irrelevant in this >> context, since there's no external flashing involved and in either case >> there is no high-voltage programming on the PIC24. >> 2. The A/H position should *always* by on "A" except for cases where >> you're trying to compensate for having an incompatible USB cable that will >> not automatically put the IOIO in host mode. Regardless, having it in "H" >> mode should not do any permanent damage (except that the IOIO will not >> work >> in a device role). >> 3. Externally powering the IOIO when it is in device mode is a valid >> option. In this mode it will consume its operating current from the >> external source. For booting into bootloader mode, one has to consider >> that >> power-cycling will not take place by detaching the USB cable if the IOIO >> is >> externally powered. So in general it is easier to do all IOIODude-related >> stuff without applying external power. >> >> Having said all that, we still seem to have a real problem here that is >> likely not v5.x firmware related, that is, that the IOIO does not enumerate >> correctly in non-bootloader mode. >> Any chance you can attempt this on a different computer, just for >> sanity-checking? >> >> On Mon, Sep 22, 2014 at 5:10 AM, AF <[email protected]> wrote: >> >>> That's what I've done yesterday. I've bought another one. I hope now >>> that this one will be upgraded with no problems. I will do it in A position >>> with no external supply because the board that is OK has been upgraded that >>> way. >>> Thank you for your offer Chad but I live in Portugal. You are a nice guy. >>> I will attempt to do other procedures in order to fix these two >>> boards... I will post here updates if I succeed because this seems to be a >>> common issue. If Ytai has personal time for that it would be great if he >>> posted a section with a title like "What you must do before >>> upgrading/downgrading IOIO firmware" in the beggining of this page: >>> https://github.com/ytai/ioio/wiki/IOIO-OTG-Bootloader-and-IOIODude. In >>> a short text he could warn IOIO users what position of the H-A switch they >>> must use before connecting to the PC and if they should use external supply >>> or not. Because I think that many users find this confusing and then >>> mistakes occur. Btw, Ytai please correct the link in the sentence "The >>> first thing to do is to grab the latest version of IOIODude >>> <https://github.com/ytai/ioio/raw/master/release/apps/IOIODude-0100.zip>" >>> of the same page to version 1.2. I guess you missed it. >>> >>> Thank you all for your responses and feel free to keep trying to solve >>> this issue. I will do the same. >>> >>> >>> Segunda-feira, 22 de Setembro de 2014 2:27:49 UTC+1, Chad Kennedy >>> escreveu: >>>> >>>> Well, short of sending both to someone who has done it before and has >>>> a known go physical setup. You may have only one option, buy another one or >>>> two... >>>> >>>> I would be willing to try the updates for you if you pay for shipping >>>> both ways. This assumes shipping is reasonable and you are in the U.S. >>>> >>>> Maybe time will pass and you'll have an "Ah ha" moment. Maybe buys some >>>> fresh 9V and try the flashing. A fresh 9V should be enough to at least >>>> flash. >>>> >>>> >>>> On 9/21/2014 4:58 PM, AF wrote: >>>> >>>> I see your point Chad. Actually now I am trying to upgrade/downgrade >>>> the firmware in A position + external supply (USB 5V 1A to IOIO JST >>>> connector, homemade adaption made by myself, works fine) but still no >>>> luck... I don't know what to do anymore... I think I have tried almost >>>> everything! >>>> >>>> Domingo, 21 de Setembro de 2014 22:49:44 UTC+1, Chad Kennedy escreveu: >>>>> >>>>> >>>>> My experience with PIC chips has taught me that "not enough power" >>>>> during the burn/flash/programming time will give significantly >>>>> inconsistent results. Your problem is sounding more like that since >>>>> you've basically done it on two IOIOs and not a procedural problem >>>>> like >>>>> I faced. At the time of updating the firmware there was insufficient >>>>> power applied or the IOIO was in H instead of A - these are my >>>>> theories. >>>>> I would encourage you to re-update and/or roll back to a prior >>>>> versionsV0330. fwiw I used a 9V battery and it did not last long >>>>> powering the IOIO OTG or for that matter any PIC chips from my >>>>> projects >>>>> I used prior during the flasing process. I dropped it quickly and >>>>> found >>>>> a usb power supply terminated pins on it and connected the IOIO. My >>>>> plug >>>>> runs 5V DC @ 2A. Try updating again verifying all power needs. I am >>>>> going way out on a limb for this IOIO OTG PIC model but I know my >>>>> other >>>>> PICs require 12+ Volt minimum to achieve a good flashing, the PC's USB >>>>> will provide some power, but is likely needing to be supplemented with >>>>> external. Again stating this from experience and not looking at the >>>>> IOIO's PIC's specifications/requirements. >>>>> >>>>> >>>>> On 9/21/2014 2:12 PM, AF wrote: >>>>> > black7, >>>>> > >>>>> > Both boards are showing inconsistent behaviour. I only managed once >>>>> to show the app firmware on ioiodude for one of the boards (don't know why >>>>> it worked that time, the procedure was the same for both boards). Now I >>>>> can't show it for both boards and one of them sometimes works with my >>>>> smartphone other times doesn't. The other one doesn't work at all. This >>>>> makes no sense I know... >>>>> > And about upgrading the firmware with the external power supply: >>>>> that's what I was trying to say on the first post, it is highly probable >>>>> that I've done that and also with H position on switch... I can't remember >>>>> but I think I've done it. >>>>> > At first the COM ports only appeared in H position. And when in A >>>>> position they appeared as unknown devices. Now after I did all those tries >>>>> and procedures I managed to make them recognized as COM ports in both H or >>>>> A positions. >>>>> > >>>>> >>>>> ____________________________________________________________ >>>>> The End of the "Made-In-China" Era >>>>> The impossible (but real) technology that could make you >>>>> impossibly rich. >>>>> http://thirdpartyoffers.netzero.net/TGL3241/541f47d59ba4247d >>>>> 57d79st03duc >>>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "ioio-users" group. >>>> To unsubscribe from this topic, visit https://groups.google.com/d/to >>>> pic/ioio-users/qY-fe0ikwLs/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> To post to this group, send email to [email protected]. >>>> Visit this group at http://groups.google.com/group/ioio-users. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> >>>> ____________________________________________________________ >>>> >>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "ioio-users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/ioio-users. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "ioio-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/ioio-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "ioio-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/d/optout.
