Robert,
I'm using a 5V/2A power supply, and have tried the same process with the
identical setup across multiple boards (same power supply, same uSD). I'm
not seeing the power supply dip below 5V at all during the flashing
process; it's steady at 5.20V throughout the process. Maybe that's on th
On Wed, Feb 3, 2016 at 2:49 PM, wrote:
> Thanks for your help.
>
> I'm now trying to re-flash the eMMC, but every time I try, after a few
> minutes all LEDs blink in what looks like an error pattern (two short blinks
> then pause). I tried using the same uSD to flash another board, which worked
>
Thanks for your help.
I'm now trying to re-flash the eMMC, but every time I try, after a few
minutes all LEDs blink in what looks like an error pattern (two short
blinks then pause). I tried using the same uSD to flash another board,
which worked fine.
Attached is the serial output from the fa
That would be my guess. Yes, making it read only will help. Or attach a
battery that can keep it powered up until shutdown can occur, and have the
kernel shut it down. A lot of discussion in the forum on this topic.
Gerald
On Wed, Feb 3, 2016 at 1:17 PM, wrote:
> So you are implying this is a
So you are implying this is a corrupt filesystem issue?
I won't be able to guarantee power failures won't occur during runtime for
this application, but if this is a corruption issue I don't have a problem
making the root partition read-only.
Chris
On Wednesday, February 3, 2016 at 2:09:20 PM
I tried it again without microhdmi / usb keyboard connected, and got intact
messages from U-Boot.
On Wednesday, February 3, 2016 at 2:04:00 PM UTC-5, cjac...@gmail.com wrote:
>
> Also the u-boot messages seem mangled. Not sure what would cause that --
> if it's a problem with my serial connectio
Shutdown Linux before powering down.
Gerald
On Wed, Feb 3, 2016 at 1:04 PM, wrote:
> Also the u-boot messages seem mangled. Not sure what would cause that --
> if it's a problem with my serial connection I would expect to see further
> mangling once the kernel starts to boot, and on the initram
Also the u-boot messages seem mangled. Not sure what would cause that -- if
it's a problem with my serial connection I would expect to see further
mangling once the kernel starts to boot, and on the initramfs prompt, but
that all seems intact.
On Wednesday, February 3, 2016 at 2:01:09 PM UTC-5,
