| commit | 59ee25470d3db13ec7a5c7553d1725719b18c3c6 | [log] [tgz] |
|---|---|---|
| author | Marco Chen <marcochen@chromium.org> | Thu Jul 19 05:08:41 2018 |
| committer | chrome-bot <chrome-bot@chromium.org> | Thu Aug 30 21:41:54 2018 |
| tree | 3906282577dcf452d05ec81a35b07a7350686976 | |
| parent | d79b53336e2650d41d5abd88e23e8e301b53a405 [diff] |
factory_tty: always re-create frecon for detecting new input device. There is an issue about frecon created in initramfs stage can't detect new input device by udev monitor after switch_root is called. For devices with default keyboard, at least we have one input device detected in the initramfs stage so the control of factory shim menu can be performed. For detachable projects, keyboard from hammer will be recognized after rootfs is ready because it is supported by kernel module and loaded by udev. But this default behavior hits the issue above and causes that there is not default input device for controlling factory shim menu. Chromebase / Chromebox / Tablet projects would be affected as well if users try to plug in USB keyboard after booting to the menu. The workaround is to re-create frecon again so force frecon to re-start udev monitor. As the result, new input device can be monitored. The downside is that if debug console is enabled then it would be closed due to the re-creation of frecon and currently factory_shim_service.sh doesn't re-open it yet. BUG=b:65606804 TEST=manually test in the DUT. Change-Id: Ib84d417f0d0ebde90f27070feeab244b9f6dadee Reviewed-on: https://chromium-review.googlesource.com/1143057 Commit-Ready: Marco Chen <marcochen@chromium.org> Tested-by: Marco Chen <marcochen@chromium.org> Reviewed-by: Hung-Te Lin <hungte@chromium.org> Reviewed-by: Chun-Tsen Kuo <chuntsen@chromium.org>
This folder contains the major scripts for the “Chrome OS factory shim”. The shim is used for installing a Chrome OS image (kernel, rootfs and firmware) to a device. It's also known as “(factory) install shim”, “RMA shim”, or “Reset shim”.
The factory shim is designed to allow operators removing USB stick once it's booted, so the boot process is slightly different. The shim relies on initramfs technology to bootstrap and load all contents into memory, then start an upstart service to display the menu.
Inside chroot, do:
build_packages --board $BOARD build_image --board $BOARD factory_install
The output disk image is in ~/trunk/src/build/images/$BOARD/latest/factory_install_shim.bin.
If you have local changes in src/platform/factory_installer, please remember to do
cros_workon --board $BOARD start factory_installer emerge-$BOARD factory_installer
If you have local changes in src/platform/initramfs, please remember to do
cros_workon --board $BOARD start chromeos-initramfs
There‘s no need to emerge chromeos-initramfs because it’s always re-built in build_image stage.
The factory shims were signed in a special way for security reasons. It needs to boot with “developer switch turned on” and “boot in recovery mode”.
If you have a signed factory shim, follow the steps to boot:
Esc-F3-Power)Ctrl-D to request turn on developer switch, and ENTER to confirm.If you boot factory shim in developer mode (Ctrl-U), few functions won't work, for example recovering TPM.
Factory shims do not provide shells by default for security reason. If you can still see virtual terminal consoles, try VT0, VT1, VT2, VT3 - there are lots of debug messages there.
If you do need a shell to debug, add cros_debug to kernel command line. You can do this in build_image:
build_image --board $BOARD --boot_args cros_debug factory_install
For an existing image, you can use make_dev_ssd.sh to change kernel command line easily:
# inside chroot cd ~/trunk/src/platform/vboot_reference/scripts/image_signing ./make_dev_ssd.sh -i $PATH_TO_IMAGE_OR_USB_DEVICE \ --partitions 2 --recovery --edit_config
This will bring an editor to allow editing command line.
Note make_dev_ssd.sh is also available on all Chrome OS image (even factory shim) - try /usr/share/vboot/bin/make_dev_ssd.sh.
If you boot a factory shim with cros_debug, then you should have one shell in VT2 or VT3. Moreover, if you can enter the menu, ‘S’ will give you the full shell.
The frecon (or frecon-lite) provides text-based console. If you can't see anything on screen, redirect the console to another device, for example Servo consoles so you can check why frecon failed. To do this, add console=ttyS0,115200n8 to kernel command line (use the make_dev_ssd.sh or add --boot_args as explained in previous section). Some devices may need different TTY name for example ttyS1. Please check the care-and-feed doc of your device.
If the menu or frecon will die and adding cros_debug does not help, you probably want to attach serial console (for example SuzyQ) and get everything except factory shim UI (menu) there. To do that:
Open the /usr/sbin/factory_tty.sh and find the TTY_CONSOLE= line. If it already has valid serial console (for example ttyS0), move to step 3.
TTY_CONSOLE and build image.Edit the make.conf in board overlay, to find or add one setting (assume serial console is ttyS0):
TTY_CONSOLE="ttyS0"
Then,then re-build the factory_installer package and factory shim:
emerge-$BOARD factory_installer build_image --board $BOARD factory_install
Mount the rootfs and rename /etc/init/console-ttyS0.conf to something that does not start as console:
# First enable RW for rootfs. Assume the USB is in /dev/sdX. cd ~/trunk/src/platform/vboot_reference/scripts/image_signing sudo ./make_dev_ssd.sh -i /dev/sdX --recovery \ --remove_rootfs_verification --partitions 2 # Mount (assume your shim is in /dev/sdX) sudo mount /dev/sdX /media cd /media/etc/init sudo mv console-ttyS0.confg debug-ttyS0.conf cd - # To leave /media folder so we can unmount. sudo umount /media