08:02 <Guest41> hello all, I have a BB black and I think that i broke it, When i power on the D1 just flick one time and that it. Nothing more. I thought that something is in short and the beaglebone can not start

08:02 <Guest41> but how can i find what is broke?

08:05 <zmatt> Guest41: if the power led briefly flashes and nothing more, that implies serious hardware damage, typically to the SoC itself

08:05 <zmatt> e.g. due to I/O being damaged by overvoltage

08:07 <Guest41> ok, it is possible to solve it? I read on an forum about a guy that have an issue with AIN port and fix it by removing FB2  https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/f/forum/30610/beaglebone-black-unable-to-power-on

08:07 <Guest41> how can i figure where is the problem?

08:08 <Guest41> maybe is just a capacitor broken

08:10 <zmatt> Guest41: that guy specifically damaged analog inputs (again, probably due to overvoltage)... disconnecting the adc power supply (by removing FB2) allowed the beaglebone to boot again in his particular case, albeit now without analog inputs

08:11 <zmatt> if you have reason to believe you blew up an analog input then you could try the same workaround, but the same workaround does not apply in any other situation

08:15 <zmatt> what's happening is that overvoltage on a pin can damage the ESD protection on that pin inside the chip in a way that results in an internal short-circuit of the I/O power supply rail to ground. the PMIC detects the overcurrent that results from this short and immediately powers off

08:19 <Guest41> i was trying to use and lcd with an 4.3' lcd cape.. but i moved the lcd connector when it was power on

08:21 <zmatt> "moved" ?

08:22 <Guest41> disconnect and connect

08:22 <zmatt> yeah that sounds like an incredibly bad idea

08:23 <Guest41> it is a bad idea :D

08:24 <zmatt> an lcd screen requires some relatively high voltages, and those connectors are definitely not designed to be hotpluggable... you probably either caused a brief short between pins or simply connected some pins but not others, either way resulting in a bad voltage spike on some data line or something

08:24 <zmatt> that would be my guess

08:25 <zmatt> just to confirm, you've tested the beaglebone without the cape?

08:26 <Guest41> yes, and i have the same behavior

08:27 <zmatt> k, yeah, if there's lines on that connector that go directly to the bbb then I can easily imagine trying to hotplug it could insta-fry the bbb

08:36 <zmatt> Guest41: in general, avoid hotplugging things that aren't designed to be hotpluggable

08:38 <Guest41> that is a really good advise. but i think is a bit late. It is possible to do something for my bbb. how can i check if there is something in short to gnd? where i suppose to look first?

08:40 <zmatt> in this situation it sounds like a waste of time. based on what you've said it seems virtually certain that you've damaged the SoC itself

08:41 <zmatt> sorry

08:42 <Guest41> it is ok, i did not think that i can fix it. I just want to check.

08:42 <zmatt> you could probably confirm which of the on-board power supply rails is getting shorted to ground by measuring these lines with a scope while attempting to power up, but that's already not easy and there's very little you can do with the information

08:43 <Guest41> I already try the workaround for AIN port because LCD cape have AIN0-AIN3 connected. But did not help

08:45 <Guest41> anyway if the TPS65217 or any other SoC is brocken i don't think i can change it. it is easier to buy other BBB

08:45 <zmatt> yeah, I was about to mention that, but if that had no effect then it's a digital I/O that's blown and then there's nothing you can do

08:45 <zmatt> not the TPS, the AM3358

08:46 <zmatt> the TPS is the PMIC, it generally doesn't fail I think

08:48 <Guest41> thank you anyway

23:30 <nick12310> Using pru shared memory, what is the highest address I can use? The starting adress is 0x10000, and from what I see there are 12 kB of shared memory. Is the highest address 0x13000?