News:

LATEST RELEASE:  FPP 8.4 - Download from here - https://github.com/FalconChristmas/fpp/releases/tag/8.4

+-+-

+-User

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?

+-Site Stats

Members
Total Members: 16779
Latest: BWP
New This Month: 42
New This Week: 15
New Today: 3
Stats
Total Posts: 134926
Total Topics: 16874
Most Online Today: 186
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 3
Guests: 169
Total: 172

BBB shutting off by itself

Started by stanward, September 21, 2016, 01:42:57 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

stanward

Hello,

I have a BBB hooked up to 6 P10 panels.  Everything between xLights and the BBB/P10 works fine.  Randomly, the BBB will just shut off, usually after a few minutes of being powered up.

Sometimes the BBB will shut off even when there is nothing being displayed on the P10 panels.  I hooked up my oscilloscope to the 5V power supply and don't notice any noise or voltage dips (unable to capture the point where the BBB shuts off).

I am powering the BBB through the barrel connector, I previously was powering it through the Cape with the same problem.  I am using the 5V power supply from DIYLEDexpress (came as a bundle).

I updated FPP from v 1.5 to v 1.8 thinking that would fix the problem, but it didn't.

JonB256

Quote from: stanward on September 21, 2016, 01:42:57 AM
Hello,

I have a BBB hooked up to 6 P10 panels.  Everything between xLights and the BBB/P10 works fine.  Randomly, the BBB will just shut off, usually after a few minutes of being powered up.

Sometimes the BBB will shut off even when there is nothing being displayed on the P10 panels.  I hooked up my oscilloscope to the 5V power supply and don't notice any noise or voltage dips (unable to capture the point where the BBB shuts off).

I am powering the BBB through the barrel connector, I previously was powering it through the Cape with the same problem.  I am using the 5V power supply from DIYLEDexpress (came as a bundle).

I updated FPP from v 1.5 to v 1.8 thinking that would fix the problem, but it didn't.

Didn't your earlier post make a pretty conclusive decision about the 5vdc power supply?

QuoteI have another question, why does the 5v power supply (DIYLEDEXPRESS) cause the BBB to just randomly shut off?

If I feed 5v from my bench power supply, the BBB runs fine.

I am feeding 5v to the terminal block on the Octoscroller Cape.
Long time Falcon, FPP and xLights user

stanward

I couldn't find anything wrong with the o scope.  Thought the cheap pwr supply would've been noisy.


Sent from my iPhone using Tapatalk

stanward

I was wrong!  I left the BBB running off of my BK Precision Linear Regulated power supply (at 5.0Vdc) and the BBB shuts itself off,  Nothing was connected to the BBB, other than the SD card and the USB thumb drive (that is empty).

PS, I am powering the BBB through the barrel connector.

Can anyone please help me?

stanward

I did more testing tonight.

It turns out if I plug in the micro SD card containing FPP in it, the BBB will randomly shut off.  I ran the BBB for an hour without shutting off (without the micro SD card plugged in).

Here is the debug/flash-eMMC.log if anyone can help me:
-----------------------------
debug copying: [/dev/mmcblk0] -> [/dev/mmcblk1]
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
mmcblk1boot0 179:16   0     1M  1 disk
mmcblk1boot1 179:24   0     1M  1 disk
mmcblk0      179:0    0  14.9G  0 disk
├─mmcblk0p1  179:1    0    96M  0 part /boot/uboot
└─mmcblk0p2  179:2    0   1.7G  0 part /
mmcblk1      179:8    0   3.7G  0 disk
├─mmcblk1p1  179:9    0    96M  0 part
└─mmcblk1p2  179:10   0   3.6G  0 part
-----------------------------
update-initramfs: Generating /boot/initrd.img-3.8.13-bone50
`/boot/initrd.img-3.8.13-bone50' -> `/boot/uboot/initrd.img'
Image Name:   initramfs
Created:      Thu May 15 12:19:18 2014
Image Type:   ARM Linux RAMDisk Image (uncompressed)
Data Size:    2679506 Bytes = 2616.71 kB = 2.56 MB
Load Address: 00000000
Entry Point:  00000000
16+0 records in
16+0 records out
16777216 bytes (17 MB) copied, 3.50912 s, 4.8 MB/s
Checking that no-one is using this disk right now ...
OK

Disk /dev/mmcblk1: 119808 cylinders, 4 heads, 16 sectors/track

sfdisk: ERROR: sector 3069053405 does not have an msdos signature
/dev/mmcblk1: unrecognized partition table type
Old situation:
No partitions found
New situation:
Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start   End    MiB    #blocks   Id  System
/dev/mmcblk1p1   *     1     96     96      98304    e  W95 FAT16 (LBA)
/dev/mmcblk1p2        97   3743   3647    3734528   83  Linux
/dev/mmcblk1p3         0      -      0          0    0  Empty
/dev/mmcblk1p4         0      -      0          0    0  Empty
Successfully wrote the new partition table

