Re: Boot stops at loader after build/install cycle

On Wed, 29 Mar 2023, bob prohaska wrote:

> On Wed, Mar 29, 2023 at 08:47:20AM +0000, Marcin Cieslak wrote:
>>
>> With three wires disconnected (nothing plugged in, only USB power and
>> the Ethernet), it works pretty unreliably. Sometimes it simply stops
>> working and simple power cycle does not bring FreeBSD back (unless
>> I connect the console and observe things). But maybe this is something
>> different. Of course now at my desk as I write this it boots every time :)
>> but not so in the field. (But that is probably something unrelated).
>>
>
> Does anything change if you use cu? cu -l cuaU0 -s 115200 for example.

No, but I just checked that everything looks fine outside of the
X session, just under the text console - vt(4), so no xterm

> If not maybe try  different hardware (cables, usb-serial adapters,
> power supplies and so on) with an eye to any changes of behavior.
> At this stage making the problem worse might be more useful than
> making it better. Disconnecting the serial-end ground might be
> worth a try. If the connection still works it suggests you have
> multiple grounds, which can cause trouble. I ended up lifting
> the ground on one of my serial connections. AFAIK both Ethernet
> and USB power supplies are floating, so multiple grounds are very
> unlikely. But something might be faulty.

The characters look too regular to me, just like a normal terminal
codes, not a line noise. I test the device now powered from the
same USB hub as the USB-serial converter. Rockchip needs 1500000 bps
console, pretty fest.

Also, uboot autoboot prompt never gets interrupted.

I also noticed that "resizewin" complains about not getting
information about the terminal upon login on the serial console
while being in the vt(4) text mode.

Looks like the bootloader tries to send/receives some terminal control
sequences and this fails, interupting the autoboot.

Marcin