flashy-c093182

flashy: support fby35

Summary: Add flash procedure for Yosemite v3.5

Test Plan:
[[email protected] ~/local/openbmc/tools/flashy] ./build.sh && ./build_dev.sh && go test
2022/09/30 08:59:50 Running command '/home/garnermic/local/openbmc/tools/flashy/scripts/calculate_test_coverage.sh' with 30s timeout
2022/09/30 08:59:54 stdout: 95.3
2022/09/30 08:59:54 Command '/home/garnermic/local/openbmc/tools/flashy/scripts/calculate_test_coverage.sh' exited with code 0 after 3.733883287s
PASS
ok      github.com/facebook/openbmc/tools/flashy    3.741s

Reviewed By: williamspatrick

fbshipit-source-id: c1fbe7852481933430b6724109f6b8c54127e9d8

flashy-0536abf

spec: add flash layout for Bletchley and Greatlakes

Summary:
We didn't specify the requirements on the flash layout
for Bletchley and Greatlakes.  Add it now.

Test Plan: Doc only.

Reviewed By: garnermic

fbshipit-source-id: 3b8254cf2ac475b7f5b07c965fda278787b4c94e

FB OpenBMC QEMU 0.6.3

psu-update: Add support to upgrade ORv3 Delta PSU

Summary:
This adds firmware upgrade script to support ORv3
Delta PSU.

Test Plan:
Check current firmware version
```
root@bmc-oob:~# rackmoncli data --dev-addr 224 --reg-addr 48
Device Address: 0xe0
Device Type: orv3_psu
CRC Errors: 0
timeouts: 0
Misc Errors: 0
Baudrate: 19200
Mode: active
  PSU FW Revision<0x0030> : "31322041"
```
Perform firmware upgrade:
```
root@bmc-oob:~# psu-update-delta-orv3.py --addr 224
./V3_DFLASH_REV_01_00_01_04.dflash
statusfile None
Send get seed
Got seed: 0e8dbde8
Send key
Send key successful.
Erasing flash...
Erase successful
Sending <128 byte segment @ 0x00000000>
[0.08%] Sending chunk 1 of 1211...
Sending <52224 byte segment @ 0x00000400>
[33.77%] Sending chunk 409 of 1211...
Sending <256 byte segment @ 0x0000d300>
[33.94%] Sending chunk 411 of 1211...
Sending <102144 byte segment @ 0x000c0000>
[99.83%] Sending chunk 1209 of 1211...
Sending <256 byte segment @ 0x000e6f00>
[100.00%] Sending chunk 1211 of 1211...
Verifying program...
Verify of flash successful!
Activating Image...
Activate successful!
```
Check firmware version is updated:
```
root@bmc-oob:~# rackmoncli data --dev-addr 224 --reg-addr 48
Device Address: 0xe0
Device Type: orv3_psu
CRC Errors: 0
timeouts: 0
Misc Errors: 0
Baudrate: 19200
Mode: active
  PSU FW Revision<0x0030> : "31252035"
```

Reviewed By: GoldenBug

fbshipit-source-id: 2defa23faffec89c4bceceb4f8ccb5dd32b5b92b

flashy-5fe6ada

grandteton: Add flashy support

Summary:
As title, add capability in flashy to support GT.
TBD, once we are in DVT, we need to convert this
to flash.FlashCpVboot.

Test Plan: Build ephemeral fbpkg and test out oobgrader. Ensure it upgrades flash1.

Reviewed By: kawmarco

fbshipit-source-id: ba1c4404eb5b34cdfba3b5647ef1ec4d104e6380

flashy-95a150a

detect missing/broken flash chips on non-vboot

Summary:
If the U-Boot environment (env MTD partition) is inaccessible and flash0 is
missing too, it's a good indication that something serious is amiss with the
SPI chips.  Return a  broken flash chip error code in this case, instead of
an unsafe to reboot error.

(For example an A-SPEED/Linux driver bug may hide the env partition on the
primary chip invisible if the secondary chip is inaccessible.)

Test Plan:
Build & unit test:

