FAFTSetup: the device you inserted does not contain Chrome OS

[Martin Yan]

Hi Faft team,

 

As I run

~/trunk/src/scripts $ /usr/bin/test_that --board=reef 192.168.1.3 firmware_FAFTSetup

 

And test is stuck at,

15:37:50 INFO | autoserv| Check test image is on USB stick and run recovery boot

15:38:36 INFO | autoserv| usb dev is /dev/sdb

15:38:36 INFO | autoserv| Will execute on servo host: mount -o ro /dev/sdb3 /tmp/usbcheck.ECWM

15:38:36 INFO | autoserv| Will execute on servo host: umount -l /dev/sdb3

15:38:36 INFO | autoserv| Will execute on servo host: sync

15:38:37 INFO | autoserv| Will execute on servo host: rm -rf /tmp/usbcheck.ECWM

15:38:37 INFO | autoserv| -[ModeSwitcher]-[ start reboot_to_mode('rec', None, True) ]-

15:38:38 INFO | autoserv| Blocking sync for /dev/mmcblk1

15:38:38 INFO | autoserv| Setting power_state to off

15:38:58 INFO | autoserv| Setting power_state to rec

15:39:10 INFO | autoserv| -[FAFT]-[ start wait_for_client ]---

15:42:12 INFO | autoserv| -[FAFT]-[ system did not respond to ping ]

 

Because DUT doesn’t boot up and displays “the device you inserted does not contain Chrome OS”.

I download “chromiumos_test_image.bin” from https://www.google.com/chromeos/partner/, and flash it into USB drive via,

cros flash usb:// ~/trunk/src/build/images/reef/latest/ chromiumos_test_image.bin

 

Did I miss anything?

[Tom Wai-Hong Tam (談偉航)]

To clarify the issue, you may plug the USB disk directly to the DUT, and then

press Esc + F3 + Power to see if it boots into the USB?

--
You received this message because you are subscribed to the Google Groups "faft users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+unsubscribe@chromium.org.

[Martin Yan]

  

If USB drive is plugged into DUT directly, and press “Esc + F3” + Power button after booting up, it also displays,

“the device you inserted does not contain Chrome OS”.

 

One helpful info, as USB drive is connected to DUT, and during normal boot, in “OS verification is OFF” windows, I press “ctrl + U”, able to boot from USB drive (enable dev_boot_usb=1 previously), I used this sequence to update test OS.

 

And, I can see “OEM”,  “ROOT-A” and “STATE” folders in USB drive as it is plugged into test server, but “ROOT-A” is showed “Unable to access”. not sure this info is helpful...

To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+...@chromium.org.

[Tom Wai-Hong Tam (談偉航)]

Looks like it is caused by mismatched key between firmware and the USB image. Did you run:

 $ /usr/share/vboot/bin/make_dev_firmware.sh
 $ /usr/share/vboot/bin/make_dev_ssd.sh

in the Chrome OS shell?

It changes the key in the firmware to a dev one, which matches the USB image's.

To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+unsubscribe@chromium.org.

[Martin Yan]

Tried to run /usr/share/vboot/bin/make_dev_firmware.sh, but it displays,

 

Disabling system software write protection status...

make_dev_firmware.sh: ERROR: Write protection is still enabled.  Please verify that hardware write protection is disabled.

 

Scope the EC_FLASH_WP_ODL signal, it is high, i.e. flash chip in not in protected state. How “make_dev_firmware.sh” detects flash protection status?

Secondly, should this utility run on DUT shell or Test server via Servo board?

To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+...@chromium.org.

[Tom Wai-Hong Tam (談偉航)]

On Wed, Nov 29, 2017 at 1:36 PM, Martin Yan <Marti...@microchip.com> wrote:

Tried to run /usr/share/vboot/bin/make_dev_firmware.sh, but it displays,

 

Disabling system software write protection status...

make_dev_firmware.sh: ERROR: Write protection is still enabled.  Please verify that hardware write protection is disabled.

 

Scope the EC_FLASH_WP_ODL signal, it is high, i.e. flash chip in not in protected state. How “make_dev_firmware.sh” detects flash protection status?

Could you try "make_dev_firmware.sh --debug" which shows more debug message to see what failed?

 

Secondly, should this utility run on DUT shell or Test server via Servo board?

Should run on DUT.

 

To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+unsubscribe@chromium.org.

[Martin Yan]

I am new to FAFT test.

 

After bring up DUT,

1: alt+ctrl+T: enter developer shell

2: crosh> shell

3: chronos@localhost /$ /usr/share/vboot/bin/make_dev_firmware.sh --debug

 

DEBUG: Prerequisite check

DEBUG: Checking software write protection status

Disabling system software write protection status…

make_dev_firmware.sh: ERROR: Failed to disable WP. Disagnose Message: usr/share/vboot/bin/make_dev_firmware.sh: 358: flashrom: not found

To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+...@chromium.org.

[Sparry, Icarus W]

First thing to suggest is to become ‘root’ rather than ‘chronos’ to manipulate the DUT.

[Martin Yan]

Hi Icarus and Tom,

 

Yes, apply “alt+ctrl+F2” to enter “root”,

/usr/share/vboot/bin/make_dev_firmware.sh

Can be executed properly, and “successfully changed firmware to developer Keys”.

 

After key in the firmware is changed to match USB / OS image’s, “the device you inserted does not contain Chrome OS” is not showed up again, then firmware_FAFTSetup can be passed.

 

Thanks your help!