Page History

...

   Image is flashed to SD card before inserting to RPI board.   

Command to flash the image

...

$ sudo dd if=<path to ImageName.rpi-sdimg> of=<path to SD card space> bs=4M

The SD card is then inserted to the Raspberry Pi board and booted to check for containers created.

...

Plugin needs to be enabled before proceeding with firmware update.

RPi - Board :

• Flash the image supported for with FirmwareControl plugin feature in the RPI board and verify the 2 partitions(ex. mmcblk0p1, mmcblk0p2) present under dev folder (use command fdisk -l)
• Execute curl request for firmware update. One more memory partition is created and device auto reboots.  During first time execution, firmware update request creates one more partition in memory(mmcblk0p3) and auto reboots to update partition table. This happens only on the first request, further requests will not result in board reboot before firmware update.
• Once device boots up verify there are 3 partitions in /dev (ex. mmcblk0p1, mmcblk0p2, mmcblk0p3) (use command fdisk -l) .
• Execute curl request for firmware update for second time.
• Image tar file will be downloaded to a file in /tmp folder (ex. ImageTemp). Verify image is downloaded to /tmp
• Reboot RPI board once firmware update process is completed manually using reboot -f command.
• Once board boots up verify the current image version ( cat /version.txt)
•  Verify the version of booted image which shows the downloaded image version

Conclusion

Please find the summary on firmware upgrade explained above

...

User Access Considerations

Limitations: 

•  Auto reboot after firmware update is not happening currently. User has to reboot manually after completion of firmware update.
•  RPI board will reboot before firmware update only for the first request for updating memory partition table, and user has to give request command once again for firmware update. This occurs only for the first request after board boot up.

<Briefly describe and graphically depict as appropriate the equipment, communications, and network configuration of the system in a way that a non-technical user can understand>

• Accessing the System

<Provide detailed information and describe the procedures necessary to access the system. If applicable, include how to get a user ID and log on to the system, as well as the actions a user must take to change and/or reset a password.>

• System Work Flow

<Describe how system flow is happening mentioning checkpoints which can be verified during flow to ensure system is working as expected>

• Exiting the System

<Mention the validation artifacts that are essential to ensure the functionality is working as expected. Also any limitation while closing the validation process>

Executing System

Describe the specific system function or feature in detail and depict graphically by including screen prints and descriptive narrative as appropriate. Ensure each screen print is captioned and has an associated tag providing appropriate alternative text

Follow the above for sub feature / use cases

Troubleshooting

• Error Messages

<Identify the error messages that a user may receive and the likely cause(s) and/or possible corrective actions for the error>

• Special Considerations

<If applicable, describe any special circumstances, actions, exceptions, etc., that should be considered for troubleshooting.>

Support

...

Contact

...

Organization

...

Phone

...

Email

...

Role

...

<Contact Name>

...

<Organization>

...

<Phone>

...

<Email>

...