New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 655176 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Oct 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 0
Type: Bug

Blocked on:
issue 651860



Sign in to add a comment

Update first batch of 300 servo v4 prior to deployment

Project Member Reported by kevcheng@chromium.org, Oct 12 2016

Issue description

The current fw on the v4 have a bug where they don't power on the uServo upon init (but servod will turn it on).  This will cause problems during deployment since the first deployment will fail since none of the uServo controls will be available, rerunning deployment will work but ideally we should update the fw on these v4.

I'm working on an update script and will give instructions on how to update the v4 in a bit.  Once that's available, Haowei and team can start updating the v4s (all that's needed is a linux box and a standard usb micro cable).
 
Labels: -Pri-3 Pri-0

Comment 2 by autumn@chromium.org, Oct 12 2016

Confirmed with Kevin that this is NOT an issue with the next batch, only the first 300 are impacted. 
A bug for lab team has been created and can be tracked here
https://b.corp.google.com/issues/32109624
 
Attached is tarball of all the files needed to run the script. 

1. Set it up, just d/l the tarball onto a linux box that has python (#tar -xvf update_v4_fw.tar.gz).
2. Connect up the servo v4 to the linux box via standard usb type A micro cable.
3. Run the script (#./update_v4.py)
4. repeat steps #2 and #3

Make sure only one servo v4 is attached to the linux box when running the script.

Let me know if you have any problems with the script or errors you hit.
update_v4_fw.tar.gz
73.4 KB Download
Note that ./fw_update.py can take an -s serialno argument
Cc: kevcheng@chromium.org
Owner: haoweiw@chromium.org
Thanks Nick for that note, it might be simpler to just do them serially to avoid pulling the wrong servo when programming multiple in parallel.

Assigning to Haowei now.

Haowei, please close out this bug when all 300 are flashed, thank you!

Comment 7 by dchan@chromium.org, Oct 26 2016

Labels: servov4
Project Member

Comment 8 by sheriffbot@chromium.org, Oct 29 2016

Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable?

If a fix is in active development, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 9 by haoweiw@google.com, Oct 30 2016

Status: Fixed (was: Assigned)
All 300 Servo V4 has been updated. 

Sign in to add a comment