faft users

thanks your response, Jeremy. per review test_that.debug, here is the difference: 1: not working

oops, attached "test_that.txt" error messages. the error line in firmware_ECBattery is

faft-users, For b/153456306 there's a question about excluding a specific CTS subtest from a run.

Hi Kevin, I did repo sync. But still same issue. I could not see /usr/local/telemetry in DUT. could

We have tried to run FAFT from different host using below command. But i am facing some error during

Looks like it failed at talking to the STM32 (the MCU of servo micro) UART. You may check why /dev/

migrating to v4 would likely be best On Tuesday, July 31, 2018 at 12:44:04 PM UTC-7, Martin Yan wrote

Good, add -d option to get more debug info, thanks! On Friday, June 22, 2018 at 11:20:14 AM UTC-4,

Got it, thanks! On Monday, May 14, 2018 at 12:13:13 PM UTC-4, Wai-Hong Tam wrote: On Thu, May 10,

Hi Tom, Per your recommendation, mchp can build chromeos-firmwareupdate package, and as it is copied

Thanks your time to explain in details. Look like AP doesn't get correct batt info from EC via

You can try to do it manually: press Esc+F3+Power, wait a warning screen, press Ctrl-D, wait a

Hi Tom, Yes, you are right, I disabled automount / automount-open features from “dconf Editor”, “

It was merged, I can see it in ToT. From: faft-...@chromium.org [mailto:faft-...@chromium.org] On

Hi Icarus and Tom, Yes, apply “alt+ctrl+F2” to enter “root”, /usr/share/vboot/bin/make_dev_firmware.

Hi Tom, Thanks your help! Servo board comm. is good now, I can move to next step... Regards, Martin

Test..

Most likely kernel related, I would search and see if other have seen the same problem using your

I encountered this issue, too. However, I used "release-R49-7834.B" branch to test, it can

Thanks. Is running FAFT with more that one servo board connected at the same time a supported

Hi Danny, OK, Thanks for the update. I will continue to debug as best I can. It is hard to capture

The joys of code not written to be debugged! Best guess - a “mosys” problem. Log into the device

I just ran firmware_FAFTSetup test on ToT and firmware branch, both passed on another veyron type

I'm happy to announce that this is now fixed. On Mon, Apr 20, 2015 at 2:41 PM, Shawn N <shawnn

Is anyone running FAFT against a 3.18 kernel? Basic question – this is x86_64 in case it matters. Am

FAFT team, I have found that I have some failing hardware and it is unrelated to R39 or anything else

Dear FAFT-Group, I do firmware_ConsecutiveBoot test, and I met a un-known issue…. Why testing show

Shawn, Good point about the external display. Marc On Fri, Aug 8, 2014 at 9:26 AM, Shawn N <shawnn

FAFTSetup test passed on my old repo. I have created fresh repo and followed the steps mentioned on

Hi All, We have completed phase 1 of FAFT infrastructure improvements. What this means for you: - if