from:"Marco Thome"

Re: [beagleboard] Re: BBB not powering on

2017-10-24 Thread Marco Thome

Is this a common issue? I can plug both boards to any computer in the room 
and they'll have the same behavior everytime..

Anyways, I'll grab an oscilloscope as soon as possible to check what is 
going on over the board. At least it's still working on a wall power supply.

I'm sorry this subject is taking so long, I'm new on power issues on this 
board (which I must add that both are old, I guess they could be Rev Bs, 
since there're still some Rev Bs around here).
Thank you for the help so far.

Marco

On Thursday, October 19, 2017 at 1:16:27 PM UTC-2, Graham wrote:
>
> All of your description points at a power supply problem.
> If the USB power, even for a millisecond, drops below 4.5 Volts AT THE 
> BBB, the PMIC (Power Management IC) will shutdown.
> If you have a computer with a USB port on the low side of the USB Voltage 
> range (4.5 to 5.5 Volts) then what you describe happens.
> So that you have some margin in the system, you should hold the power AT 
> THE BBB between 4.75 and 5.25 Volts, even with heavy loads of booting or 
> updating.
>
> If you put an oscilloscope on the power connector of the BBB, you should 
> be able to see what is happening.
>
> --- Graham
>
> ==
>
>
>
> On Thu, Oct 19, 2017 at 6:56 AM, Marco Thome <maa...@gmail.com 
> > wrote:
>
>> Thing is that I'm using only the provided USB cable. What troubles me is 
>> that the board turns on when I'm using a power adapter (DC jack), but it 
>> dies as soon as I connect it to the computer with an USB cable.
>>
>> On Wednesday, October 18, 2017 at 11:15:12 AM UTC-2, Graham wrote:
>>>
>>> Most likely, you are having power supply issues.
>>>
>>> The power drain of the BBB will double or triple during boot and update, 
>>> (relative to idle) so you need a power supply that can handle this.
>>>
>>> Many long USB cables are not capable of powering a BBB during peak loads.
>>>
>>> Some of the cheap wall supplies can't handle it.
>>>
>>> --- Graham
>>>
>>> ==
>>>
>>> On Wednesday, October 18, 2017 at 7:14:48 AM UTC-5, Marco Thome wrote:
>>>>
>>>> Hi,
>>>>
>>>> I was working with a brand new beaglebone black on usb as usual. 
>>>> Everything was fine, until I connect it to the company's network over 
>>>> ethernet and updated the board with *apt-get update* then *apt-get 
>>>> upgrade*. In the middle of the upgrade, the beagleboard just died. 
>>>> None of the five leds are on, no matter which usb port or computer it's 
>>>> connected to. I tried the same config with another board and it turned on 
>>>> just fine.
>>>>
>>>> I'm a little worried about it because it isn't the first time this kind 
>>>> of problem occurs. I was working with another board also over usb but on 
>>>> another computer and the same thing happened, though on this board the 
>>>> power led at least blink once when connected.
>>>>
>>>> It may not be so helpful, but I'm attaching a printscreen of what I was 
>>>> doing at the time. I had no chance to upgrade the kernel.
>>>>
>>>> Both boards only turn on when on power plug, but as soon as I connect 
>>>> them to the computer over usb, they die (no led lit).
>>>>
>>>> What am I doing wrong?
>>>>
>>>> Regards,
>>>> Marco
>>>>
>>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/beagleboard/oVelgZJExEQ/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> beagleboard...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/dc6f1f34-d993-414f-ab35-3bbd054158b5%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/beagleboard/dc6f1f34-d993-414f-ab35-3bbd054158b5%40googlegroups.com?utm_medium=email_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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/543913d3-2864-41fd-a369-05f69c08ba1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB not powering on

2017-10-19 Thread Marco Thome

Thing is that I'm using only the provided USB cable. What troubles me is 
that the board turns on when I'm using a power adapter (DC jack), but it 
dies as soon as I connect it to the computer with an USB cable.

On Wednesday, October 18, 2017 at 11:15:12 AM UTC-2, Graham wrote:
>
> Most likely, you are having power supply issues.
>
> The power drain of the BBB will double or triple during boot and update, 
> (relative to idle) so you need a power supply that can handle this.
>
> Many long USB cables are not capable of powering a BBB during peak loads.
>
> Some of the cheap wall supplies can't handle it.
>
> --- Graham
>
> ==
>
> On Wednesday, October 18, 2017 at 7:14:48 AM UTC-5, Marco Thome wrote:
>>
>> Hi,
>>
>> I was working with a brand new beaglebone black on usb as usual. 
>> Everything was fine, until I connect it to the company's network over 
>> ethernet and updated the board with *apt-get update* then *apt-get 
>> upgrade*. In the middle of the upgrade, the beagleboard just died. None 
>> of the five leds are on, no matter which usb port or computer it's 
>> connected to. I tried the same config with another board and it turned on 
>> just fine.
>>
>> I'm a little worried about it because it isn't the first time this kind 
>> of problem occurs. I was working with another board also over usb but on 
>> another computer and the same thing happened, though on this board the 
>> power led at least blink once when connected.
>>
>> It may not be so helpful, but I'm attaching a printscreen of what I was 
>> doing at the time. I had no chance to upgrade the kernel.
>>
>> Both boards only turn on when on power plug, but as soon as I connect 
>> them to the computer over usb, they die (no led lit).
>>
>> What am I doing wrong?
>>
>> Regards,
>> Marco
>>
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/dc6f1f34-d993-414f-ab35-3bbd054158b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB not powering on

2017-10-18 Thread Marco Thome

Hi,

I was working with a brand new beaglebone black on usb as usual. Everything 
was fine, until I connect it to the company's network over ethernet and 
updated the board with *apt-get update* then *apt-get upgrade*. In the 
middle of the upgrade, the beagleboard just died. None of the five leds are 
on, no matter which usb port or computer it's connected to. I tried the 
same config with another board and it turned on just fine.

I'm a little worried about it because it isn't the first time this kind of 
problem occurs. I was working with another board also over usb but on 
another computer and the same thing happened, though on this board the 
power led at least blink once when connected.

It may not be so helpful, but I'm attaching a printscreen of what I was 
doing at the time. I had no chance to upgrade the kernel.

Both boards only turn on when on power plug, but as soon as I connect them 
to the computer over usb, they die (no led lit).

What am I doing wrong?

Regards,
Marco

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/2a666b29-68f1-4af0-86aa-d30f0ba0fccc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Unable to manually load dtbo to bone_capemgr slots

2017-08-14 Thread Marco Thome

I'm sorry for taking so long to reply.
I don't have a serial cable to see what's happening. I did what I could do: 
I erased everything and started again.
This time, I upgraded my kernel with options --bone-channel --lts-4_9 and 
then it started working!

I really do not understand why it didn't work before with other options, 
since I'm using the same dtbo file as before.

On Friday, August 11, 2017 at 11:33:40 AM UTC-3, RobertCNelson wrote:

> On Fri, Aug 11, 2017 at 6:02 AM, Marco Thome <maa...@gmail.com 
> > wrote: 
> > Tried to upgrade my bootloader and my board stopped booting. 
>
> Do you have a serial cable to log bootup? 
>
> Then we can see where and what caused the boot failure. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/2c05a633-6d5a-46e6-91a6-2c9680fac929%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Unable to manually load dtbo to bone_capemgr slots

2017-08-11 Thread Marco Thome

Tried to upgrade my bootloader and my board stopped booting.

On Thursday, August 10, 2017 at 11:38:58 AM UTC-3, RobertCNelson wrote:

> On Thu, Aug 10, 2017 at 8:11 AM, Marco Thome <maa...@gmail.com 
> > wrote: 
> > Hi, 
> > 
> > I started Reading about dts files a few days ago and wrote my own to set 
> > P8.42, P8.43, P8.44 and P8.46 as gpio outputs. I compiled it and tried 
> to 
> > echo it to /sys/devices/platform/bone_capemgr/slots, but I get no 
> response 
> > (my terminal just stops). 
> > 
> > Here's what I get on dmesg's last lines: 
> > [  407.020467] bone_capemgr bone_capemgr: part_number 'bb-gpio', version 
> > 'N/A' 
> > [  407.020531] bone_capemgr bone_capemgr: slot #4: override 
> > [  407.033061] bone_capemgr bone_capemgr: slot #4: auto loading handled 
> by 
> > U-Boot 
>
> "auto loading handled by U-Boot" see the directions here: 
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays 
>
> Regards, 
>
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/0983c8d5-b3e9-4e9b-ab4f-9f773eea6c92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Unable to manually load dtbo to bone_capemgr slots

2017-08-10 Thread Marco Thome

Hi,

I started Reading about dts files a few days ago and wrote my own to set 
P8.42, P8.43, P8.44 and P8.46 as gpio outputs. I compiled it and tried to 
echo it to /sys/devices/platform/bone_capemgr/slots, but I get no response 
(my terminal just stops).

Here's what I get on dmesg's last lines:
[  407.020467] bone_capemgr bone_capemgr: part_number 'bb-gpio', version 
'N/A'
[  407.020531] bone_capemgr bone_capemgr: slot #4: override
[  407.033061] bone_capemgr bone_capemgr: slot #4: auto loading handled by 
U-Boot

And here's my custom dts:

/dts-v1/;
/plugin/;
/ {
 compatible = "ti,beaglebone", "ti,beaglebone-black";
 /* identification */
 part-number = "bb-gpio";
 version = "00a0";
 /* state the resources this cape uses */
 exclusive-use =
 "P8.42",
 "P8.43",
 "P8.44",
 "P8.46",
 "gpio2_11",
 "gpio2_8",
 "gpio2_9",
 "gpio2_7";
 fragment@0 {
  target = <_pinmux>;
  __overlay__ {
   bb_gpio_pins: pinmux_bb_gpio_pins {
pinctrl-single,pins = <
0x0b4 0x0f /* P8_42 GPIO2_11 */
0x0a8 0x0f /* P8_43 GPIO2_8 */
0x0ac 0x0f /* P8_44 GPIO2_9 */
0x0a4 0x0f /* P8_46 GPIO2_7 */
>;
   };
  };
 };
 fragment@1 {
  target = <>;
  __overlay__ {
   bbgpio : gpio {
pinctrl-names = "default";
pinctrl-0 = <_gpio_pins>;
status = "okay";
/*oe {
 gpio-name = "oe";
 gpio = < 11 0x00>;
 output;
};
clk {
 gpio-name = "clk";
 gpio = < 8 0x00>;
 output;
};
le {
 gpio-name = "le";
 gpio = < 9 0x00>;
 output;
};
sdi {
 gpio-name = "sdi";
 gpio = < 7 0x00>;
 output;
};*/
   };
  };
 };
};


I tried upgrading kernel (right now, *uname -a* returns: Linux arm 
4.9.41-ti-r53 #1 SMP PREEMPT Thu Aug 10 02:34:57 UTC 2017 armv7l 
GNU/Linux), disabling audio/vídeo/wireless/adc overlays, enabling/disabling 
cape_universal, loading internet dtbos (from kilobaser 
and
 
bbbadventures ) 
and default ones (like cape-universaln) and changing boards (I have 2 BBBs) 
and installing bb-cape-overlays through apt-get

I think I'm missing something really stupid, because I found nothing 
regarding this kind of error so far.
If I try to load the dtbos on boot through uEnv.txt, my board stops with 
the 4 user leds lit, which I understand as a signal that my BBB is not 
loading the OS. Of course, I can't ssh it.

What am I missing?

Best regards,
Marco

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/d7b3a25d-e723-4fa2-ab46-2eb014a10bbe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Unable to manually load any dtbo to slots

2017-08-10 Thread Marco Thome

Hi,

I started reading abou dts files a few days ago and wrote one to change the 
lasts P8 pins' mode, but I can't load my dtbo to 
*/sys/devices/platform/bone_capemgr/slots* with *echo*. Everytime I do 
that, my terminal gets no response and I get stuck (even ctrl + C does not 
work).
I tried disabling other capes like HDMI on *uEnv*, upgrading kernel, 
changing pinmode through *config-pin* (which returns no file/directory 
error), changing boards (I have access to a few BBBs), disabling/enabling 
universal cape and loading internet capes (from kiloblaser 
,
 
bbbadventures ) 
and default ones (like cape-universaln). I ought to think it must be 
something really stupid I'm missing, because I found nothing regarding this 
kind of error so far.

My custom dts:

/dts-v1/;
/plugin/;
/ {
 compatible = "ti,beaglebone", "ti,beaglebone-black";
 /* identification */
 part-number = "bb-gpio";
 /*version = "00A0";*/
 /* state the resources this cape uses */
 exclusive-use =
 "P8.42",
 "P8.43",
 "P8.44",
 "P8.46",
 "gpio2_11",
 "gpio2_8",
 "gpio2_9",
 "gpio2_7";
 fragment@0 {
  target = <_pinmux>;
  __overlay__ {
   bb_gpio_pins: pinmux_bb_gpio_pins {
pinctrl-single,pins = <
0x0b4 0x0f /* P8_42 GPIO2_11 */
0x0a8 0x0f /* P8_43 GPIO2_8 */
0x0ac 0x0f /* P8_44 GPIO2_9 */
0x0a4 0x0f /* P8_42 GPIO2_7 */
>;
   };
  };
 };
 fragment@1 {
  target = <>;
  __overlay__ {
   bbgpio : gpio {
pinctrl-names = "default";
pinctrl-0 = <_gpio_pins>;
status = "okay";
/*oe {
 gpio-name = "oe";
 gpio = < 11 0x00>;
 output;
};
clk {
 gpio-name = "clk";
 gpio = < 8 0x00>;
 output;
};
le {
 gpio-name = "le";
 gpio = < 9 0x00>;
 output;
};
sdi {
 gpio-name = "sdi";
 gpio = < 7 0x00>;
 output;
};*/
   };
  };
 };
};

Last lines of dmesg:
[   64.071193] pru-rproc 4a334000.pru0: PRU rproc node 
/ocp/pruss_soc_bus@4a326000/pruss@4a30/pru@4a334000 probed successfully
[   64.090943] remoteproc remoteproc2: 4a338000.pru1 is available
[   64.091062] pru-rproc 4a338000.pru1: PRU rproc node 
/ocp/pruss_soc_bus@4a326000/pruss@4a30/pru@4a338000 probed successfully
[  321.616414] bone_capemgr bone_capemgr: part_number 'bb-gpio', version 
'N/A'
[  321.616478] bone_capemgr bone_capemgr: slot #4: override
[  321.630993] bone_capemgr bone_capemgr: slot #4: auto loading handled by 
U-Boot

uname -a (right now):
Linux arm 4.9.41-ti-r53 #1 SMP PREEMPT Thu Aug 10 02:34:57 UTC 2017 armv7l 
GNU/Linux

pinctrl pins (71 ~ 75):
pin 71 (PIN71) 44e1091c  pinctrl-single
pin 72 (PIN72) 44e10920  pinctrl-single
pin 73 (PIN73) 44e10924  pinctrl-single
pin 74 (PIN74) 44e10928  pinctrl-single
pin 75 (PIN75) 44e1092c 0030 pinctrl-single


Can anyone point out what I may be missing?

Best regards,
Marco

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/334bf1ec-5a4c-43da-821f-00802abec5ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BBB not powering on

[beagleboard] Re: BBB not powering on

[beagleboard] BBB not powering on

Re: [beagleboard] Unable to manually load dtbo to bone_capemgr slots

Re: [beagleboard] Unable to manually load dtbo to bone_capemgr slots

[beagleboard] Unable to manually load dtbo to bone_capemgr slots

[beagleboard] Unable to manually load any dtbo to slots

7 matches

Site Navigation

Mail list logo

Footer information