-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move bf/mavericks from legacy u-boot to FIT format #98
Comments
facebook-github-bot
pushed a commit
that referenced
this issue
Aug 17, 2019
Summary: Summart: As title Pull Request resolved: facebookexternal/openbmc.celestica#98 Test Plan: root@bmc-oob:~# cpld_ver.sh SMB_SYSCPLD: 3.2 SMB_PWRCPLD: 3.0 SCMCPLD: 3.1 FCMCPLD: 2.0 root@bmc-oob:~# Pass Reviewed By: joancaneus fbshipit-source-id: ccc71e6790
bbinxie
pushed a commit
to SW-CSA/openbmc
that referenced
this issue
Aug 29, 2019
Summary: FRU number always shows one digit even if there are two. Modify the display rule to correct it. Example: Before modify: 1 scm 2018-10-17 02:09:45 sensord ASSERT: Upper Non Critical threshold - raised - FRU: 12, num: 0x17 curr_val: 9024.00 RPM, thresh_val: 8500.00 RPM, snr: PSU2_FAN_SPEED 1 scm 2018-10-17 02:09:47 sensord ASSERT: Upper Non Critical threshold - raised - FRU: 13, num: 0x24 curr_val: 9024.00 RPM, thresh_val: 8500.00 RPM, snr: PSU3_FAN_SPEED 1 scm 2018-10-17 02:09:48 sensord ASSERT: Upper Non Critical threshold - raised - FRU: 14, num: 0x31 curr_val: 8992.00 RPM, thresh_val: 8500.00 RPM, snr: PSU4_FAN_SPEED After modify: 12 psu2 2018-10-17 02:09:45 sensord ASSERT: Upper Non Critical threshold - raised - FRU: 12, num: 0x17 curr_val: 9024.00 RPM, thresh_val: 8500.00 RPM, snr: PSU2_FAN_SPEED 13 psu3 2018-10-17 02:09:47 sensord ASSERT: Upper Non Critical threshold - raised - FRU: 13, num: 0x24 curr_val: 9024.00 RPM, thresh_val: 8500.00 RPM, snr: PSU3_FAN_SPEED 14 psu4 2018-10-17 02:09:48 sensord ASSERT: Upper Non Critical threshold - raised - FRU: 14, num: 0x31 curr_val: 8992.00 RPM, thresh_val: 8500.00 RPM, snr: PSU4_FAN_SPEED Pull Request resolved: facebookexternal/openbmc.accton#98 Test Plan: Test on minipack: pass Reviewed By: amithash fbshipit-source-id: a28726d45
facebook-github-bot
pushed a commit
that referenced
this issue
Oct 17, 2020
Summary: ELBERT: fpga_util: verify parition before programming Add some additional checks in fpga_util to prevent programming the wrong image type in the partition. Only enforcing partition 1, 2 at the moment. Testing: # Program the wrong image type root@bmc-oob:/tmp# sha1sum elbert_pim_pim16q_0x6v4.abin 0c4520e203726c6f0edd07afd10b348c314cd4e9 elbert_pim_pim16q_0x6v4.abin root@bmc-oob:/tmp# fpga_util.sh pim8ddm program elbert_pim_pim16q_0x6v4.abin Detected PIM Flash device. Selected partition pim8ddm to program. FPGA type in image, 1, does not match expected FPGA type, 2, for partition pim8ddm # Program the wrong image type root@bmc-oob:/tmp# sha1sum elbert_pim_pim8ddm_0x7v3.abin 1cb2ed7139d62aceaf3642bfe80b9d28430f9c11 elbert_pim_pim8ddm_0x7v3.abin root@bmc-oob:/tmp# fpga_util.sh pim16q program elbert_pim_pim8ddm_0x7v3.abin Detected PIM Flash device. Selected partition pim16q to program. FPGA type in image, 2, does not match expected FPGA type, 1, for partition pim16q #Test programming correct image root@bmc-oob:/tmp# fpga_util.sh pim16q program elbert_pim_pim16q_0x6v4.abin Detected PIM Flash device. Selected partition pim16q to program. /tmp/stripped_pim_image size 442733 < 33554432 (32MB) Resizing /tmp/stripped_pim_image by 33111699 bytes to /tmp/pim_image_32mb.bin flashrom v1.2 on Linux 5.6.19-elbert (armv7l) flashrom is free software, get the source code at https://flashrom.org Using region: "pim16q". Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Using default 2000kHz clock. Use 'spispeed' parameter to override. Found Micron flash chip "MT25QL256" (32768 kB, SPI) on linux_spi. === This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to [email protected] if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED. # Running just the verify command. This is not needed right after as program command also verifies. root@bmc-oob:/tmp# fpga_util.sh pim16q verify elbert_pim_pim16q_0x6v4.abin Detected PIM Flash device. Selected partition pim16q to program. /tmp/stripped_pim_image size 442733 < 33554432 (32MB) Resizing /tmp/stripped_pim_image by 33111699 bytes to /tmp/pim_image_32mb.bin flashrom v1.2 on Linux 5.6.19-elbert (armv7l) flashrom is free software, get the source code at https://flashrom.org Using region: "pim16q". Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Using default 2000kHz clock. Use 'spispeed' parameter to override. Found Micron flash chip "MT25QL256" (32768 kB, SPI) on linux_spi. === This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to [email protected] if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Verifying flash... VERIFIED. Pull Request resolved: facebookexternal/openbmc.arista#98 Reviewed By: benwei13 fbshipit-source-id: e2d400e982
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Almost all platforms are moved over to the FIT format. This transition should be harmless.
One known issue is the data partition is moved thus if upgrading from a pre-FIT image to a post-FIT image, one needs to first remount /mnt/data as read-only and then upgrade using flashcp/fw-util. After reboot the contents in /mnt/data might be lost. So, a backup might be required.
@simon-fan keeping you in the the loop :-)
The text was updated successfully, but these errors were encountered: