platforms: adds support for arduino unoq by SuMere · Pull Request #46 · qualcomm-linux/qcom-ptool

SuMere · 2025-10-16T15:53:59Z

adds partitions.conf default file for qualcomm base image
adds partitions_user_16G.conf for arduino-specific images supporting userdata partition on 16GB emmc

lumag · 2025-10-16T17:04:42Z

platforms/qrb2210-unoq/emmc/partitions_user_16G.conf

Missing EOL

lumag · 2025-10-16T17:06:28Z

platforms/qrb2210-unoq/emmc-16GB/partitions.conf

@@ -0,0 +1,91 @@
+# Copyright (c) 2025 Qualcomm Innovation Center, Inc. All rights reserved.


Just to note, this file be ignored. If it's something that you want to use in your builds, it is easier to spawn the 'qrb2210-unoq-16GiB' device.

or create emmc-16GB and emmc-32GB folders, that looks 'nicer'

ndechesne · 2025-10-17T05:39:48Z

platforms/qrb2210-unoq/emmc/partitions.conf

you need to squash your changes in the previous commit. we merge 'clean' history only.

I'll mark the pr as draft, I'll be back in the office on monday

- adds partitions.conf default file for qualcomm base image - adds partitions_user_16G.conf for arduino-specific images supporting userdata partition on 16GB emmc Signed-off-by: Riccardo Mereu <r.mereu@arduino.cc>

Depends on qualcomm-linux/qcom-ptool#46

ndechesne · 2025-10-24T08:25:31Z

platforms/qrb2210-unoq/emmc/partitions.conf

+--partition --name=fsg --size=2048KB --type-guid=638FF8E2-22C9-E33B-8F5D-0E81686A68CB
+--partition --name=fsc --size=128KB --type-guid=57B90A16-22C9-E33B-8F5D-0E81686A68CB
+--partition --name=efi --size=524288KB --type-guid=C12A7328-F81F-11D2-BA4B-00A0C93EC93B --filename=efi.bin
+--partition --name=rootfs --size=10460284KB --type-guid=B921B045-1DF0-41C3-AF44-4C6F280D3FAE --filename=rootfs.img


what is the purpose of this conf file? the other one seems to be for the UnoQ with 16GB of eMMC. Is this one supposed to be for 32GB UnoQ?
Why is the userdata missing?
What do you expect to be different in the ptable between the 16GB and 32GB?

This is the default partition table; it's a copy of the rb1 conf. It is intended for use when building a qcom image. Our flash recipe will navigate to the folder with the configuration for 16GB eMMC and use it.
When everything is tested on the 32GB emmc I will add a PR for it.

ok, I would prefer to make it clear from the filename what it is, so :

platforms/qrb2210-unoq/emmc/partitions.conf

platforms/qrb2210-unoq/emmc-16GB/partitions.conf

could be:

platforms/qrb2210-unoq/emmc-16GB/partitions.conf

platforms/qrb2210-unoq/emmc-16GB-arduino/partitions.conf

and then we will add

platforms/qrb2210-unoq/emmc-32GB/partitions.conf

platforms/qrb2210-unoq/emmc-32GB-arduino/partitions.conf

the 'arduino' file is to be used with arduino images which have different ptable requirements than qcom reference imagses

What is qcom reference image for the UnoQ? What is the expected difference between 'Qualcomm' and 'Arduino' images?

I'd prefer something like:

platforms/qrb2210-unoq-16GB/emmc/

platforms/qrb2210-unoq-32GB/emmc/

etc.

Arduino image has an additional partition mounted on "/home/arduino" folder in the ptool perspective. This is meant to allow users to build a qcom debian image without the extra Arduino features and flash it on the UnoQ.
In fact the platforms/qrb2210-unoq/emmc/partitions.conf file is the same as the rb1. Since the ptool conf file is dependent on the target board we would like to prevent the user from modifying the flash recipe when building the qcom reference image.
On the arduino image perspective, there is no problem for us to change the recipe and point to the correct conf file, hence the extra folder for our partition table.

@lumag , it's really the Arduino image built/shipped by Arduino vs Qualcomm Linux images from QCOM (Debian/Yocto). So I don't think we should use 'unoq' in the filename to differenciate them.

lool · 2025-10-30T13:59:37Z

We discussed this PR today; some of the key questions were:

how do we structure the data in ptool; we already have cases where we have multiple scenarios for hardware platforms, e.g. emmc vs ufs boot on qcs615, so the arduino scenario of having a separate user partition could be handled similarly
which boards/platforms/scenarios do we want to carry in the ptool repo? currently it's exclusively qcom reference boards, but the unoq could be construed as such, perhaps not with the arduino userdata config
how would we maintain test the arduino version of the file?

