Is that with the application firmware running? The behavior of raising HOST in response to USBID pulled low is software-defined. It is not an inherent property of the hardware. For example, the bootloader doesn't do that. You can verify that the application firmware is properly installed and running by running HelloIOIOSwing / HelloIOIOConsole on a PC connected to the IOIO.
On Wed, Apr 15, 2015 at 4:29 PM, Vic Wintriss <[email protected]> wrote: > In trouble shooting the new VicsWagon board with the ioio circuitry on it, > I find that even though USBID is solidly low (ground), HOST does not go > high after startup. Do you know any reason why that might be? > > > On Tuesday, April 14, 2015 at 10:26:50 PM UTC-7, Vic Wintriss wrote: > >> I found the problem. The ioio board is not detecting the presence of the >> Android...again. I'll work on it and see if I can figure out why it >> suddenly stopped seeing the Android. >> >> On Tuesday, April 14, 2015 at 10:16:53 PM UTC-7, Ytai wrote: >> >> So, if I understand correctly, you are holding two different IOIO >> variants in your hand and an Android with your custom app. One of the >> variants doesn't work as expected. >> A few questions come to mind: >> >> 1. What's the (known) difference between them as far as hardware? >> 2. Have you verified that the firmware (both bootloader and app) are >> installed correctly? Hint: you can force-reinstall with ioiodude just in >> case. >> 3. What's not working with the "bad" variant? Does it charge the >> Android when connected? Does it pop the OpenAccessory dialog? >> 4. Does the "bad" board work with a PC? >> >> >> On Tue, Apr 14, 2015 at 10:10 PM, Vic Wintriss <[email protected]> wrote: >> >> Of course...I guess what I was trying to say is that my Android test >> program works fine with an ioio board on an earlier version of the >> VicsWagon. All of a sudden the Android has stopped talking to the ioio >> circuitry on the VicsWagon. >> >> On Tuesday, April 14, 2015 at 10:00:19 PM UTC-7, Ytai wrote: >> >> You don't download code from Android Studio to the PIC. >> You can either: >> >> - Download code from MPLABX to the PIC (firmware) >> OR: >> - Download code from Android Studio to Android (software) >> >> I don't understand what you're saying really. >> >> On Tue, Apr 14, 2015 at 9:57 PM, Vic Wintriss <[email protected]> wrote: >> >> The PIC. I have laid the ioio circuit down on the new VicsWagon board. >> Everything was working fine. I even was getting ultrasonic readings from >> the sensors on the VicsWagon and then all of a sudden I couldn't load from >> Android Studio any more. >> >> On Tuesday, April 14, 2015 at 8:22:30 PM UTC-7, Ytai wrote: >> >> What do you mean when you say "cannot load a test program from Android >> Studio into the processor"? >> Which processor? >> >> On Tue, Apr 14, 2015 at 8:05 PM, Vic Wintriss <[email protected]> wrote: >> >> When I run versions with IOIOdude when not in the bootloader mode, I get: >> >> VicMacMini-2:IOIODude VicMini$ ./ioiodude --port=/dev/tty.usbmodem1a121351 >> versions >> >> IOIO Application detected. >> >> >> Hardware version: SPRK0020 >> >> Bootloader version: IOIO0401 >> >> Application version: IOIO0500 >> >> VicMacMini-2:IOIODude VicMini$ >> >> On Tuesday, April 14, 2015 at 7:12:57 PM UTC-7, Vic Wintriss wrote: >> >> I have a new problem. Suddenly, I cannot load a test program from >> Android Studio into the processor. I can load the Blink program with >> ioioDude and it works OK. I can load the Android Studio test program into >> other IOIO boards and it works OK. The test program just blinks the led. >> Any ideas? >> >> On Monday, April 6, 2015 at 3:41:28 PM UTC-7, Ytai wrote: >> >> Device and host are standard USB terminology. Loosely speaking, the host >> is the one providing power and the one requiring to have intimate knowledge >> of the device's interface. >> In the case of the IOIO/Android, either way works (i.e. the IOIO can act >> either as a host or device). In your case, you're probably more interested >> in the IOIO being host scenario, which is the case in which that IOIO >> charges the Android. >> >> On Sun, Apr 5, 2015 at 5:47 PM, Vic Wintriss <[email protected]> wrote: >> >> I got the Android to detect the presence of the ioio board. By measuring >> the Vbus rail current, it looks like the Android that I am using (an older >> HTC) takes about 450 ma. When you say device, what are you referring to? >> When you say host, what are you referring to...assuming that I have the >> ioio board connected to an Android. >> >> On Saturday, April 4, 2015 at 3:50:02 PM UTC-7, Ytai wrote: >> >> The way USB works is that the device detects the presence of a host by >> sensing the VBUS rail. If it is about 5V, a host is present and the USB >> specifies what is the minimum the host must provide in order to be detected >> correctly. Under this specified voltage, the device may or may not detect >> the presence of a host. >> Now, what we're doing on the IOIO is taking a 5V signal and passing it >> through (effectively) a resistor to the VBUS rail. This means that the >> voltage on VBUS will drop linearly in the amount of current drawn (5V - >> I*R). So the more you try to limit the current by increasing the >> resistance, you'd also be lowering the VBUS voltage until eventually >> causing the Android to stop detecting the presence of a host. >> >> On Sat, Apr 4, 2015 at 2:31 PM, Vic Wintriss <[email protected]> wrote: >> >> I don't understand. Which voltage are you talking? The ioio is not >> measuring its 5 volt supply voltage. I would not expect the ioio 5 volt >> supply to drop a measurable amount in any case, regardless of load. The >> variable resistor is setting a charge current *to* the Android, >> therefore I would expect the Android supply voltage to raise...not drop. >> Is the Android monitoring it's own supply voltage? >> >> On Saturday, April 4, 2015 at 11:25:33 AM UTC-7, Ytai wrote: >> >> How much the voltage drops as result of different charge current limiting >> and how low the voltage can drop before the Android decides it is not >> connected is totally device dependent. This is in general a total hack >> (which does work great in certain cases). The formal USB specification >> doesn't actually allow doing that. >> >> On Fri, Apr 3, 2015 at 4:01 PM, Vic Wintriss <[email protected]> wrote: >> >> I tried another board and got it working OK. At least now, it recognizes >> the App is present. >> The next problem is to make the Android detect the board. How much >> charging current does the Android need in order to detect that it is >> connected to something? >> >> >> On Thursday, April 2, 2015 at 12:58:24 PM UTC-7, Vic Wintriss wrote: >> >> It is supposed to be an exact OTG copy. Something is keeping it in the >> boot mode even after reset. Any ideas? Can hardware keep it in boot >> mode? BOOT is not being held low. I will probe HOST. >> >> On Thursday, April 2, 2015 at 11:01:57 AM UTC-7, Ytai wrote: >> >> In what ways is your hardware different than the standard IOIO-OTG? Is it >> possible that for some reason it thinks it is in host mode? Can you probe >> the HOST signal? >> On Apr 2, 2015 10:41 AM, "Vic Wintriss" <[email protected]> wrote: >> >> It always says "Bootloader detected" >> >> VicMacMini-2:Downloads VicMinils /dev/tty.usb* >> >> /dev/tty.usbmodem1a121371 >> >> VicMacMini-2:Downloads VicMini$ ./ioiodude --port=/dev/tty.usbmodem1a121371 >> versions >> >> IOIO Bootloader detected. >> >> >> Hardware version: SPRK0020 >> >> Bootloader version: IOIO0401 >> >> Platform version: IOIO0030 >> >> VicMacMini-2:Downloads VicMini$ ./ioiodude --port=/dev/tty.usbmodem1a121371 >> --force write /Users/VicMini/Downloads/App-IOIO0500.ioioapp >> >> Writing image... >> >> [########################################] >> >> Writing fingerprint... >> >> Done. >> >> VicMacMini-2:Downloads VicMini$ ./ioiodude --port=/dev/tty.usbmodem1a121371 >> versions >> >> IOIO Bootloader detected. >> >> >> Hardware version: SPRK0020 >> >> Bootloader version: IOIO0401 >> >> Platform version: IOIO0030 >> >> VicMacMini-2:Downloads VicMini$ ./ioiodude --port=/dev/tty.usbmodem1a121371 >> --reset versions >> >> IOIO Bootloader detected. >> >> On Thursday, April 2, 2015 at 10:33:11 AM UTC-7, Vic Wintriss wrote: >> >> VicMacMini-2:Downloads VicMini$ ls /dev/tty.usb* >> >> VicMacMini-2:Downloads VicMini$ ./ioiodude --port=/dev/tty.usbmodem1a121361 >> versions >> >> IOIO Bootloader detected. >> >> >> Hardware version: SPRK0020 >> >> Bootloader version: IOIO0401 >> >> VicMacMini-2:Downloads VicMini$ ./ioiodude --port=/dev/tty.usbmodem1a121361 >> --reset write /Users/VicMini/Downloads/App-IOIO0500.ioioapp >> >> Comparing fingerprints... >> >> Fingerprint match - skipping write. >> >> VicMacMini-2:Downloads VicMini$ ./ioiodude --port=/dev/tty.usbmodem1a121361 >> versions >> >> It hangs up at this point and I have to exit. >> >> ^CVicMacMini-2:Downloads VicMini$ >> >> On Wednesday, April 1, 2015 at 8:48:49 PM UTC-7, Ytai wrote: >> >> This is only the bootloader. I would like to see what happens after a >> reset. That is, to get the "IOIO Application Detected" message. >> >> On Wed, Apr 1, 2015 at 8:16 PM, Vic Wintriss <[email protected]> wrote: >> >> VicMacMini-2:Downloads VicMini$ ls /dev/tty.usb* >> >> /dev/tty.usbmodem1a121311 >> >> VicMacMini-2:Downloads VicMini$ ./ioiodude --port=/dev/tty.usbmodem1a121311 >> versions >> >> IOIO Bootloader detected. >> >> >> Hardware version: SPRK0020 >> >> Bootloader version: IOIO0401 >> >> Platform version: IOIO0030 >> >> VicMacMini-2:Downloads VicMini$ ./ioiodude --port=/dev/tty.usbmodem1a121311 >> fingerprint >> >> d895d272a4b98529693fcdc4f69eeb3c >> >> VicMacMini-2:Downloads VicMini$ >> >> VicMacMini-2:Downloads VicMini$ ./ioiodude --port=/dev/tty.usbmodem1a121311 >> --reset versions >> >> IOIO Bootloader detected. >> >> >> Hardware version: SPRK0020 >> >> Bootloader version: IOIO0401 >> >> Platform version: IOIO0030 >> >> VicMacMini-2:Downloads VicMini$ >> >> On Wednesday, April 1, 2015 at 7:48:34 PM UTC-7, Ytai wrote: >> >> ./ioiodude --port=/dev/tty.usbmodem1a121321 *--reset *versions >> ./ioiodude --port=/dev/tty.usbmodem1a121321 versions >> >> OR: >> >> ./ioiodude --port=/dev/tty.usbmodem1a121321 fingerprint >> >> On Wed, Apr 1, 2015 at 7:43 PM, Vic Wintriss <[email protected]> wrote: >> >> VicMacMini-2:Downloads VicMini$ ./ioiodude --port=/dev/tty.usbmodem1a121321 >> versions >> >> IOIO Bootloader detected. >> >> >> Hardware version: SPRK0020 >> >> Bootloader version: IOIO0401 >> >> Platform version: IOIO0030 >> How do I get out of the bootloader mode without changing the port so I >> can check to see what it says is loaded? >> >> On Wednesday, April 1, 2015 at 4:16:09 PM UTC-7, Ytai wrote: >> >> What bootloader did you put on it? Was it able to correctly talk to >> IOIODude? What app did you install? 5 blinks doesn't mean anything... >> Possibly corrupt firmware. >> On Apr 1, 2015 4:13 PM, "Vic Wintriss" <[email protected]> wrote: >> >> Actually it blinks 5 times...only when the usb cable is connected to a >> phone. Any idea what that means? The boot pin is not being held low. >> >> On Wednesday, April 1, 2015 at 2:24:55 PM UTC-7, Ytai wrote: >> >> That means that you're in bootloader mode. This will happen when you >> power on with the boot pin held low. >> On Apr 1, 2015 1:22 PM, "Vic Wintriss" <[email protected]> wrote: >> >> When I power on, the LED blinks 3 times. Is that normal operation? I >> think that I have IOIO0500 installed. >> >> On Wednesday, April 1, 2015 at 11:41:06 AM UTC-7, Ytai wrote: >> >> The HOST signal is active high. >> >> On Tue, Mar 31, 2015 at 2:58 PM, Vic Wintriss <[email protected]> wrote: >> >> When you say assert, do you mean assert high or assert low? >> >> On Tuesday, March 31, 2015 at 2:36:24 PM UTC-7, Ytai wrote: >> >> The IOIO decides whether it should be host or device based on whether the >> USBID pin is pulled low (host) or left floating (device). On the standard >> IOIO board this pin would get pulled low by either plugging in a USB micro >> A connector to the A/B socket or by forcing it low using the on-board >> switch. >> When the IOIO application firmware detects that USBID is pulled low, it >> will assert the HOST signal, which will cause 5V to be supplied on the VBUS >> rail. >> >> On Tue, Mar 31, 2015 at 1:06 PM, Vic Wintriss <[email protected]> wrote: >> >> I got the boot loader flashed and am able to run the blink app...but >> having trouble with the Android charging circuit. >> >> Is there a detailed description of the Android charging circuit including >> the operation of Q1, Q2 and the VBUS and HOST pins of the PIC? My new >> circuit implementation does not seem to be charging the Android properly. >> >> On Monday, March 30, 2015 at 9:26:30 PM UTC-7, Vic Wintriss wrote: >> >> Thanks…think I got it running with the Pickit3…I’ll let you know. >> >> On Mar 30, 2015, at 9:18 PM, Ytai Ben-Tsvi <[email protected]> wrote: >> >> There's not much to it. Get a PIC programmer, or use a second IOIO as >> such. Flash the bootloader image that you can download from the downloads >> page and finally use IOIODude as usual to flash the application firmware. >> Here's an example of how to do the second IOIO way: >> https://www.youtube.com/watch?v=eUKAPP63QtU >> >> On Mon, Mar 30, 2015 at 6:40 PM, Vic Wintriss <[email protected]> wrote: >> >> Just got my new VicsWagon boards back with PIC soldered on the robot >> board with all ioio circuitry on the board, too. Where are the best >> instructions for flashing a boot loader and app firmware? >> >> -- >> 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 a topic in the >> Google Groups "ioio-users" group. >> To unsubscribe from this topic, visit https://groups.google.com/d/to >> pic/ioio-users/vOzO1t92Ryg/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. >> >> -- >> 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]. >> 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]. >> To post to this group, send email to >> >> ... > > -- > 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.
