Forum Discussion
How to load intel RSU driver using "insmod"?
- 3 years ago
I will leave this here in case someone in the future needs to do this.
checkout this link for version compatibility:
Remote System Update Compatibility | Documentation | RocketBoards.org
What "worked" for me was to compile ATF 2.4.1, kernel 5.4.114 with RSU and u-boot 2021.01 plus the RSU libraries that needs to be put on the HPS, essentially the exact version they had in their manual.
ATF 2.6.1 crashed when booting into the kernel, with u-boot 2021.01, Intel does not really support older versions, so performance most likely will regress.
Side note:
Updating to u-boot 2021.01 from 2019 also meant that the L3 registers needed to be handled differently, the "sec_reg" driver that they introduced that can touch the L3 registers in the DTS file, only starts to exist from uboot 2021.04 and even then, it does not preserve the values of the RESERVED registers.
So for that I had to follow the suggestions at here and recompile ATF with the modification to its source code and add a script in u-boot to set them before booting the kernel.
Hello Sir
Instead of compiling it as a loadable module.
Could you try to set the flag to y instead of m.
"CONFIG_INTEL_STRATIX10_RSU=y"
This way you do not need to explicitly insmod the module on boot up.
Regards
Jingyang, Teh
- Scotty23 years ago
Occasional Contributor
Hi,
Yes I will be trying that, but unfortunately the build process and the deployment on our project is a fairly lengthy one and I am hoping to understand the process better or have a workaround until we can try to build this module into the kernel.
For that, I have locally also tried setting the config to an "m" in the "defconfig" file and trying to build the modules only with "make modules" but it does not generate a ".ko" file, hoping that I can then use this to load the module on the board. (this older document shows the process for the quartus prime version 19.3 and they do not build the module into the kernel).
Would you please advise on how to proceed and my other questions stated before?
Also would you kindly confirm that having this module loaded would automatically result in "/dev/mtd0" to be mounted on boot up?
If you can point me to other documents and guides on the process and the lower level details, I'd appreciate that as well!
Thank you!