Re-reading the partition table ...

If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
/dev/mmcblk1p1   *        2048      198655       98304    e  W95 FAT16 (LBA)
mkfs.vfat 3.0.13 (30 Jun 2012)
mke2fs 1.42.5 (29-Jul-2012)
Discarding device blocks:   4096/933632528384/933632             done                           
Filesystem label=rootfs
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
233856 inodes, 933632 blocks
46681 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=956301312
29 block groups
32768 blocks per group, 32768 fragments per group
8064 inodes per group
Superblock backups stored on blocks:
   32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables:  0/29 1/29 2/29 3/29 4/29 5/29 6/29 7/29 8/29 9/2910/2911/2912/2913/2914/2915/2916/2917/2918/2919/2920/2921/2922/2923/2924/2925/2926/2927/2928/29     done                           
Writing inode tables:  0/29 1/29 2/29 3/29 4/29 5/29 6/29 7/29 8/29 9/2910/2911/2912/2913/2914/2915/2916/2917/2918/2919/2920/2921/2922/2923/2924/2925/2926/2927/2928/29     done                           
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information:  0/29 1/29 2/29 3/29 4/29 5/29 6/29 7/29 8/29 9/2910/2911/2912/2913/2914/2915/2916/2917/2918/2919/2920/2921/2922/2923/2924/2925/2926/2927/2928/29     done

`/boot/uboot/MLO' -> `/tmp/boot/MLO'
`/boot/uboot/u-boot.img' -> `/tmp/boot/u-boot.img'
sending incremental file list
./
ID.txt
LICENSE.txt
README.htm
README.md
SOC.sh
START.htm
autorun.inf
initrd.img
uEnv.txt
uInitrd
zImage
App/
App/README
App/beaglebone-getting-started.zip

JonB256

There are multiple file access errors in your logs.

If you have another class 10 SD card handy, do a fresh install of FPP.
Long time Falcon, FPP and xLights user

stanward

Quote from: JonB256 on September 22, 2016, 05:04:56 AM
There are multiple file access errors in your logs.

If you have another class 10 SD card handy, do a fresh install of FPP.

Thank you, will try that!


Sent from my iPhone using Tapatalk

stanward

Hello JonB,

I just found out I made a terrible mistake.  I setup my P10 matrix using the eMMC method and not the SD method.  But I left the SD card in the BBB as well as a USB flash drive too.

The 16GB SD card was only formatted to have 96MB of space, where the other 15.xGB space is unallocated.  I think this is the reason why the BBB would just shut off.  I am unable to delete the partitions on this SD card to create one large 16GB partition.

Is anyone able to help me with this SD card problem?  I am in Disk Management, but unable to modify the partitions.

rlemery

Have you tried reformatting the SD card  using the SD card format tool from the SD card association?   I know that fpp will put files in the card In  Linux and Windows cannot read it.

Sent from my SM-G920V using Tapatalk

728 lor channels
5492 pixels

JonB256

The Drive Management software that comes with Windows 10 doesn't see or show all the partitions on a Debian partitioning.
There may be third party software that will handle it. My solution has always be "scorched earth" when an SD card acts funny. I just use the SD Formatter utility mentioned in the install instructions, and wipe the SD completely.

I've found it easier to start over from a fresh download than to spend hours troubleshooting. That's just me.
Long time Falcon, FPP and xLights user

stanward

Quote from: JonB256 on September 24, 2016, 10:38:55 AM
The Drive Management software that comes with Windows 10 doesn't see or show all the partitions on a Debian partitioning.
There may be third party software that will handle it. My solution has always be "scorched earth" when an SD card acts funny. I just use the SD Formatter utility mentioned in the install instructions, and wipe the SD completely.

I've found it easier to start over from a fresh download than to spend hours troubleshooting. That's just me.

Yes, agreed, to start with a fresh install.

I did just that, a fresh install with another SD card and while I had the P10 matrix running for a few hours, I was trying to troubleshoot the SD card.

I will download the utility.


Thank you!!


Sent from my iPhone using Tapatalk

Support FPP

+- Recent Topics

Adding additional PSU to R2R F16v5 by Poporacer
Today at 04:47:12 PM

FPP connecting to network issue by Santacarl
Today at 04:20:33 PM

K32 & Soundblaster by Ryeguy
Today at 12:02:18 PM

GE Insane Cane Bars not following submodel in Xlights. by Suikoden
Today at 09:16:20 AM

can't find FPP after a router change by mrgimmeone
Today at 06:20:46 AM

How can I play one random playlist, selected from a playlist of playlists? by jedimasta
Today at 12:41:13 AM

Red status on E131 by TheMinionHouse
December 11, 2024, 06:34:56 PM

Length of pigtail before pixels by Todd
December 11, 2024, 01:51:00 PM

Disabling the 'built-in' e131 server? by sirwesley
December 11, 2024, 09:03:55 AM

picap V1 by darylc
December 10, 2024, 09:44:17 PM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod