I've currently burned 3 different CHGIC chips on boards. I've been running 
the board powered off a power supply set to 18V. I have other boards booted 
at the same time, and have booted up all of these boards on the same power 
before. There are different ports connected, but none of them are being 
used. I believe the trend I noticed right before they break is that they 
power on, but are unresponsive. I power cycle them and they continue to be 
unresponsive. Then I plug them in a 3rd time, and the CHGIC chip pops and 
smokes. 

Is there something I can do? I can't have boards continuing to break. And 
from the last message, it sounded like his board burned from even just 15V. 

On Friday, May 19, 2017 at 9:54:39 AM UTC-7, Jason Kridner wrote:
>
>
> On Thu, Apr 13, 2017 at 8:43 AM <[email protected] <javascript:>> 
> wrote:
>
>> I'm seeing a problem that may be related.  We have now fried 3 BeagleBone 
>> Blues Rev A2.  
>>
>
> I recommend starting a new thread for a different issue. Otherwise, I find 
> it difficult to see if issues are getting useful responses. I understand 
> you saw this one as possibly related, but you say you've seen smoke and I 
> don't want to miss issues like that. The outer thread still looks like it 
> could be file system corruption to me.
>  
>
>> We started using ours with a 15V 2.6A supply *without* connecting a LiPo 
>> battery.  After only a couple of power cycles, the battery charging IC gets 
>> very hot and pops with a puff of smoke and a burned trace on the board.  
>> I've not seen any similar/related posts. 
>>
>
> I believe this operation is meant to be fine. The charging circuit should 
> provide power to the system in this case.
>  
>
>>  Are the posted docs incomplete or incorrect?  Is 12V the max? 
>>
>
> 18V is the max.
>  
>
>>  Is it required to have a LiPo battery attached at all times when powered?
>>
>
> We generally expect you to have the LiPo battery, but I believe the case 
> where no battery is present should be OK.
>
> Did the board come with the wire on CHGIC or is that damage as well? What 
> kind of load did you have on the system when it was damaged?
>  
>
>>
>>
>> <https://lh3.googleusercontent.com/-iGoDPtK8vsQ/WO9xm3PwoCI/AAAAAAAAAuI/jyqucwvijQ8pY4rLVvc0fpWTh8IceToiwCLcB/s1600/IMG_0494.JPG>
>>
>>
>> On Thursday, March 30, 2017 at 10:53:30 AM UTC-4, Ted Carancho wrote:
>>>
>>> Help!  My BBBL just arrived Monday and was in the middle of porting my 
>>> quadcopter code to it.  I was able to get 9DOF measurements from it and 
>>> decided to take it to the library with me, so I put it back into the static 
>>> bag it came with, placed it in the original box in between the ESD foam it 
>>> came with and placed it into my backpack.  When I took it out, I found that 
>>> it was unresponsive.  I thought maybe I somehow bricked it by not doing a 
>>> shutdown -h before unplugging it, so I tried to follow online directions on 
>>> booting from an external uSD card.
>>>
>>> If I power the board from USB or an external 3S Lipo, all I see is the 
>>> blue ON LED, the LIPO status LED stuck at 75, and the G and R LED's on 
>>> (picture below).  If I press the SD button with the uSD already plugged in 
>>> and apply power, I don't see any blinking lights that tell me it's booting 
>>> from the uSD card.
>>>
>>>
>>> <https://lh3.googleusercontent.com/-Yc4XsOXH3Mo/WNyzdyE9ZfI/AAAAAAAAAUU/mO37vRZfgvs50Sxu9LFfIMP8Y4SxJQ0BACLcB/s1600/BBBL.JPG>
>>>
>>>
>>> I've tried the Debian 8.7 2017-03-19 
>>> <https://debian.beagleboard.org/images/bone-debian-8.7-lxqt-4gb-armhf-2017-03-19-4gb.img.xz>
>>>  IoT 
>>> and Debian 8.7 2017-03-19 
>>> <https://debian.beagleboard.org/images/bone-debian-8.7-lxqt-4gb-armhf-2017-03-19-4gb.img.xz>
>>>  LXQT 
>>> firmware, I tried a 8GB and a 32GB uSDHC card, I tried 2 different USB 
>>> cables.  When plugged into a USB port, I can't find the network access 
>>> point to be able to login using 192.168.7.2, and also I can't ping the 
>>> device over it's wireless network after I had configured the wifi using 
>>> connman.
>>>
>>> I'm starting to think that the hardware was somehow damaged (but I felt 
>>> I took appropriate ESD considerations, and transported it in its box).
>>>
>>> This is my first beagle bone product ever (but have used many Arduino's, 
>>> RPI and Intel Edison).  Is there some newbie mistake I'm making?  Thanks 
>>> for your help in advance!
>>>
>>>
>>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/6f1a5c15-eebd-41ae-9256-2360afa2435f%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/beagleboard/6f1a5c15-eebd-41ae-9256-2360afa2435f%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4549435f-b17e-4f20-be10-982a2e26b901%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to