```
0 ~/local/openbmc/tools/flashy $ ./build.sh && ./build_dev.sh && go test ./...
ok      github.com/facebook/openbmc/tools/flashy        (cached)
ok      github.com/facebook/openbmc/tools/flashy/checks_and_remediations/common (cached)
ok      github.com/facebook/openbmc/tools/flashy/checks_and_remediations/galaxy100      (cached)
ok      github.com/facebook/openbmc/tools/flashy/checks_and_remediations/wedge100       (cached)
ok      github.com/facebook/openbmc/tools/flashy/checks_and_remediations/yamp   (cached)
?       github.com/facebook/openbmc/tools/flashy/flash_procedure        [no test files]
ok      github.com/facebook/openbmc/tools/flashy/install        (cached)
ok      github.com/facebook/openbmc/tools/flashy/lib/fileutils  (cached)
ok      github.com/facebook/openbmc/tools/flashy/lib/flash      (cached)
ok      github.com/facebook/openbmc/tools/flashy/lib/flash/flashcp      (cached)
ok      github.com/facebook/openbmc/tools/flashy/lib/flash/flashutils   (cached)
ok      github.com/facebook/openbmc/tools/flashy/lib/flash/flashutils/devices   (cached)
?       github.com/facebook/openbmc/tools/flashy/lib/logger     [no test files]
ok      github.com/facebook/openbmc/tools/flashy/lib/step       (cached)
ok      github.com/facebook/openbmc/tools/flashy/lib/utils      (cached)
ok      github.com/facebook/openbmc/tools/flashy/lib/validate   (cached)
ok      github.com/facebook/openbmc/tools/flashy/lib/validate/image     (cached)
ok      github.com/facebook/openbmc/tools/flashy/lib/validate/partition (cached)
?       github.com/facebook/openbmc/tools/flashy/tests  [no test files]
?       github.com/facebook/openbmc/tools/flashy/utilities      [no test files]
0 ~/local/openbmc/tools/flashy $ echo $?
0
```

Reviewed By: kawmarco

fbshipit-source-id: 355a7d01ce55f4994ca76693b360592206651b6a

flashy-5aec440

Support running run_flashy_remote.sh in release build

Summary:
When we release a prebuilt flashy to OSS, we need to point to the right flashy binary, since we are no longer building flashy from the project root.

Add a new flag `path-to-flashy` that allows pointing to the release path of flashy.

In the github release, make sure we have the right folder structure

```
. flashy
|---scripts
     |--- run_flashy.sh
     |--- run_flashy_remote.sh
```

Test Plan:
# Running in release folder, path to flashy provided

```
release/scripts $ ./run_flashy_remote.sh --device mtd:flash0 --host fboss9310996-oob.snc1 --dry-run --imagepath ../flash-wedge40 --path-to-flashy ../flashy
Running in dry-run mode
Running a remote upgrade on 'fboss9310996-oob.snc1' with image '/data/users/linhaolee/openbmc/tools/flashy/release/flash-wedge40'
Continue (y/n)?y
path-to-flashy provided: /data/users/linhaolee/openbmc/tools/flashy/release/flashy
Making installation directories on OpenBMC...
Copying flashy...
Copying image...
Copying upgrade script...
Finished dry run
```

# Running in scripts folder, path to flashy not provided
```
openbmc/tools/flashy/scripts $ ./run_flashy_remote.sh --device mtd:flash0 --host fboss9310996-oob.snc1 --dry-run --imagepath ../release/flash-wedge40
Running in dry-run mode
Running a remote upgrade on 'fboss9310996-oob.snc1' with image '/data/users/linhaolee/openbmc/tools/flashy/release/flash-wedge40'
Continue (y/n)?y
path-to-flashy not provided, building flashy...
Making installation directories on OpenBMC...
Copying flashy...
Copying image...
Copying upgrade script...
Finished dry run
```

Reviewed By: deathowl

fbshipit-source-id: 27bcbaf8606864c2b768455ff2a9ee15e2dbfaa3

flashy-a74952f

grandteton: Remove debug print

Summary: As title

Test Plan: Build GT

Reviewed By: williamspatrick

fbshipit-source-id: d574907c045bc81be97fa99addbb2af7cdb7c99c

Facebook OpenBMC e2294ff5d31d

Add Attest-util to Yv3.5

Summary: Enable attest-util on Yv3.5 for testing purposes.

Test Plan: build with Yv3.5

Reviewed By: williamspatrick

fbshipit-source-id: 93ee53ca95922ff9ef2571c135a229a52c9bd042

Facebook OpenBMC v2021.49.0

v2021.49.0