firmware_ECWriteProtect.dev: System not in expected dev mode.

[Martin Yan]

As I tested EC firmware_ECWriteProtect.dev case,

$ /usr/bin/test_that --board=$BOARD 192.168.1.4 firmware_ECWriteProtect.dev

The error messages are as followings,

 

//////

Expected 'wpsw_boot' value '1' but got '0'

System not in expected dev mode. Reboot into it.

...

ENTER pressed to switch to dev mode

...

<class 'socket.error'>([Errno 111] Connection refused)

Retrying in 1.040710 seconds...

<class 'httplib.BadStatusLine'>('')

Retrying in 0.688418 seconds...

<class 'httplib.BadStatusLine'>('')

Retrying in 0.615248 seconds...

<class 'httplib.BadStatusLine'>('')

Retrying in 0.769904 seconds...

<class 'httplib.BadStatusLine'>('')

Retrying in 0.913363 seconds...

<class 'httplib.BadStatusLine'>('')

Retrying in 0.581843 seconds...

<class 'httplib.BadStatusLine'>('')

Retrying in 0.845973 seconds...

….

autoserv| raise BadStatusLine(line)

autoserv| BadStatusLine: ''

/////

 

Attach “test_that_results_dAwDR_.zip” for more debug information. Testing “firmware_DevMode.ec_wp” case has pretty same error messages.

 

Is BIOS or OS not supporting dev mode? After bios & OS are built, “image.dev.bin” bios is used to programmed onto board, and using “./build_image –board=${BOARD} –noenable_rootfs_verificaiton test” to build test OS, does “–noenable_rootfs_verificaiton” parameter cause this problem?

 

And is there any utility to verify if BIOS & OS are good for FAFT test?

 

Regards,

Martin

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

+faft-users@ for informative

On Thu, Mar 29, 2018 at 1:05 PM, Tom Wai-Hong Tam (談偉航) <wai...@google.com> wrote:

On Thu, Mar 29, 2018 at 11:36 AM, <Marti...@microchip.com> wrote:

Oops, sorry, I forwarded the wrong one.

This is the one I hit the problem.

Regards,

Martin

Looks like it failed to switch between normal mode and dev mode.

You can try to do it manually: press Esc+F3+Power, wait a warning screen, press Ctrl-D, wait a confirm screen, press Enter. Does it work?

Also does the firmware_DevMode pass?

 

Attach “test_that_results_dAwDR_.zip” for more debug information. Testing “firmware_DevMode.ec_wp” case has pretty same error messages.

 

Is BIOS or OS not supporting dev mode? After bios & OS are built, “image.dev.bin” bios is used to programmed onto board, and using “./build_image –board=${BOARD} –noenable_rootfs_verificaiton test” to build test OS, does “–noenable_rootfs_verificaiton” parameter cause this problem?

The "noenable_rootfs_verification" should work. You can verify it manually, like the above instructions.

 

And is there any utility to verify if BIOS & OS are good for FAFT test?

Suggest to run firmware_FAFTSetup first, it verifies some basic functionalities. 

 

Regards,

Martin

--
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]

You can try to do it manually: press Esc+F3+Power, wait a warning screen, press Ctrl-D, wait a confirm screen, press Enter. Does it work?

[Martin]: it works as soon as it is in normal mode, then system can enter dev mode with Ctrl-D pressing;

 

Also does the firmware_DevMode pass?

[Martin]: no, it fails either;

 

Suggest to run firmware_FAFTSetup first, it verifies some basic functionalities.

[Martin]: FAFTSetup is passed;

 

After dev mode -> normal mode -> dev mode sequence, this test case “firmware_ECWriteProtect.dev” is passed!! Interesting Thanks!

+faft-users@ for informative

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