It might be more practical for the Arduino specific scenario to leave outside of this repo so that there is a review step for new qcom-ptool changes from time to time, and Arduino can opt when to take the ptool changes, and adjust their files.

A completely different approach from this PR would be to design a way to express the changes that Arduino wants to make to the partitions. For instance, expressing that the partitions should be the same as for RB1, but with a userdata partition added. It could be in ptool or around ptool, for instance a script generating or post-processing partitions.conf files, or an include mechanism.

ricardosalveti · 2025-10-30T21:56:44Z

which boards/platforms/scenarios do we want to carry in the ptool repo? currently it's exclusively qcom reference boards, but the unoq could be construed as such, perhaps not with the arduino userdata config

The same question will follow for other targets we might add via 3rdparty, and I believe if we merge a partition table specific for the arduino image (and not the board), then we should support variants.

Generic images (from other generic distros) will probably want to consume the generic partition file for the target, and not the one for the arduino image.

Depends on qualcomm-linux/qcom-ptool#46

lool · 2026-01-24T17:58:01Z

platforms/qrb2210-unoq/emmc-16GB/partitions.conf

+--partition --name=fsc --size=128KB --type-guid=57B90A16-22C9-E33B-8F5D-0E81686A68CB
+--partition --name=efi --size=524288KB --type-guid=C12A7328-F81F-11D2-BA4B-00A0C93EC93B --filename=efi.bin
+--partition --name=rootfs --size=10460284KB --type-guid=B921B045-1DF0-41C3-AF44-4C6F280D3FAE --filename=rootfs.img
+--partition --name=userdata --size=2145728KB --type-guid=B921B045-1DF0-41C3-AF44-4C6F280D3FAE --filename=userdata.img


GUID seems wrong for the userdata partition, it should be 0fc63daf-8483-4772-8e79-3d69d8477de4, or perhaps 933ac7e1-2eb4-4f13-b844-0e14e2aef915 if we are ok to mount this as /home instead of /home/arduino. See https://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/ for a table explaining the GUIDs and how systemd will interpret them.

lool · 2026-01-28T19:05:12Z

I've submitted #65 that might be taking over this PR

lumag · 2026-01-29T12:23:02Z

#65 has been merged, closing this.

SuMere requested review from lumag, ndechesne, sbanerjee-quic and vkraleti as code owners October 16, 2025 15:54

lumag reviewed Oct 16, 2025

View reviewed changes

ndechesne reviewed Oct 17, 2025

View reviewed changes

SuMere force-pushed the feature/unoq-support branch from 38486dc to 939f9cc Compare October 20, 2025 06:52

SuMere marked this pull request as draft October 20, 2025 06:54

SuMere force-pushed the feature/unoq-support branch from 939f9cc to f395e9d Compare October 20, 2025 06:56

platforms: adds support for arduino unoq

609f63c

- adds partitions.conf default file for qualcomm base image - adds partitions_user_16G.conf for arduino-specific images supporting userdata partition on 16GB emmc Signed-off-by: Riccardo Mereu <r.mereu@arduino.cc>

SuMere force-pushed the feature/unoq-support branch from 41fe251 to 609f63c Compare October 20, 2025 07:13

SuMere marked this pull request as ready for review October 20, 2025 07:14

facchinm added a commit to arduino/arduino-deb-images that referenced this pull request Oct 20, 2025

unoq: integrate with flash debos recipe

1640713

Depends on qualcomm-linux/qcom-ptool#46

ndechesne reviewed Oct 24, 2025

View reviewed changes

SuMere marked this pull request as draft October 30, 2025 13:43

facchinm added a commit to arduino/arduino-deb-images that referenced this pull request Dec 16, 2025

unoq: integrate with flash debos recipe

d43d895

Depends on qualcomm-linux/qcom-ptool#46

lool reviewed Jan 24, 2026

View reviewed changes

lool mentioned this pull request Jan 28, 2026

platforms: add support for Arduino UNO Q #65

Merged

lumag closed this Jan 29, 2026

		@@ -0,0 +1,91 @@
		# Copyright (c) 2025 Qualcomm Innovation Center, Inc. All rights reserved.

Conversation

SuMere commented Oct 16, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

lool commented Oct 30, 2025

Uh oh!

ricardosalveti commented Oct 30, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

lool commented Jan 28, 2026

Uh oh!

lumag commented Jan 29, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Comments