The reason why DS3 never comes on is because the battery is fully charged. There is a more detailed explanation on the DS1 and DS3 LEDs of the breakout board here Re: Turning off Mini-Breakout Boards DS1 and DS3 LED Lights .
I believe the error comes from, as you said, from the USB device not receiving any power, which is also the reason you get the unable to initialize libusb: -99 error. Take a look at this thread Re: lsusb,get error: unable to initialize libusb: -99 .
Additionally, there is more information on the Breakout Board Hardware Guide Section 2.1 Intel® Edison Boards — Intel® Edison Breakout Board Hardware Guide that you might find helpful.
Thanks for your reply.
In the absence of a battery in both mine and intel_dan's case; what do you think might cause us to get different results from DS3?
In both cases there is no battery to read the charge of, yet mine remains off and intel_dan's shows illuminated.
As I mentioned I'm supplying 12 volt from an external power supply to J21.
The only difference I can find in the hardware guide is that a micro USB type A is recommended to activate host mode. I'm using a micro USB type B
The difference is the shape. However I have seen many people use USB type B OTG adapters with success, as long as the ID pin is grounded.
I connected my mini breakout board using micro USB type B cables, both LEDs lit up. I’m not using J21. Can you try to power your board using two USB to micro USB cables to see if this time both LEDs light up?
Have you already seen the breakout board hardware guide, in section 2.1.1 it states:
If you power the breakout board with a battery, it will not supply power as a USB host.
There is also useful information in section 2.1.1 about the different scenarios of using type A and type B cables.
I only get one LED when powering with two micro USB cables (nothing else connected, no battery no external power)
Also, now the Edison does not show up in windows as a storage device (as it did before to put the firmware files on).
The serial connection works fine.
Okay I have solved me original problem by reflashing Release 2.1 Yocto* complete image using the same Hardware.
Reboot OTA didn't do the trick, so I looked into using flashall.bat
The problem was that my Edison does not show up as a drive in windows and cannot be found through the dfu-util.
However, I did need to find a workaround in order to flash the image: