<https://lh5.googleusercontent.com/-izpWXe4Mgaw/UsT9VogKF-I/AAAAAAAAAAw/OQKDlfDwv7A/s1600/ioio3.png> Thanks. I just managed to detect the IOIO by using another cable, apparently the cable i was using was a bit long i guess., now I can detect my IOIO correctly, As i went on I encountered another problem. Im not sure if i should post this here but i will nevertheless, maybe you can help so here it is, tried the HelloIOIOSwing.jar and here is what happened. It stops at "waiting for handshake". After i re-installed the driver you can see in the picture what happened. After that its just "waiting for handshake again". Do yo think i have a bad board? On Wednesday, January 1, 2014 9:02:00 PM UTC-8, gopi natarajan wrote: > > @Xelhion, > USBID pin is assigned to port pin RF3(Peripheral Pin Select > number of this pin is RP16). You can internally pull up this USBID pin by > using internal pull up enable Register CN2PU. That is, you have to set BIT0 > of CN2PU register. and make sure that application layer doesn't change > CN2PU register or atleast its BIT0. By doing this, the USBID pin will be > pulled up to (VDD-1.1V) as mentioned in PIC24FJ256DA206 controller > datasheet page no 163. > > If you find this doesn't work, then you have to manually pull the > USBID line up by using an external pull up resistor. One end of the > resistor should be connected to 3.3V and the other end is connected to > USBID pin. This is bit risky, because, you need to find the USBID track in > the PCB that goes from the USB MicroAB Receptacle to PIC24FJ256DA206. And > don't connect the other end of the Resistor directly to Microcontroller's > RF3 pin. This may cause false trigger to the near by pins. > > On Thursday, 2 January 2014 09:54:30 UTC+5:30, xelhion wrote: >> >> Excuse me but I am having the same issue, can you please post a picture >> of what you did? I cannot seem to visualize how you pulled up the USB ID. >> Thanks in advance. >> >> On Monday, November 25, 2013 3:17:51 AM UTC-8, gopi natarajan wrote: >>> >>> Hi ytai. I hope i have fixed this Issue. >>> >>> As per the IOIO-OTG firmware, USB stack has been initialized twice. That >>> is, Bootloader initializes USB Device stack at the beginning if Boot pin is >>> grounded. Else, the control jumps to Application part where USB OTG Stack >>> been initialized. During this OTG Initialization, i found that my USBID pin >>> floats and initializes the OTG stack randomly in USBDeviceTasks() function. >>> For this, i pulled the USBID line up using 3.3v pin via 10K resistor. Now >>> the board enumerates fine in device mode and i can execute HelloIOIOSwing >>> and Console applications without any error. >>> >>> I can even connect OTG board with android device with my external pull >>> up in my USB ID pin. Now every thing works fine. >>> >>> On Monday, 25 November 2013 07:04:44 UTC+5:30, Ytai wrote: >>>> >>>> Not sure what can cause that. Have you tried clock recalibration (as >>>> described one the IOIODude wiki page)? >>>> >>>> >>>> On Thu, Nov 21, 2013 at 9:04 PM, gopi natarajan <[email protected]>wrote: >>>> >>>>> Hi all, I too experiencing the same problem as Mr Christian >>>>> Wehrenfennig explained in this thread. My IOIO-OTG board can successfully >>>>> enumerates with my PC while its in Boot mode(I verified this by writing >>>>> Application firmware 3.30 and 4.0). Eventually the USB connection gets >>>>> lost >>>>> while the board initializes Application's USB Stack. Looking for your >>>>> help. >>>>> >>>>> For your information,. >>>>> >>>>> I use UBUNTU 12.04 PC, >>>>> Bootloader Version : Device bootloader V4.0 >>>>> Application Version : App 3.30 (I also tried AppV4.0) >>>>> >>>>> On Wednesday, 24 April 2013 21:54:26 UTC+5:30, Christian Wehrenfennig >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I'm experiencing problems connecting my new IOIO-OTG to a PC or to my >>>>>> phone (with the phone acting as a host). The PC reports that the device >>>>>> descriptor request failed and the windows device manager comes up with >>>>>> the >>>>>> error "The device could not start". Interestingly the board enumerates >>>>>> properly when booting into the bootloader, so firmware updates via >>>>>> IOIOdude >>>>>> are possible. The board also works properly in host mode with a phone >>>>>> connected as a device. What can I do to fix/further investigate this? >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Christian >>>>>> >>>>> -- >>>>> 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/groups/opt_out. >>>>> >>>> >>>>
-- 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/groups/opt_out.
