Skip to first unread message

KenUnix

unread,
Apr 3, 2020, 10:44:16 AM4/3/20
to BeagleBoard

I recently added an external 5V supply to the BBB barrel jack because I am going to add a relay cape.

If I issue "sudo shutdown -h now" the BBB looks like it is going to shutdown judging by the messages on the Jtag port but then re-boots?
See messages below.

I am using USB connectivity. If I unplug the 5V adapter and issue "sudo shuwdown -h now:" it works.

[  OK  ] Reached target Shutdown.
[  OK  ] Reached target Final Step.
[  OK  ] Started Power-Off.
[  OK  ] Reached target Power-Off.
[44567.694668] reboot: Power down   <=== This is where it should power off

U-Boot SPL 2019.04-00002-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500)  <=== This is what happens
Trying to boot from MMC2

U-Boot 2019.04-00002-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500), Build: jenkins-github_Bootloader-Builder-128

CPU  : AM335X-GP rev 2.1
I2C:   ready
DRAM:  512 MiB
No match for driver 'omap_hsmmc'
No match for driver 'omap_hsmmc'
Some drivers were not found
Reset Source: Power-on reset has occurred.
RTC 32KCLK Source: External.
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1

BeagleBoard.org Debian IoT Image 2020-03-26
Linux beaglebone 4.19.94-ti-r41 #1buster SMP PREEMPT Sat Mar 21 03:13:40 UTC 2020 armv7l GNU/Linux

Thanks


Robert Nelson

unread,
Apr 3, 2020, 10:57:24 AM4/3/20
to Beagle Board, Kenneth Martin
On Fri, Apr 3, 2020 at 9:44 AM KenUnix <ken.un...@gmail.com> wrote:
>
>
> I recently added an external 5V supply to the BBB barrel jack because I am going to add a relay cape.
>
> If I issue "sudo shutdown -h now" the BBB looks like it is going to shutdown judging by the messages on the Jtag port but then re-boots?
> See messages below.

Use:

sudo systemctl poweroff

Regards,

--
Robert Nelson
https://rcn-ee.com/

Robert Nelson

unread,
Apr 3, 2020, 2:49:49 PM4/3/20
to Beagle Board, Kenneth Martin
On Fri, Apr 3, 2020 at 10:02 AM Kenneth Martin <ken.un...@gmail.com> wrote:
>
> Robert,
>
> Thanks for the quick reply.
>
> Sorry same result.
>
> debian@beaglebone:~$ sudo systemctl poweroff
> debian@beaglebone:~$ [ OK ] Unmounted /run/user/1000.
> [ OK ] Stopped User Runtime Directory /run/user/1000.
> [ OK ] Started Show Plymouth Power Off Screen.
> [ OK ] Removed slice User Slice of UID 1000.
> Stopping Permit User Sessions...
> [ OK ] Reached target Unmount All Filesystems.
> Stopping LSB: Load kernel …d to enable cpufreq scaling...
> [ OK ] Stopped dnsmasq - A lightw…t DHCP and caching DNS server.
> [ OK ] Stopped Permit User Sessions.
> [ OK ] Stopped target Network.
> Stopping Connection service...
> Stopping Wicd a wireless a…d network manager for Linux...
> Stopping Raise network interfaces...
> Stopping WPA supplicant...
> [ OK ] Stopped LSB: Load kernel m…ded to enable cpufreq scaling.
> [ OK ] Stopped target Remote File Systems.
> [ OK ] Stopped Wicd a wireless an…red network manager for Linux.
> [ OK ] Stopped WPA supplicant.
> [ OK ] Stopped Connection service.
> Stopping D-Bus System Message Bus...
> [ OK ] Stopped D-Bus System Message Bus.
> [ OK ] Stopped target Basic System.
> [ OK ] Stopped target Sockets.
> [ OK ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
> [ OK ] Closed Syslog Socket.
> [ OK ] Closed Node-RED Socket.
> [ OK ] Stopped target Slices.
> [ OK ] Removed slice User and Session Slice.
> [ OK ] Stopped target Paths.
> [ OK ] Stopped Forward Password R…s to Plymouth Directory Watch.
> [ OK ] Closed D-Bus System Message Bus Socket.
> [ OK ] Stopped target System Initialization.
> Stopping Network Time Synchronization...
> Stopping Update UTMP about System Boot/Shutdown...
> [ OK ] Stopped target Swap.
> Stopping Restore / save the current clock...
> [ OK ] Stopped target Local Encrypted Volumes.
> [ OK ] Stopped Forward Password R…uests to Wall Directory Watch.
> Stopping Load/Save Random Seed...
> [ OK ] Stopped Network Time Synchronization.
> [ OK ] Stopped Restore / save the current clock.
> [ OK ] Stopped Update UTMP about System Boot/Shutdown.
> [ OK ] Stopped Load/Save Random Seed.
> [ OK ] Stopped Create Volatile Files and Directories.
> [ OK ] Stopped Raise network interfaces.
> [ OK ] Stopped target Local File Systems.
> [ OK ] Stopped target Local File Systems (Pre).
> [ OK ] Stopped Create Static Device Nodes in /dev.
> [ OK ] Stopped Create System Users.
> [ OK ] Stopped Remount Root and Kernel File Systems.
> [ OK ] Stopped Apply Kernel Variables.
> [ OK ] Stopped Load Kernel Modules.
> [ OK ] Reached target Shutdown.
> [ OK ] Reached target Final Step.
> [ OK ] Started Power-Off.
> [ OK ] Reached target Power-Off.
> [ 1598.168032] reboot: Power down
>
> U-Boot SPL 2019.04-00002-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500) <=== Reboot
> Trying to boot from MMC2
> Loading Environment from EXT4... ** File not found /boot/uboot.env **

