Arm Community
Arm Community
  • Site
  • User
  • Site
  • Search
  • User
  • Groups
    • Research Collaboration and Enablement
    • DesignStart
    • Education Hub
    • Innovation
    • Open Source Software and Platforms
  • Forums
    • AI and ML forum
    • Architectures and Processors forum
    • Arm Development Platforms forum
    • Arm Development Studio forum
    • Arm Virtual Hardware forum
    • Automotive forum
    • Compilers and Libraries forum
    • Graphics, Gaming, and VR forum
    • High Performance Computing (HPC) forum
    • Infrastructure Solutions forum
    • Internet of Things (IoT) forum
    • Keil forum
    • Morello Forum
    • Operating Systems forum
    • SoC Design and Simulation forum
    • 中文社区论区
  • Blogs
    • AI and ML blog
    • Announcements
    • Architectures and Processors blog
    • Automotive blog
    • Graphics, Gaming, and VR blog
    • High Performance Computing (HPC) blog
    • Infrastructure Solutions blog
    • Innovation blog
    • Internet of Things (IoT) blog
    • Operating Systems blog
    • Research Articles
    • SoC Design and Simulation blog
    • Tools, Software and IDEs blog
    • 中文社区博客
  • Support
    • Arm Support Services
    • Documentation
    • Downloads
    • Training
    • Arm Approved program
    • Arm Design Reviews
  • Community Help
  • More
  • Cancel
Open Source Software and Platforms
Open Source Software and Platforms
Wiki Notice: Potential damage to N1SDP boards if using latest firmware release
  • Help
  • Jump...
  • Cancel
  • About this wiki
  • Supported platforms
  • Obtaining support
  • +Arm Reference Platforms deliverables
  • -A-class platforms
    • +Juno
    • +FVPs
    • +System Guidance for Infrastructure (SGI)
    • +System Guidance for Mobile (SGM)
    • Corstone-500
    • Cortex-A5 DesignStart
    • -Neoverse N1 SDP
      • N1SDP FAQ
      • N1SDP Getting Started Guide
      • Notice regarding N1SDP power supply unit (PSU)
      • Notice: Potential damage to N1SDP boards if using latest firmware release
      • Notice: Remote reset switch impact on reset host
    • Neoverse Reference Designs
    • +Legacy platforms
  • +M-class platforms
  • +R-class platforms
  • +FPGA prototyping boards
  • +Open source software

Notice: Potential damage to N1SDP boards if using latest firmware release

This document serves as notice of an issue with the N1SDP PMIC that may potentially lead to system hangs or even damage to components under certain conditions.

In late 2019, Arm identified a number of N1SDP boards experiencing system hangs during 12-hour stress-ng soak tests. Unstable voltage rails were found to be the root cause, and the issue was resolved by tuning the PMIC with a new binary image. All N1SDP boards leaving the factory since the middle of November 2019 have shipped with this new PMIC image.

Unfortunately, we cannot simply update all N1SDP boards with this new PMIC image as boards previously running the original PMIC image are susceptible to component damage if upgraded and will require an RMA to be repaired.

The consequences of this are that:
1) boards built before November 2019 should use the original PMIC image to avoid component damage;
2) boards built after November 2019 should use the new PMIC image to avoid system hangs.

Following PMIC binaries should be used for boards with relevant serial numbers:

MBPMIC: pms_0V85.bin        ;MB PMIC for boards before 36253xxx
MBPMIC: 300k_8c2.bin        ;MB PMIC for boards after 36253xxx

Arm is developing a solution whereby the MCC firmware automatically detects both:
• whether this is a board built before or after November 2019, based on serial number;
• which PMIC image is in use.

If a mismatch is detected, a warning message is printed in the console recommending the user to switch PMIC image.

While the next N1SDP release will include the solution described above, unfortunately it was not ready in time for the N1SDP-2020.03.26 release, which only ships with the original PMIC image. This means users with boards built after November 2019 will actually be overwriting the new PMIC image with the original PMIC image when upgrading to the N1SDP-2020.03.26 release, which may lead to system hangs.

In the interim, we have provided instructions below on how to manually update your N1SDP to use the correct PMIC image.


1. Download the attached n1sdp_new_pmic.zip archive

2. Connect a USB-B cable between your host PC and your N1SDP’s DBG USB port

3. Power cycle your N1SDP

4. On the MCC console, press Enter to halt the boot process if prompted

5. On the MCC console, enter the following command to mount your N1SDP’s motherboard storage as a removable drive on your host PC:

Cmd> usb_on

6. On your host PC, extract the n1sdp-new-pmic.zip archive onto your N1SDP’s mounted motherboard storage, overwriting existing files:

$ unzip -o n1sdp-new-pmic.zip -d /path/to/N1SDP

7. On your host PC, ensure the writes have been flushed:

$ sync

8. Power cycle your N1SDP

Following are some example console outputs after updating your N1SDP.


Board built after November 2019 (serial numbers after 36253xxx), using original PMIC image (pms_0V85.bin):

Powering up system...

Switching on ATXPSU...
Switching on main power...

Reading Board File \MB\HBI0316A\io_v123f.txt

Warning: the PMIC image for this board must be updated.
Please edit io_vxxxf.txt stored in \MB\HBI0316A\ and
Set MBPMIC: to 300k_8c2.bin or later

Press any key to continue... <-- CLI waits here


Board built before November 2019 (serial numbers before 36253xxx), using new PMIC image (300k_8c2.bin):

Powering up system...

Switching on ATXPSU...
Switching on main power...

Reading Board File \MB\HBI0316A\io_v123f.txt

Warning: the PMIC image for this board must be updated.
Please edit io_vxxxf.txt stored in \MB\HBI0316A\ and
set MBPMIC: to pms_0V85.bin

Press any key to continue... <-- CLI waits here


Note that a new flag has also been added to config.txt to skip the “Press any key to continue…” step:

PMIC_FORCE: TRUE ;TRUE = Display warning, False = Display warning and wait for key press

It is advised that your follow the guidance provided by the MCC firmware to update the PMIC firmware rather than toggling this PMIC_FORCE flag to skip the warning, unless explicitly recommended to by Arm.

  • Share
  • History
  • More
  • Cancel
Related
Recommended