Hi All, My company is building a product that uses QSMP-1570 module from KaRo Electronics (https://www.karo-electronics.com/qsmp) and the modules itself is based on STM32MP1 processor from ST. They have application software that works on standard openSUSE 15.3 distro and Intel based board. They now want to build similar product based on the QSMP-1570 module and prefer to use openSUSE again so that the application does not need to get ported to a new Linux distro. The module itself comes with full Linux support using Yocto. My task now is to research the feasibility of spending the time to port openSUSE to the QSMP-1570 module. I have experience with Yocto/openEmbedded and embedded Linux, but have never used and build openSUSE before. Where should I start looking? What's your opinion - how hard would it be to make openSUSE work on this board? Thanks in advance. Best regards, Panayot
Hi Panayot, On 28/11/2022 13:21, Panayot Daskalov wrote:
Hi All,
My company is building a product that uses QSMP-1570 module from KaRo Electronics (https://www.karo-electronics.com/qsmp) and the modules itself is based on STM32MP1 processor from ST. They have application software that works on standard openSUSE 15.3 distro and Intel based board. They now want to build similar product based on the QSMP-1570 module and prefer to use openSUSE again so that the application does not need to get ported to a new Linux distro. The module itself comes with full Linux support using Yocto. My task now is to research the feasibility of spending the time to port openSUSE to the QSMP-1570 module.
I have experience with Yocto/openEmbedded and embedded Linux, but have never used and build openSUSE before. Where should I start looking? What's your opinion - how hard would it be to make openSUSE work on this board?
I'd advise you to start looking into any not-yet upstream patches in the kernel or U-Boot that would be needed. I hope there won't be any but who knows. I suppose using the Yocto recipes that will be easy to find out. After that you will need to have to find out how the boot works. Will U-Boot be part of the SD card image or will it be flashed in some SPI-Flash or something similar. Do you need to get any specific binary FW on the SD card to boot? Do you need to 'dd' U-boot a on specific offset on the SD card? Once you have an overview of that, we can start to have a look if we are missing any kernel config options. And in parallel set up a kiwi image to create a openSUSE Tumbleweed JeOS image (as a start). Regards, Matthias
Thanks in advance.
Best regards, Panayot
Hi Mathias, Thank you for the reply.
My company is building a product that uses QSMP-1570 module from KaRo Electronics (https://www.karo-electronics.com/qsmp) and the modules itself is based on STM32MP1 processor from ST. They have application software that works on standard openSUSE 15.3 distro and Intel based board. They now want to build similar product based on the QSMP-1570 module and prefer to use openSUSE again so that the application does not need to get ported to a new Linux distro. The module itself comes with full Linux support using Yocto. My task now is to research the feasibility of spending the time to port openSUSE to the QSMP-1570 module.
I have experience with Yocto/openEmbedded and embedded Linux, but have never used and build openSUSE before. Where should I start looking? What's your opinion - how hard would it be to make openSUSE work on this board?
I'd advise you to start looking into any not-yet upstream patches in the kernel or U-Boot that would be needed. I hope there won't be any but who knows. I suppose using the Yocto recipes that will be easy to find out. OK, clear on that. Will do.
After that you will need to have to find out how the boot works. Will U-Boot be part of the SD card image or will it be flashed in some SPI-Flash or something similar. Do you need to get any specific binary FW on the SD card to boot? Do you need to 'dd' U-boot a on specific offset on the SD card? OK, clear on that too. I'm waiting for an EVK of the module, then will get access to the additional docs and will be able to flash and test the whole thing.
Once you have an overview of that, we can start to have a look if we are missing any kernel config options. And in parallel set up a kiwi image to create a openSUSE Tumbleweed JeOS image (as a start).
Any advice on where would be the best place to start learning the openSUSE build basics and setting that up? Thanks. Best regards, Panayot
On 28/11/2022 20:08, Panayot Daskalov wrote:
Hi Mathias,
Thank you for the reply.
My company is building a product that uses QSMP-1570 module from KaRo Electronics (https://www.karo-electronics.com/qsmp) and the modules itself is based on STM32MP1 processor from ST. They have application software that works on standard openSUSE 15.3 distro and Intel based board. They now want to build similar product based on the QSMP-1570 module and prefer to use openSUSE again so that the application does not need to get ported to a new Linux distro. The module itself comes with full Linux support using Yocto. My task now is to research the feasibility of spending the time to port openSUSE to the QSMP-1570 module.
I have experience with Yocto/openEmbedded and embedded Linux, but have never used and build openSUSE before. Where should I start looking? What's your opinion - how hard would it be to make openSUSE work on this board?
I'd advise you to start looking into any not-yet upstream patches in the kernel or U-Boot that would be needed. I hope there won't be any but who knows. I suppose using the Yocto recipes that will be easy to find out. OK, clear on that. Will do.
After that you will need to have to find out how the boot works. Will U-Boot be part of the SD card image or will it be flashed in some SPI-Flash or something similar. Do you need to get any specific binary FW on the SD card to boot? Do you need to 'dd' U-boot a on specific offset on the SD card? OK, clear on that too. I'm waiting for an EVK of the module, then will get access to the additional docs and will be able to flash and test the whole thing.
Once you have an overview of that, we can start to have a look if we are missing any kernel config options. And in parallel set up a kiwi image to create a openSUSE Tumbleweed JeOS image (as a start).
Any advice on where would be the best place to start learning the openSUSE build basics and setting that up?
I'm not sure what you mean. Ar you familiar with OBS? If not you might want to have a look at [1] first. For the creation of a JeOS image you can branch the following package: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS There are a lot of files in there, but they get created from the *.in files, so only edit them if you want to enable your platform. You would also need to add it to _multibuild and probably disable other images as you don't want to wait on all the image to be build. You can also have a look at config.sh I suppose that all. I'm not aware that we have that documented somewhere in the wiki, so feel free to contribute to that with your findings. Matthias [1] https://openbuildservice.org/help/
Thanks.
Best regards,
Panayot
Hi Matthias, Thanks for the reply. I'm not familiar with OBS, so already started to read the docs. I have a ROCKPro64 board and wanted, as a next step, to test if I can build an image for it just to get the feel of it since I noticed that it is officially supported in openSUSE. I guess for that purpose, I just have to build this - https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:Rockchip/J... Thanks. Best regards, Panayot On 9.12.22 г. 11:08 ч., Matthias Brugger wrote:
I'm not sure what you mean. Ar you familiar with OBS? If not you might want to have a look at [1] first. For the creation of a JeOS image you can branch the following package: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS
There are a lot of files in there, but they get created from the *.in files, so only edit them if you want to enable your platform. You would also need to add it to _multibuild and probably disable other images as you don't want to wait on all the image to be build. You can also have a look at config.sh
I suppose that all. I'm not aware that we have that documented somewhere in the wiki, so feel free to contribute to that with your findings.
Matthias
[1] https://openbuildservice.org/help/
Thanks.
Best regards,
Panayot
Hi Panayot On 11/12/2022 16:51, Panayot Daskalov wrote:
Hi Matthias,
Thanks for the reply. I'm not familiar with OBS, so already started to read the docs. I have a ROCKPro64 board and wanted, as a next step, to test if I can build an image for it just to get the feel of it since I noticed that it is officially supported in openSUSE. I guess for that purpose, I just have to build this - https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:Rockchip/J...
Thanks.
The Contrib projects are a bit special in that sense. The contrib projects hold non-upstream packages that are needed to boot the board. Think of it like a old version of U-Boot where the patches got never upstream. These packages will live in for example: devel:ARM:Factory:Contrib:JeOS-newboard Then the JeOS repo [1] will have a file called contrib-repo-newboard.tgz which holds a text file with the name of the contrib project. In config.sh line 143 following [2] you can see how this will be used to add the project, and the packages in there to the Kiwi build. In short. Branching and changing https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS should be enough to build an image for the ROCKPro64. For the first steps enabeling you QSMP-1570 I would not care about the contrib project approach but just branch https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS and add any needed packages directly to the project. Hope I didn't create too much confusion. Regards, Matthias [1]https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS [2]https://build.opensuse.org/package/view_file/openSUSE:Factory:ARM/JeOS/confi...
Best regards,
Panayot
On 9.12.22 г. 11:08 ч., Matthias Brugger wrote:
I'm not sure what you mean. Ar you familiar with OBS? If not you might want to have a look at [1] first. For the creation of a JeOS image you can branch the following package: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS
There are a lot of files in there, but they get created from the *.in files, so only edit them if you want to enable your platform. You would also need to add it to _multibuild and probably disable other images as you don't want to wait on all the image to be build. You can also have a look at config.sh
I suppose that all. I'm not aware that we have that documented somewhere in the wiki, so feel free to contribute to that with your findings.
Matthias
[1] https://openbuildservice.org/help/
Thanks.
Best regards,
Panayot
Hi Matthias, Thank you for the information, it's very useful, certainly no noise there :). I will move forward with that and let you know how it goes. Best regards, Panayot On Mon, Dec 12, 2022 at 6:06 PM Matthias Brugger <mbrugger@suse.com> wrote:
Hi Panayot
On 11/12/2022 16:51, Panayot Daskalov wrote:
Hi Matthias,
Thanks for the reply. I'm not familiar with OBS, so already started to read the docs. I have a ROCKPro64 board and wanted, as a next step, to test if I can build an image for it just to get the feel of it since I noticed that it is officially supported in openSUSE. I guess for that purpose, I just have to build this -
https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:Rockchip/J... ?
Thanks.
The Contrib projects are a bit special in that sense. The contrib projects hold non-upstream packages that are needed to boot the board. Think of it like a old version of U-Boot where the patches got never upstream. These packages will live in for example: devel:ARM:Factory:Contrib:JeOS-newboard
Then the JeOS repo [1] will have a file called contrib-repo-newboard.tgz which holds a text file with the name of the contrib project. In config.sh line 143 following [2] you can see how this will be used to add the project, and the packages in there to the Kiwi build.
In short. Branching and changing https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS should be enough to build an image for the ROCKPro64.
For the first steps enabeling you QSMP-1570 I would not care about the contrib project approach but just branch https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS and add any needed packages directly to the project.
Hope I didn't create too much confusion.
Regards, Matthias
[1]https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS [2] https://build.opensuse.org/package/view_file/openSUSE:Factory:ARM/JeOS/confi...
Best regards,
Panayot
On 9.12.22 г. 11:08 ч., Matthias Brugger wrote:
I'm not sure what you mean. Ar you familiar with OBS? If not you might want to have a look at [1] first. For the creation of a JeOS image you can branch the following package: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS
There are a lot of files in there, but they get created from the *.in files, so only edit them if you want to enable your platform. You would also need to add it to _multibuild and probably disable other images as you don't want to wait on all the image to be build. You can also have a look at config.sh
I suppose that all. I'm not aware that we have that documented somewhere in the wiki, so feel free to contribute to that with your findings.
Matthias
[1] https://openbuildservice.org/help/
Thanks.
Best regards,
Panayot
participants (2)
-
Matthias Brugger -
Panayot Daskalov