Mysterious ANSI codes prevent booting
My UP2 boots into the BIOS password prompt. This prompt is then filled with *'s, as if text is being typed into it rapidly. I can't type anything into it, and pressing ENTER has no effect. CTRL-ALT-DEL reboots the UP2, so my keyboard works.
I think this behaviour started after I connected the 2xUSB+debug UART cable. However removing the cable has had no effect.
When the problem first occured, the system did boot into the GRUB prompt of the installed Ubuntu Linux and also into the GRUB prompt. From seeing what was being typed at that prompt I noted that these are various ANSI escape codes and ENTER's. However after I managed to get into the BIOS one time the random typing probably changed some settings as the UP2 now doesn't boot into GRUB anymore, not from the installed Ubuntu Linux nor from an USB boot drive.
My theory is that the system thinks that the debug UART is activated and as it is by default configured as ANSI terminal it keeps sending ANSI escape codes to clear the screen etc. But somehow these end up in the keyboard buffer rather than on the debug UART. When I could still boot into GRUB and with the debug UART connected I did not receive anything from the UP2 but I could type commands from my serial terminal 'into' the UP2.
What I've tried:
- Starting without anything except HDMI cable connected
- Starting without any cable (except power) connected
- Starting with HDMI and USB keyboard connected and tapping F7 (for UEFI menu) or DEL (for BIOS menu)
- Starting with HDMI and debug UART and sending F7 in the terminal window
- Disconnecting power and battery and letting it stay that way overnight
- Flashing various BIOS versions (1.8, 2.1, 3.3, 4.0), with MiniPro TL866A programmer, 1.8V converter and SOIC8 debug clip direct on the W25Q128FW flash chip
- Flashing BIOS dump from my other UP2 with 'Console Redirection' disabled in the Serial Port Console Redirection menu
All this either leads to a non-starting UP2 (some BIOS flashes) or to the situation staying as it was.
Can anybody from AAEON please advise what I could do to resolve this?
- Any idea what could have caused this?
- Since some serial debug console seems to be active, how can I connect to this?
- Is this solvable by flashing a BIOS?
- Is there a way to reset everything to default?
- What is the expected behaviour of connecting the debug UART?
Anybody else with debug UART experience please chime in.
I'm a little bit hesitant to experiment with my other UP2, as I don't want to loose them both...
- All Categories
- 105 Announcements & News
- 57 Product News - New Product/Product Change Notice/ End-of-life
- 186 Welcome Developers!
- 55 Unboxing & Project Sharing
- 50 Tech Updates
- 693 UP Products
- 11 UP 7000
- 1 UP Squared i12
- 10 UP Xtreme i12
- 11 UP Squared Pro 7000
- 1 UP Element i12 Edge
- 19 UP Squared V2
- 59 UP 4000
- 24 UP Xtreme i11
- 35 UP Squared 6000
- 60 UP Squared Pro
- 143 UP Xtreme
- 837 UP Squared
- 1.4K UP Board
- 89 UP Core Plus
- 222 UP Core
- 3 UP Xtreme Lite
- 44 UP AI Edge
- 216 Starter Kits & Peripheral