Hi gays,
i am using beaglebone black with debian os
i am getting bellow shown error please tell me how to solve
systemd-analyze
Bootup is not yet finished. Please try again later.
systemd-analyze blame
Bootup is not yet finished. Please try again later.
Regards,
Raghavendra.b
--
For mor
This problem usually occurs. In my case, I waited for around 10 minutes and the
a window appeared with a message displaying boot time as 6 seconds.
And then it started back.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to t
HI
You've probably sorted this by now but in case anyone is interested, I have
updated the Beaglebone black files to REV C in Altium from REV B4.
On Friday, March 24, 2017 at 9:16:14 PM UTC+2, kleberr...@gmail.com wrote:
>
> Hi jam...@cladnetwork.com,
>
> I'm having same difficult as you to use
Thank you so much vishu your replay
But in my case it will not come out it is showing after 30min also same
error may be some service is continuously running i want to check
Regards,
Raghavendra.b
On 18-Oct-2018 3:43 PM, "Vishu Vashishtha"
wrote:
This problem usually occurs. In my case, I waite
The documentation for BBB says all over the place not to apply signals to
the GPIO pins until the BBB is powered up. What is the best way to know
when that occurs? Is there a signal or pin to watch for going high or low
that can be used to set up some simple logic to inhibit my input devices
On Thu, Oct 18, 2018 at 9:52 AM dwviel via BeagleBoard
wrote:
>
> The documentation for BBB says all over the place not to apply signals to the
> GPIO pins until the BBB is powered up. What is the best way to know when
> that occurs? Is there a signal or pin to watch for going high or low that
I have lost 4 BBB after simple power down. Debian 8, 4.1.30-ti-r69. Serial
console output now reveals:
rootfs contains a file system with errors, check forced.
rootfs:
Duplicate or bad block in use!
rootfs: Multiply-claimed
On Thu, Oct 18, 2018 at 2:08 PM wrote:
>
> I have lost 4 BBB after simple power down. Debian 8, 4.1.30-ti-r69. Serial
> console output now reveals:
>
> rootfs contains a file system with errors, check forced.
> rootfs:
> Dup
I know how to recover the file system but I do not want to happen it again
as manual intervention is required every time and this is not desired.
Is it that you are saying that the system is not designed to survive a
sudden unlisted power loss?
If 4 devices display exactly the same process (sy
On Thu, Oct 18, 2018 at 2:49 PM wrote:
>
> I know how to recover the file system but I do not want to happen it again as
> manual intervention is required every time and this is not desired.
>
> Is it that you are saying that the system is not designed to survive a sudden
> unlisted power loss?
Hello,
we checked that the power source from the other board and from the PC USB
are not connected in parallel.
See the picture below: we power BBB via the VDD_5V which is identical as
using an external 5V supply with the barrel jack. The PC USB puts power to
the USB_DC rail. The U2 TPS65217C i
11 matches
Mail list logo
