PolarFire SoC GitHub Discussions Guidelines

[hughbreslin]

Thanks for taking the time to check out GitHub discussions for PolarFire SoC!

Before creating a discussion post please take the time to read over the following guidelines:

1. Search through the existing discussion topics to make sure this query hasn't already been answered

2. We may already have training material that covers the question you are going to ask, please take the time to review the following resources before asking a question:

   • Training videos
   • Webinar series
   • Documentation

3. We will only be able to provide support to anything related to the contents of the PolarFire SoC organization

   • For example if your request is for support in regards to a custom board we will not be able to support this
   • We have a separate GitHub Discussions set up for Mi-V Soft CPUs

4. Please let us know what board and version of deliverables you are using and what you are attempting to do

   • For example "Trying to boot FreeRTOS using HSS version 2022.05, MPFS HAL version 1.8.254 on an Icicle Kit"
   • For example "Trying to load a custom driver for fabric IP on an Icicle Kit using Yocto release 2022.05 and HSS 2022.05"

5. Categorize your post appropriately

   • For example if your end application is embedded software but you are having an issue with the HSS, please categorize your post in the "HSS and U-Boot" category and not under "Bare Metal Embedded Software"

6. Don't respond to discussions via email

   • Email responses aren't parsed or displayed very well and can revel personal information such as email addresses and phone numbers

7. Preview your post / response before posting and verify the formatting and styling are accurate

   • If you are unsure about how to format your post correctly, check out this Markdown guide

8. Please ask one question per discussion post

   • This makes it easier to search for existing questions based on the title of discussions
   • If you ask a question and it is answered and then have a second question, please make a new discussion post

9. Please copy and paste error messages into your discussion post instead of screenshots.

   • This will make it easier for someone to search for the same error message if it occurs for them.

Recommended discussion post format:

Title

< A useful title to describe this post >

Description of issue

< Please give an outline of the issue you are facing, including, when / where the problem has occurred. What (if any) differences there are between your case and our reference. What are you trying to achieve. >

Steps to reproduce

< Please include the steps you took to reach this point and how this issue could be reproduced. >

Logs and errors

< Include copies of any logs or error messages you can share. >

Additional or background information

< Any additional information that may be useful in re-creating or debugging this. >