[Debian-lego-team] Bug#877297: Bug#877297: libnxt: usb:v03EBp* too inclusive, leads to false positive matches

Nicolas Schodet schodet-reportbug at ni.fr.eu.org
Thu Sep 30 08:32:46 BST 2021

* Petter Reinholdtsen <pere at hungry.com> [2021-09-29 17:13]:
> [Nicolas Schodet]
> > Actually, the NXT in flash mode is using the Atmel ROM bootloader which
> > uses 0x03eb:0x6124. Every devices using the SAM-BA bootloader on Atmel
> > AT91SAM chips will use this identifiers.
> Right.  So perhaps this patch is a better one?

> pere at minerva:~/src/lego-mindstorm/libnxt-git$ git diff
> diff --git a/debian/libnxt.metainfo.xml b/debian/libnxt.metainfo.xml
> index fd9f148..9593780 100644
> --- a/debian/libnxt.metainfo.xml
> +++ b/debian/libnxt.metainfo.xml
> @@ -12,6 +12,6 @@ intelligent brick at a relatively low level.
>    </description>
>    <provides>
>      <modalias>usb:v0694p0002d*</modalias>
> -    <modalias>usb:v03EBp*</modalias>
> +    <modalias>usb:v03EBp6124d*</modalias>
>    </provides>
>  </component>

I think so, could you check you have the same product id on your NXT?

> Alternative, perhaps that USB ID should not be listed in the appstream
> metainfo file?  I suspect I got the ID from one of the udev entries in
> one of the other lego related packages:

What are the consequences when several packages use the same identifier?

I do not think there will be many SAM-BA in the wild, unless you are
working with a SAM91 dev board. What would be the consequence for
someone working with such a board?


More information about the Debian-lego-team mailing list