Sorry i can't re-produce this on a BeagleBone Green..

Please run: sudo /opt/scripts/tools/version.sh so i can more easily validate..

debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
[sudo] password for debian:
git:/opt/scripts/:[62ea733f04b46cbcc4988eb0748bddac2301ede0]
eeprom:[A335BNLT�BBG115091771]
model:[TI_AM335x_BeagleBone_Green]
dogtag:[BeagleBoard.org Debian IoT Image 2020-03-30]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
2019.04-00002-g07d5700e21]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-19-TI-00A0]
UBOOT: Loaded Overlay:[BB-ADC-00A0]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]
UBOOT: Loaded Overlay:[M-BB-BBG-00A0]
kernel:[4.19.94-ti-r41]
nodejs:[v10.15.2]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
pkg:[bb-cape-overlays]:[4.14.20200330.0-0rcnee0~buster+20200330]
pkg:[bb-wl18xx-firmware]:[1.20200322.0-0rcnee0~buster+20200322]
pkg:[kmod]:[26-1]
pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~buster+20190327]
pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~buster+20200305]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video
plugdev users systemd-journal bluetooth netdev i
2c gpio pwm eqep remoteproc admin spi iio docker tisdk weston-launch
xenomai cloud9ide]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait c
oherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100]
dmesg | grep remote
dmesg | grep pru
dmesg | grep pinctrl-single
[ 0.926187] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
[ 0.939661] gpio-of-helper ocp:cape-universal: ready
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END

Tarmo Kuuse

unread,
Apr 6, 2020, 7:57:12 AM4/6/20
to BeagleBoard
Hi Ken,
I've seen similar behaviour on a subset of my BBB-s and BeagleCores - perhaps 1-3 out of ten just refused to shut down when powered via 5V supply input. Hasn't bothered me enough to dig in, but since it's specific to a few hardware specimens, it doesn't look like a software issue.

--
Kind regards,
Tarmo

KenUnix

unread,
Apr 6, 2020, 12:43:02 PM4/6/20
to BeagleBoard
Tarmo,

Thanks. That  would explain why another guy does not have this issue.

My thought is to do away with the USB -> P.C. cable and go with Ethernet.
That way BBB only has 1 power source. Removing USB power then
sudo shutdown -h now  works.

Ken

jonnymo

unread,
Apr 6, 2020, 12:46:49 PM4/6/20
to Beagle Board
Have you tried 'poweroff"?

Ex:
   sudo poweroff


Cheers,

Jon

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/836714c3-e041-4975-a2f1-8fb453442cfe%40googlegroups.com.

KenUnix

unread,
Apr 6, 2020, 12:53:58 PM4/6/20
to BeagleBoard
Jon,

Yes. Same result.

sudo poweroff

Re-boot. See my reply to Tarmo.

jonnymo

unread,
Apr 6, 2020, 1:12:17 PM4/6/20
to Beagle Board
Oh, you were using both the USB power and the Barrel Jack power?

Is this supported?

I always thought it was one or the other; not both.

Jon

--
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...@googlegroups.com.

KenUnix

unread,
Apr 6, 2020, 1:21:52 PM4/6/20
to BeagleBoard
Jon,

Originally when I got the BBB I only needed power from the USB cable.

However after adding a "cape" I needed more power. So the 5V
barrel power.

After looking over the schematic for the BBB and the TI 65217 power
management IC it appears it will take power from either. And if one
drops it will use the other.

That's why I am moving to an Ethernet connection.

Ken

Reply all
Reply to author
Forward
0 new messages