nslu2-log has quit [Remote host closed the connection]
nslu2-log has joined #beagle
vagrantc has quit [Quit: leaving]
samnob has quit [Ping timeout: 240 seconds]
Shadyman has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook has joined #beagle
ThunderChicken has joined #beagle
dTeaguela has joined #beagle
<ThunderChicken> So in a wondrous lapse of luck, happenstance, and awareness a tiny drip of solder found its way onto the PMIC chip across pins 3 to 6 though mainly across the battery and bat sense pins(BBB from like....2013?). Having discovered this after plugging a battery into the header (populated minimally but properly from what I read (ie with resistor and
<ThunderChicken> such)) and the wires/pins/pcb attempting to go nuclear, I further discovered the board would not respond at all when powered from USB or barrel plug. These attempts were made before discovering the shorted pins. I have taken solder braid and flux to the side of the chip in hopes of clearing any bridging from solder that may have flowed under the
<ThunderChicken> package though I cant say for sure I got it all. My next step is to remove the LAN and barrel plugs to get a better look at it, then just remove the chip all together and either reflow it back onto the board after some pad cleanup, or order a replacement. There arent any obvious signs of high currents down stream (no blown components or discolored
<ThunderChicken> joints/packages), and the datasheet for that chip says it has some pretty spiffy safety features (which I realize would not prevent 4.2v from a fully charged lipo from energizing whatever rail it touched, though it was dead shorting to itself/gnd, so I imagine there wasnt much preference for flowing down stream). Finally to the question: Anyone
<ThunderChicken> care to give-me-some/crush-all hope that the rest of the board beat the odds and could be okay once any bridge fault is removed or PMIC is replaced? Is there any way I could test the rest of the circuits for 'not being blown' without having a PMIC on the board?
<zmatt> ThunderChicken: well a short between bat and bat-sense wouldn't cause any problems, they're *supposed* to be shorted together (albeit preferably as close to the battery as possible)
<zmatt> while a short from bat to ground will mostly be unpleasant for the battery, not for the bbb
<zmatt> ohh you shorted it to VLDO1 ?
<zmatt> if you managed to put 4.2V on VLDO1, you can be pretty sure the AM335x is dead
<zmatt> since that's a 1.8V supply
<zmatt> (pin 3 is VLDO1)
<ThunderChicken> (*reply to initial reply about shorts: so a good chance there is an uncleared bridge is still under it maybe and the IC protections are doing their jobs?) I cant say absolutely, It happened a few years ago and its been in a 'random stuff to mess with' box, finally getting around to actually gearing up to lift the chip. I did the solder removal
<ThunderChicken> before boxing it, so the pins/pads are all stripped, but IIRC I believe the short was initially over the batt batt sense and possibly pin 7 ('sys' on the datasheet). At least at the time the battery was on it. The solder did flow about some in initially trying to clean it up. There is a solid hope against hope that no dangerous voltage found its
<ThunderChicken> way into something bad, but the only chance it would have (supposing only the batt pins initially) would be when It would have been powered either through USB or barrel. Which Im hoping means the PMIC detected some f$%kery and is just keeping itself in a deactivated fault state
<ThunderChicken> Like, I wouldnt be surprised if its fried. But if it were couldnt hurt it trying some stuff before binning it LOL
<ThunderChicken> its not like i could make it more broken if that were the case
<zmatt> I can't remember what happens if bat is shorted to batsense but not to an actual battery, I guess it's possible it confuses the pmic
<zmatt> I don't think that's the case, but I don't remember for sure
<zmatt> shorting to sys could certainly cause weird things though
<zmatt> that sounds plausible
<ThunderChicken> well at the header, in my case, it sparked some and quickly heated the resistor I added (per suggested addition). Nothing else gets hot or anything on 5v and power seems to stop at the PMIC from what ive probed so far and what I can remember
<ThunderChicken> So, it acted like a damn near dead short between + and - battery pins
<zmatt> wait it heater the resistor? what?
<zmatt> no significant current should ever flow through that resistor
<zmatt> (it's supposed to be an NTC for measuring the battery temperature, using a plain resistor is a trick to say "yeah yeah temperature is fine don't worry")
<zmatt> nothing you've described explains how you'd get a short to ground either
<zmatt> so whatever went wrong, it went way horribly more wrong than you could get by shorting bat/batsense/sys
<ThunderChicken> I believe so. my first hint something very hot under my finger. Maybe it was the pad/traces/vias and im remembering wrong. Yeah....I went with the 'its a reputable battery, I trust it, it has safeties, just work dang it' pain resistor heh
<ThunderChicken> Im under the assumption there was a path to the gnd pad under the ic. but that is an assumption
<zmatt> that pad is relatively far away, neighbouring pins are closer
<ThunderChicken> It was a relativly tiny blob that flew off my iron as some point. the tips were toast, was waiting for new ones, and just kind of beat them along til then. at some point a drip found that exact spot. And it was tiny.....until you look at the pins of that chip LoL  SMD stuff man.....crazy small some times
<zmatt> so I'm not sure how you'd get enough solder under there to short to ground without shorting a whoooole bunch of pins
<ThunderChicken> at some point I basically did, jsut not with the battery
<ThunderChicken> Tried to flow it away, or suck it up with stranded wire, before having braid and flux on hand
<zmatt> and destroyed the pmic in the process by overheating it? :P
<ThunderChicken> I didnt power it at all with obvious shorted pins, so there is that.
<ThunderChicken> haha yep, thats the other option
<ThunderChicken> XD
<zmatt> are you sure a single bbb is worth all this effort?
<ThunderChicken> I didnt pay for it (got it as a gift for designing some haunted house controllers), so Im only really out having to buy another one if I wanted to replace it.
<ThunderChicken> At ~$80 from what Ive seen, its worth messing with
<zmatt> depends on how much time you spend on trying to fix it, and how much you value your time
<ThunderChicken> Like, I dont expect it to come back. It would be a total fists popping up over monitor with a 'yissssssssssss' moment if it did. But, I figure I can learn a few things ruining it more if its toast anyways. So....[shrug]
<zmatt> anyway, my main worry in all this would be battery voltage making its way onto VLDO1 or some other output supply rail (whether due to a short or due to damaging the pmic), if that happened then it is all over for the board
<zmatt> if that didn't happen then it sounds plausible enough that replacing the pmic might be eonugh
<ThunderChicken> Currently, I have time to burn. Going through the random tinkery box is what is keeping the stir crazy at bay
<ThunderChicken> at the very least itd make a heck of a reddit post, rezzing a 'dead' BBB lol
<zmatt> some info about the bbb's power supply stuff here: https://elinux.org/BeagleBone_Power_Management
<zmatt> (I wrote that page a long time ago)
<zmatt> I don't recommend attempting to use the battery terminals at all, see warning on that page and the thread it links to
Shadyman has quit [Quit: Leaving.]
<ThunderChicken> sweeeet! I like digging into technical stuff, and it seems a lot of posts end at 'meh toss it and get another'. Well, the components exist, these are dev boards, some with the express purpose of introducing people to electronics, why not peel it apart find the dead thing and fix it? ya know? idk, maybe Im just that obsessive LoL Seems like fun to
<ThunderChicken> me though. Then again, the vast majority of people do need to consider time v lost cost, etc.... Still, while the bar has moved there is still some of that wall between the weekend warriors of plugging stuff in together and running tutorial code (and there is NOTHING wrong with that. At all. Ever. Learning is awesome, it doesnt matter how its dont
<ThunderChicken> or to what length), and the people who are aware of, know how to set efuses in fresh out the box SoC CPUs(per se), and what they affect, at the finest level of granularity. Like, someone could have had built most of these SBC designs (practically all if you have a reflow oven) so its a logical next step to troubleshooting, find the broken thing,
<ThunderChicken> replace it with a new one, initialize and fist pump XD
<ThunderChicken> oh?! there is a known issue with the battery stuff I take it?
<ThunderChicken> I was so excited when I discovered the BBB had onboard self contained power! Heck, I still complain the RPi and most variants dont have battery provisions and/or PoE
<ThunderChicken> *how its done
<ThunderChicken> **could have hand built
<ThunderChicken> Using a k400 wireless kb in my lap, the ergonomics leave much to be desired......
dTeaguela is now known as CrazyEddy
<zmatt> general-purpose AM335x doesn't have customer-programmable efuses, only some factory efuses (e.g. for the MAC address, which exact AM335x variant the part is, etc)
<zmatt> typically if people want to battery-power a BBB you just use a 5V usb power pack
<zmatt> though I'll admit that's not going to win any efficiency-award :P
weevoy has quit [Ping timeout: 265 seconds]
weevoy has joined #beagle
<ThunderChicken> Ahh. Im still in the twilight when it comes to some of those bare metal intricacies. I remember back when broadcom wifi chips were avoided like the plague if you wanted to do anything interesting on wifi (cough cough god bless WEP encryption when traveling cough cough). Then finally someone dropped some driver hack or something that effectively
<ThunderChicken> wedged promiscuous mode ability to the user. Sometimes it worked, sometimes it crashed the system, sometimes it didnt do anything LOL. Now Broadcoms are in dang near everything! Most of them more open than I ever remember them being before.
<ThunderChicken> true. I mean hats/capes/whatevs exist for UPS self power, and PoE. Itd just be cool to have a board that took those things into consideration with how the whole maker thing took off
<ThunderChicken> Though that opinion may be colored through wrestling with feeding RPis over long runs on crappy supplies XD
<ThunderChicken> I still waiting patiently for someone to incorporate QC communications so the board can tell the supply to bump the voltage up on a lossy run. That would be a selling point, IMHO. Of course, simple ideas can get complicated to impliment real quick....still a fun thought
<zmatt> seems unnecessary complication and cost, the BBB is already pretty crowded with components
weevoy has quit [Ping timeout: 250 seconds]
<ThunderChicken> Oh yeah, especially the BBB. Part of the drive to try with my board is how feature packed it is.
<ThunderChicken> Even these days, its still got some bullet points to throw around
<zmatt> if you're using a "lossy run" from a "crappy supply", the solution for that isn't to change the board :P
<ThunderChicken> Shhhhhhhhhh....... ;P
<ThunderChicken> lol
<zmatt> besides the BBB tolerates a fair bit of voltage drop as long as you don't need its usb host port
<zmatt> iirc
weevoy has joined #beagle
<ThunderChicken> what was the input voltage window on the BBBs? I dont see anything that looks like a normal vreg, but they do come in all sorts of packages and I cant remember what half of these packages do.... heh
* ThunderChicken is depopulating the power and lan currently...
<zmatt> power input is all handled by the pmic
<ThunderChicken> right, so the Vmax is the PMICs vmax?
<zmatt> I don't remember the min voltage, but I'm pretty sure I put it on that wiki page I linked earlier, otherwise see pmic documentation
<ThunderChicken> ah for sure :)
<zmatt> as far as max voltage you should not exceed 5.25V I think, per USB spec
<zmatt> protection kicks in a bit higher than that I think
<zmatt> but in general you should just supply 5V
<ThunderChicken> itll take 18v and like it! ....say, whats this pretty blue smoke? haha
<zmatt> in theory the pmic should protect the rest of the bbb from that... I would not be eager to test that theory :P
<ThunderChicken> well cnsidering how this board ends up could do all sorts of voltage injection 'experiments' hehehe
<ThunderChicken> naughty electronics will be made an example of XD
buckket has quit [Quit: buckket]
buckket has joined #beagle
buzzmarshall has joined #beagle
<set_> Hello!
<set_> I made it back outside of Not-so-Fun Friday.
<set_> Anyway, presume as you may. Up and away!
<set_> bbl...
ThunderChicken has quit [Quit: Client closed]
out_rageous is now known as outrageous
static_rocket has quit [Server closed connection]
static_rocket has joined #beagle
xet7 has joined #beagle
starblue has joined #beagle
vagrantc has joined #beagle
out_rageous has joined #beagle
outrageous has quit [Ping timeout: 260 seconds]