Ytai,

Just to add this: The board I've bought the other day has just arrived 
(from Sparkfun too). It had app firmware v3.3 and I just updated to v5.0 
with no problems. A mode + No external supply + normal USB-A to micro-B 
cable. IOIODude reads both bootloader and app firmware with no problems at 
all.
So it's confirmed, it has to be one of these options I guess (hope it makes 
sense):
1. The "H mode + external supply" flashing damages the IOIO board in the 
way that it will no longer work correctly in A mode for some reason
or
2. There is no damage but some unknown problem about non-bootloader mode 
with Windows and/or the IOIO board appears after doing option 1

De-tuned clock, could be, never thought about that. I'll see what I can do 
and I will post updates soon. Thank you once again Ytai.

Quarta-feira, 24 de Setembro de 2014 18:18:47 UTC+1, Ytai escreveu:
>
> The wiki page about IOIODude has a section about that. The idea is 
> resetting the IOIO's clock calibration values, in case it got de-tuned for 
> some reason. Once you do that, the next time you connect the IOIO to a PC 
> it will recalibrate itself from the host PC (automatically).
>
> On Wed, Sep 24, 2014 at 10:01 AM, AF <[email protected] <javascript:>> 
> wrote:
>
>> Ytai,
>>
>> Any comment you make here is always appreciated even if you can't help. 
>> So I thank you for that.
>> Configuration wipe? on the IOIO's? or the PC (ioio.inf, etc...)? Could 
>> you be more specific please? I don't know how to do that on the IOIO's or 
>> what you really mean...
>>
>> Quarta-feira, 24 de Setembro de 2014 16:40:57 UTC+1, Ytai escreveu:
>>>
>>> Heikki, you seem to have gotten your cables wrong. When connecting to a 
>>> PC you don't need any adapter cable, just a common A-micro-B cable. As soon 
>>> as you plug the adapter into the IOIO it will think it is a host, unless 
>>> the adapter is not a standard one, in which case the IOIO will not act as 
>>> host even when it should (hence the reason for having the host mode switch).
>>>
>>> I'm sorry I cannot be of more help with diagnosing the enumeration 
>>> failure. I just don't have a setup I can use to reproduce this issue. By 
>>> the way, has any of you attempted a configuration wipe at any point?
>>>
>>> On Tue, Sep 23, 2014 at 7:49 AM, AF <[email protected]> wrote:
>>>
>>>> heikki, I have upgraded my 3 boards (Sparkfun) from app firmware 3.3 to 
>>>> 5.0 in Windows 8.1 x64.
>>>> One of them was brand new and never used before and was upgraded in A 
>>>> mode with no external supply. Everything OK no problems. (upgrade done 
>>>> with 
>>>> USB-A to micro-USB-B cable, no OTG ends)
>>>> The other two were already used with a smartphone and after the upgrade 
>>>> they started to have the issues already described here (before the upgrade 
>>>> they were OK). For these two, the upgrade has been done certainly in H 
>>>> mode 
>>>> and with external supply for the first time. After that it has been done 
>>>> through every possible way. (upgrade also done with USB-A to micro-USB-B 
>>>> cable, no OTG ends)
>>>> As Ytai confirmed in this thread, use a normal USB-A (PC) to 
>>>> micro-USB-B (IOIO) connector. No need for OTG ends and do not use the ones 
>>>> that come with IOIO (micro-USB-A) because they force IOIO to be in H mode.
>>>> This non-bootloader issue really seems to be very common...
>>>>
>>>> Ytai,
>>>>
>>>> 2.05V. (in case you missed my last response)
>>>>
>>>>
>>>> Terça-feira, 23 de Setembro de 2014 14:34:02 UTC+1, 
>>>> [email protected] escreveu:
>>>>
>>>>> Hi !
>>>>> I have similar problems as here reported thread: 
>>>>> https://groups.google.com/forum/#!topic/ioio-users/_GlTiiui5tI
>>>>> I never managed to upgrade using Windows 8.1, but Windows 7 is working 
>>>>> nearly ok. In the bootloader mode PC is connected, but not in the 
>>>>> application mode. However Android HELLO IOIO connects and reports version 
>>>>> 5. Also my own Android app using ioiolib v5 connects
>>>>> I am a little confused about USB cables: The board that has problems 
>>>>> is from Seedstudio, it came with red USB cable and micro A usb in IOIO 
>>>>> side. I made upgrade using it.
>>>>> I have new boards from AliExpress. These are with black USB cable with 
>>>>> more common micro B connector on IOIO side. Is it so that upgrade cannot 
>>>>> be 
>>>>> made with these black cables.
>>>>>
>>>>> tiistai, 23. syyskuuta 2014 14.55.12 UTC+3 AF kirjoitti:
>>>>>>
>>>>>> Ytai,
>>>>>>
>>>>>> 2.05V.
>>>>>>
>>>>>> Terça-feira, 23 de Setembro de 2014 3:06:11 UTC+1, Ytai escreveu:
>>>>>>>
>>>>>>> With the IOIO connected to a PC in non-bootloader mode, can you 
>>>>>>> please measure the voltage between GND and the middle leg of the host 
>>>>>>> switch? It should read about 2.1V.
>>>>>>> On Sep 22, 2014 4:57 PM, "AF" <[email protected]> wrote:
>>>>>>>
>>>>>>>> Ytai,
>>>>>>>>
>>>>>>>> Just tried on a different PC. No luck. Same issue happens. Unknown 
>>>>>>>> USB Device in non-bootloader mode. Cannot read app firmware in 
>>>>>>>> ioiodude 
>>>>>>>> when in this mode. (connected the IOIO in "A" position with no 
>>>>>>>> external 
>>>>>>>> supply)
>>>>>>>> About the USB hub in the middle, I had already verified that 
>>>>>>>> before. With or without it same issue happens too.
>>>>>>>> I don't know what to do anymore, this is so frustrating...
>>>>>>>>
>>>>>>>> Segunda-feira, 22 de Setembro de 2014 21:14:58 UTC+1, Ytai escreveu:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 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-IO
>>>>>>>>>>>> IODude. 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 &#34;Made-In-China&#34; Era 
>>>>>>>>>>>>>> The impossible &#40;but real&#41; 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/topic/ioio-users/qY-fe0ikwLs/uns
>>>>>>>>>>>>> ubscribe.
>>>>>>>>>>>>> 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.
>>>>>>>>
>>>>>>>  -- 
>>>> 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] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> 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.

Reply via email to