What steps are necessary for custom PolarFire board?

[zmcginty-thinkOrbital]

I will be working on a custom board using a PolarFire SOC (MPFS160T-FCVG784I) which I don't think is used on any dev-boards, so I can't really just use any existing config for another dev-board (such as icicle or discovery-kit). What I want to know is what changes do I need to make to get Linux up and running on a custom board?
Should I start with a dev-board such as the icicle, or disco-kit and modify it to work on ours?
What pieces need to be modified? (Reference-Design, HSS, Device-Tree, Pin-Mux, are there any others I'm forgetting here?)
Any advice is greatly appreciated here!

[rockoguido]

Hi. Yes my personal recommendation is to leverage an existing deployment, perhaps the Icicle Kit as a baseline for your porting effort. To get Linux up and running a few pointers should help… * If you memory configuration differs from the kit you chose you’ll need to reflect that change in the MSS Configuration. * Just to get Linux running you may want to disable some devices in the device tree to simplify things for starters * Devices can still stay enabled in the MSS Configurator * With any new board DDR training and init is a big deal. This is outside the scope of Linux, be prepared to spend some time here * Of course part of your porting effort involves the HSS, so some effort there but should not be too much, all isolated in the .config file I am sure there is more and you’ll go bottom up. Libero based design followed by the HSS. Regards, Dave Campanella Principal Embedded Solutions Engineer / FAE Microchip Technology Inc. 165 Technology Dr Irvine, CA 92618 +1 925 989 0569 (mobile) +1 760 304 0172 (office) ***@***.******@***.***> For any Technical related concerns, kindly you can create web ticket at http://www.microchip.com/support For Technical Training please go to Microchip University at https://secure.microchip.com/mu There are several paths to take for Microchip support: * Self-paced learning – see the Developer Help Site<http://microchipdeveloper.com/> * Knowledge Base - here<http://www.microchip.com/support/hottopics.aspx> * Community Forums - help<http://www.microchip.com/forums/> with a lot of information from experts. From: zmcginty-thinkOrbital ***@***.***> Sent: Wednesday, April 30, 2025 10:42 AM To: polarfire-soc/polarfire-soc-documentation ***@***.***> Cc: Subscribed ***@***.***> Subject: [PolarFire-SoC] What steps are necessary for custom PolarFire board? (Discussion #541) EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe I will be working on a custom board using a PolarFire SOC (MPFS160T-FCVG784I) which I don't think is used on any dev-boards, so I can't really just use any existing config for another dev-board (such as icicle or discovery-kit). What I want to know is what changes do I need to make to get Linux up and running on a custom board? Should I start with a dev-board such as the icicle, or disco-kit and modify it to work on ours? What pieces need to be modified? (Reference-Design, HSS, Device-Tree, Pin-Mux, are there any others I'm forgetting here?) Any advice is greatly appreciated here! — Reply to this email directly, view it on GitHub<#541>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AXJPF676LMHYRNWPQNHT2M324EDNRAVCNFSM6AAAAAB4GHRV3KVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZYGI3DMNJXGA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>

[zmcginty-thinkOrbital]

Thank you for confirming this! Could you explain more about what I might need to change in the HSS?

[rockoguido]

to keep things simple assuming you are starting with the Icicle Kit as a baseline, HSS comes targeting the Icicle Kit, In envm-wrapper/Makefile you would need to change the DIE and PACKAGE settings to match your target
also you need a .config targeting the Icicle Kit in the root directory. then the XML file you reference has to be the one you generated from the MSS Configurator, this config file would come from the Icicle Kit directory and is called def_config by default
you can attempt a build within Softconsole at this point.

[xiaogu-arch]

@zmcginty-thinkOrbital @rockoguido Hello, I also encountered some similar issues during the transplantation process. Could you please take a look? Thank you very much!This is the website where I describe the problem. https://github.com/orgs/polarfire-soc/discussions/560