I’m having trouble troubleshooting the device. I’ve adjusted the screen ribbon several times, making sure to lock the black tabs. Perhaps I have damaged a component trying to assemble the Pokitto. So I want to know how to interpret the output of the pre-loaded testing program.
The testing program is emitting a rapid series of faint audio clicks / beeps. Is this the expected behavior when there is a problem connecting to the screen?
Thank you so much for your quick responses, Jonne. Unfortunately, I have to do this on my Mac. Following your instructions, I see the ‘CRP DISABLED’ volume mounted with the ‘firmware.bin’. The noises cease when it’s in Flash Drive mode.
Thats good. It means the processor is working and talking with the computer.
Now. Lets make sure your device is simply not out of charge. For safety reasons, Pokittos are shipped with li-pos at <30% charge.
Let the device charge for a while and try to start it up. Also, if you can, please take and post a pic of the lcd cable inside the lcd connector so we make 200% sure its not the cause
using windows 10, did everything above, can’t seem to connect to my pokitto as a usb flash drive. All I get is an unnamed volume (E:) which I can’t access. As you can see in the pic I uploaded, it says insert disk… any ideas why and how can I fix this please?
That is very puzzling @musashi. You see, I can’t understand why Pokitto would be identified as a portable device. I have never seen that. I would understand if the USB connection failed but to be identified as a wrong type of device makes no sense at all.
are you sure you have no additional drive management programs, such as HP Drive Manager?
No other drive management programs, this is a fairly fresh vanilla windows 10 install. Tried a few other USB cables, same problem. No other pc around right now, will have to wait for tomorrow. Bummer, was so looking forward to playing with pokitto.
need to run an errand, will try safe mode later, if it helps I grabbed the event log:
Device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_NXP&Prod_LPC1XXX_IFLASH&Rev_1.0#ISP&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} requires further installation.
Driver Management has concluded the process to add Service WUDFWpdFs for Device Instance ID SWD\WPDBUSENUM\_??_USBSTOR#DISK&VEN_NXP&PROD_LPC1XXX_IFLASH&REV_1.0#ISP&0#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B} with the following status: 0.
Driver Management concluded the process to install driver wpdfs.inf_amd64_4b4cfcfa114bdc22\wpdfs.inf for Device Instance ID SWD\WPDBUSENUM\_??_USBSTOR#DISK&VEN_NXP&PROD_LPC1XXX_IFLASH&REV_1.0#ISP&0#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B} with the following status: 0x0.
is your answer @musashi. It appears you possibly have the W10 anniversary update that broke the USBMSC functionality. You need the windows update mentioned in the last reply in the thread above
@musashi Oddly enough I had a similar problem with a Windows 10 computer that wasn’t recognising an SD slot (the event manager was showing up a similar “requires further installation”). In my case I got a replacement SD slot which seemed to fix the problem.
@jonne I wish I’d found that NXP link when I had the SD problem, I’m convinced it’s the same problem since the SD port in question was running off .
In fairness I find that updates don’t tend to take as long as they used to these days.