package/imx-uuu: new host package
PATCH v2 1/2 package/imx-uuu: new host package
NXP deprecated the old mfgtools code. It has been replaced by the Universal Update Utility (uuu), also called mfgtools v3.0 although the releases are named v1.x.yy, which is quite confusing.
This new tool actually resides in the same repository in the master branch whereas the old one is now in a 'linux' branch.
The new tool uuu is a completely different tool than the old mfgtools. This also means, that existing mfgtools scripts will not work with the uuu tool.
Therefore, it has been decided to create a new package imx-uuu [1].
Note, that uuu uses git to define a version string GIT_VERSION. It does so even when building from a source tarball (automatically generated by github). The problem is, that git provides the version information of Buildroot and mfgtools uses this version information to do a runtime check to detect outdated command list scripts.
To fix this, we overwrite gen_ver.sh with something that simply prints a define for GIT_VERSION with the uuu version string (preceeded by "lib", as done in the original gen_ver.sh).
[1] http://patchwork.ozlabs.org/patch/1112411/
---
v2:
* fix version string generation (missing 'uuu_')
--- DEVELOPERS | 1 + package/Config.in.host | 1 + package/imx-uuu/Config.in.host | 12 ++++++++++++ package/imx-uuu/imx-uuu.hash | 3 +++ package/imx-uuu/imx-uuu.mk | 24 ++++++++++++++++++++++++ 5 files changed, 41 insertions(+) create mode 100644 package/imx-uuu/Config.in.host create mode 100644 package/imx-uuu/imx-uuu.hash create mode 100644 package/imx-uuu/imx-uuu.mk
DEVELOPERS +1 -0
@@ -1306,6 +1306,7 @@ F: package/augeas/ F: package/bluez-alsa/ F: package/caps/ F: package/freescale-imx/imx-alsa-plugins/ +F: package/imx-uuu/ F: package/libopusenc/ F: package/libupnpp/ F: package/luv/
package/Config.in.host +1 -0
@@ -33,6 +33,7 @@ menu "Host utilities" source "package/imagemagick/Config.in.host" source "package/imx-mkimage/Config.in.host" source "package/imx-usb-loader/Config.in.host" + source "package/imx-uuu/Config.in.host" source "package/jq/Config.in.host" source "package/jsmin/Config.in.host" source "package/libp11/Config.in.host"
package/imx-uuu/Config.in.host new file +12 -0
@@ -0,0 +1,12 @@ +config BR2_PACKAGE_HOST_IMX_UUU + bool "host imx-uuu" + depends on BR2_arm + help + Freescale/NXP i.MX Chip image deploy tools (formerly + mfgtools). + + It is designed to program firmware to i.MX boards during + production. The communication is done over USB using the + Freescale UTP protocol. + + https://github.com/NXPmicro/mfgtools
package/imx-uuu/imx-uuu.hash new file +3 -0
@@ -0,0 +1,3 @@ +# locally computed +sha256 0377bb26e4eab20e32f2daaecaa9394048ab4443f5b517acde6c27e2dc5310d5 imx-uuu-1.3.102.tar.gz +sha256 cc8d47f7b9260f6669ecd41c24554c552f17581d81ee8fc602c6d23edb8bf495 LICENSE
package/imx-uuu/imx-uuu.mk new file +24 -0
@@ -0,0 +1,24 @@ +################################################################################ +# +# imx-uuu +# +################################################################################ + +IMX_UUU_VERSION = 1.3.102 +IMX_UUU_SITE = $(call github,NXPmicro,mfgtools,uuu_$(IMX_UUU_VERSION)) +IMX_UUU_LICENSE = BSD-3-Clause +IMX_UUU_LICENSE_FILES = LICENSE +HOST_IMX_UUU_DEPENDENCIES = host-libusb host-libzip host-zlib + +# Version string generation is broken in uuu as it relies on git, even when +# building from a source tarball. The version string is used by uuu to do a +# runtime check to detect outdated command list scripts. We overwrite +# gen_ver.sh with something that simply prints a define for GIT_VERSION with +# the uuu version (preceeded by "libuuu_", as done in the original gen_ver.sh). +define HOST_IMX_UUU_OVERWRITE_GEN_VER_SH + echo '#!/bin/sh' > $(@D)/libuuu/gen_ver.sh + echo 'echo "#define GIT_VERSION \"libuuu_$(IMX_UUU_VERSION)\"" > $$1' >> $(@D)/libuuu/gen_ver.sh +endef +HOST_IMX_UUU_POST_PATCH_HOOKS += HOST_IMX_UUU_OVERWRITE_GEN_VER_SH + +$(eval $(host-cmake-package))
Signature · 1 line
2.24.1
PATCH v2 2/2 package/mfgtools: drop package
As suggested in [1] the package mfgtools is dropped.
NXP did replaced the old mfgtools with the version number 0.2 enterily with the uuu (Universal Update Utility) which is somehow named mfgtools 3.0 although the version scheme for the uuu tool is 1.xx.yyy.
As the old mfgtools scripts are not compatible with the new uuu tool and as imx-uuu goes hand-in-hand with imx-uuc, which we ship for the target, the mfgtools package is dropped.
Users should switch to use imx-uuu instead.
[1] http://patchwork.ozlabs.org/patch/1112411/
---
v2:
* add missing link to patchwork
--- Config.in.legacy | 7 ++++ DEVELOPERS | 1 - package/Config.in.host | 1 - package/mfgtools/Config.in.host | 10 ----- package/mfgtools/mfgtools.hash | 4 -- package/mfgtools/mfgtools.mk | 34 ---------------- package/mfgtools/readme.txt | 69 --------------------------------- 7 files changed, 7 insertions(+), 119 deletions(-) delete mode 100644 package/mfgtools/Config.in.host delete mode 100644 package/mfgtools/mfgtools.hash delete mode 100644 package/mfgtools/mfgtools.mk delete mode 100644 package/mfgtools/readme.txt
Config.in.legacy +7 -0
@@ -146,6 +146,13 @@ endif comment "Legacy options removed in 2020.02" +config BR2_PACKAGE_HOST_MFGTOOLS + bool "host mfgtools was removed" + select BR2_LEGACY + help + mfgtools is not maintained anymore. Switch to imx-uuc + instead. + config BR2_PACKAGE_WIREGUARD bool "wireguard package renamed" depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_10
DEVELOPERS +0 -1
@@ -967,7 +967,6 @@ F: configs/nitrogen* F: package/freescale-imx/ F: package/gstreamer1/gst1-imx/ F: package/libimxvpuapi/ -F: package/mfgtools/ F: package/sshpass/ F: package/x11r7/xdriver_xf86-video-imx-viv/
package/Config.in.host +0 -1
@@ -41,7 +41,6 @@ menu "Host utilities" source "package/lpc3250loader/Config.in.host" source "package/lttng-babeltrace/Config.in.host" source "package/mender-artifact/Config.in.host" - source "package/mfgtools/Config.in.host" source "package/mkpasswd/Config.in.host" source "package/mtd/Config.in.host" source "package/mtools/Config.in.host"
package/mfgtools/Config.in.host deleted +0 -10
@@ -1,10 +0,0 @@ -config BR2_PACKAGE_HOST_MFGTOOLS - bool "host mfgtools" - depends on BR2_arm - help - This package contains the Freescale manufacturing tool. - It is designed to program firmware to i.MX boards during - production. The communication is done over USB using the - Freescale UTP protocol. - - https://github.com/codeauroraforum/mfgtools
package/mfgtools/mfgtools.hash deleted +0 -4
@@ -1,4 +0,0 @@ -# locally computed -sha256 055d71227d18883d6e8bc9e854c076015f9a7749820a94272e19071bf0b25c89 mfgtools-0.02.tar.gz -sha256 2655559a6bb1179eae514f5c7166f4ede4f2453efa9cf4dc3c045cab5d57dede LICENSE -sha256 0963b6e5086bf454265b0f57821a02b681d1211e40ad74c310231cb4d94815c9 README.txt
package/mfgtools/mfgtools.mk deleted +0 -34
@@ -1,34 +0,0 @@ -################################################################################ -# -# mfgtools -# -################################################################################ - -MFGTOOLS_VERSION = 0.02 -MFGTOOLS_SITE = $(call github,codeauroraforum,mfgtools,v$(MFGTOOLS_VERSION)) -MFGTOOLS_SUBDIR = MfgToolLib -MFGTOOLS_LICENSE = BSD-3-Clause or CPOL -MFGTOOLS_LICENSE_FILES = LICENSE README.txt -HOST_MFGTOOLS_DEPENDENCIES = host-libusb - -HOST_MFGTOOLS_CFLAGS = \ - $(HOST_CFLAGS) $(HOST_LDFLAGS) -std=c++11 -lpthread \ - -L$(@D)/MfgToolLib -lMfgToolLib -I$(@D)/MfgToolLib \ - -lusb-1.0 -I$(HOST_DIR)/include/libusb-1.0 \ - -fpermissive -Wno-write-strings - -define HOST_MFGTOOLS_CLI_BUILD - $(HOST_CONFIGURE_OPTS) $(MAKE) CC="$(HOSTCXX)" \ - CFLAGS="$(HOST_MFGTOOLS_CFLAGS)" -C $(@D)/TestPrgm -endef - -HOST_MFGTOOLS_POST_BUILD_HOOKS += HOST_MFGTOOLS_CLI_BUILD - -define HOST_MFGTOOLS_INSTALL_CMDS - $(INSTALL) -D -m 755 $(@D)/MfgToolLib/libMfgToolLib.so \ - $(HOST_DIR)/lib/libMfgToolLib.so - $(INSTALL) -D -m 755 $(@D)/TestPrgm/mfgtoolcli \ - $(HOST_DIR)/bin/mfgtoolcli -endef - -$(eval $(host-cmake-package))
package/mfgtools/readme.txt deleted +0 -69
69 lines not on this page · raw message
Signature · 1 line
2.24.1
PATCH v2 2/2 package/mfgtools: drop package
Hi Jorge,
Quoted 10 lines · J?rg Krause
As suggested in [1] the package mfgtools is dropped.
NXP did replaced the old mfgtools with the version number 0.2 enterily with the uuu (Universal Update Utility) which is somehow named mfgtools 3.0 although the version scheme for the uuu tool is 1.xx.yyy.
As the old mfgtools scripts are not compatible with the new uuu tool and as imx-uuu goes hand-in-hand with imx-uuc, which we ship for the target, the mfgtools package is dropped.
I know I'm the one who pushed for that commit to happen but now want to mitigate the claim above.
True uuu depends on imx-uuc and mfgtools (1st of its name) too. BUT by looking at imx-uuc, the two use cases are separated into 2 different files:
- uu.c: daemon that uses utp protocol to communicate with host
- ufb.c: daemon that uses fastboot protocol to communicate with host
So I think it should be safe to have both host clients co-existing for now. Maybe uu.c will be removed at some point in the future but I guess NXP will leave it there for a while.
Regards,
Gary
PATCH v2 2/2 package/mfgtools: drop package
Hi Gary,
Quoted 10 lines · Gary Bisson
Hi Jorge,
Quoted 7 lines · J?rg Krause
As suggested in [1] the package mfgtools is dropped.
NXP did replaced the old mfgtools with the version number 0.2 enterily with the uuu (Universal Update Utility) which is somehow named mfgtools 3.0 although the version scheme for the uuu tool is 1.xx.yyy.
Quoted 6 lines
Quoted 3 lines
As the old mfgtools scripts are not compatible with the new uuu tool and as imx-uuu goes hand-in-hand with imx-uuc, which we ship for the target, the mfgtools package is dropped.
I know I'm the one who pushed for that commit to happen but now want to mitigate the claim above.
Thanks for your feedback and sorry for my late reply.
Quoted 5 lines
True uuu depends on imx-uuc and mfgtools (1st of its name) too. BUT by looking at imx-uuc, the two use cases are separated into 2 different files:
-uu.c: daemon that uses utp protocol to communicate with host
-ufb.c: daemon that uses fastboot protocol to communicate with host
In fact, I am using mfgtools without imx-uuc, but with U-Boot.
Quoted 3 lines
So I think it should be safe to have both host clients co-existing for now. Maybe
uu.cwill be removed at some point in the future but I guess NXP will leave it there for a while.
So, lets just update mfgtools to latest version (1.3.154), right?
Best regards
J?rg Krause
PATCH v2 2/2 package/mfgtools: drop package
Hi Jorg,
Quoted 28 lines · J?rg Krause
Hi Gary,
Quoted 10 lines · Gary Bisson
Hi Jorge,
Quoted 7 lines · J?rg Krause
As suggested in [1] the package mfgtools is dropped.
NXP did replaced the old mfgtools with the version number 0.2 enterily with the uuu (Universal Update Utility) which is somehow named mfgtools 3.0 although the version scheme for the uuu tool is 1.xx.yyy.
Quoted 6 lines
Quoted 3 lines
As the old mfgtools scripts are not compatible with the new uuu tool and as imx-uuu goes hand-in-hand with imx-uuc, which we ship for the target, the mfgtools package is dropped.
I know I'm the one who pushed for that commit to happen but now want to mitigate the claim above.
Thanks for your feedback and sorry for my late reply.
Quoted 5 lines
True uuu depends on imx-uuc and mfgtools (1st of its name) too. BUT by looking at imx-uuc, the two use cases are separated into 2 different files:
-uu.c: daemon that uses utp protocol to communicate with host
-ufb.c: daemon that uses fastboot protocol to communicate with host
Quoted 7 lines
In fact, I am using mfgtools without imx-uuc, but with U-Boot.
Quoted 3 lines
So I think it should be safe to have both host clients co-existing for now. Maybe
uu.cwill be removed at some point in the future but I guess NXP will leave it there for a while.So, lets just update mfgtools to latest version (1.3.154), right?
No, mfgtools 1.x.y really is 'uuu', not mfgtools any more.
So since 'mfgtools' doesn't have any more build issues, I'd say we keep it as-is for people that use it. So the idea is _not_ to drop it.
Then just have your uuu addition patch, so basically both tools co-exist in Buildroot (as they serve different purposes).
Regards,
Gary
PATCH v2 2/2 package/mfgtools: drop package
Hi Gary,
Quoted 33 lines · Gary Bisson
Hi Jorg,
Quoted 30 lines · J?rg Krause
Hi Gary,
Quoted 10 lines · Gary Bisson
Hi Jorge,
Quoted 7 lines · J?rg Krause
As suggested in [1] the package mfgtools is dropped.
NXP did replaced the old mfgtools with the version number 0.2 enterily with the uuu (Universal Update Utility) which is somehow named mfgtools 3.0 although the version scheme for the uuu tool is 1.xx.yyy.
Quoted 6 lines
Quoted 3 lines
As the old mfgtools scripts are not compatible with the new uuu tool and as imx-uuu goes hand-in-hand with imx-uuc, which we ship for the target, the mfgtools package is dropped.
I know I'm the one who pushed for that commit to happen but now want to mitigate the claim above.
Thanks for your feedback and sorry for my late reply.
Quoted 5 lines
True uuu depends on imx-uuc and mfgtools (1st of its name) too. BUT by looking at imx-uuc, the two use cases are separated into 2 different files:
-uu.c: daemon that uses utp protocol to communicate with host
-ufb.c: daemon that uses fastboot protocol to communicate with hostIn fact, I am using mfgtools without imx-uuc, but with U-Boot.
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
So I think it should be safe to have both host clients co-existing for now. Maybe
uu.cwill be removed at some point in the future but I guess NXP will leave it there for a while.So, lets just update mfgtools to latest version (1.3.154), right?
No, mfgtools 1.x.y really is 'uuu', not mfgtools any more.
It is very confusing, how NXP deals with this. From my understanding, mfgtools is the top level name for the image deploying tools.
In mfgtools 2 there was a seperate Windows and Linux build of the 'MfgToolLib', the linux command line utility was 'mfgtoolcli'. The linux branch ended with v0.02, the windows branch with 0.06 -> 2.8.0.
Both branches are abandoned and replaced by libuuu and the command line utility uuu. This new library and tool are introduced of an evolving mfgtools 3.0.
So, indeed there are two different tools, the old and abandoned mfgtools 2 and the new mfgtools 3 (a.k.a uuu).
Note, that for the mfgtools 2 the tag v0.02 was only labeld as "Pre- release" on Github.
Quoted 5 lines
So since 'mfgtools' doesn't have any more build issues, I'd say we keep it as-is for people that use it. So the idea is _not_ to drop it.
Then just have your uuu addition patch, so basically both tools co-exist in Buildroot (as they serve different purposes).
If we really want to keep the mfgtools 2 package, we have to decide how to name the new package:
a) imx-uuu
b) mfgtools3
c) mfgtools_uuu
d) something else
I'm voting for b) mfgtools3, as the github project name is still 'mfgtools' and the project is described as "uuu (Universal Update Utility), mfgtools 3.0".
Best regards
J?rg Krause
PATCH v2 2/2 package/mfgtools: drop package
Hi Jorg,
Quoted 40 lines · J?rg Krause
Hi Gary,
Quoted 37 lines · Gary Bisson
Hi Jorg,
Quoted 34 lines · J?rg Krause
Hi Gary,
Quoted 10 lines · Gary Bisson
Hi Jorge,
Quoted 7 lines · J?rg Krause
As suggested in [1] the package mfgtools is dropped.
NXP did replaced the old mfgtools with the version number 0.2 enterily with the uuu (Universal Update Utility) which is somehow named mfgtools 3.0 although the version scheme for the uuu tool is 1.xx.yyy.
Quoted 6 lines
Quoted 3 lines
As the old mfgtools scripts are not compatible with the new uuu tool and as imx-uuu goes hand-in-hand with imx-uuc, which we ship for the target, the mfgtools package is dropped.
I know I'm the one who pushed for that commit to happen but now want to mitigate the claim above.
Thanks for your feedback and sorry for my late reply.
Quoted 5 lines
True uuu depends on imx-uuc and mfgtools (1st of its name) too. BUT by looking at imx-uuc, the two use cases are separated into 2 different files:
-uu.c: daemon that uses utp protocol to communicate with host
-ufb.c: daemon that uses fastboot protocol to communicate with hostIn fact, I am using mfgtools without imx-uuc, but with U-Boot.
Quoted 3 lines
So I think it should be safe to have both host clients co-existing for now. Maybe
uu.cwill be removed at some point in the future but I guess NXP will leave it there for a while.
Quoted 6 lines
Quoted 3 lines
Quoted 1 line
So, lets just update mfgtools to latest version (1.3.154), right?
No, mfgtools 1.x.y really is 'uuu', not mfgtools any more.
It is very confusing, how NXP deals with this. From my understanding, mfgtools is the top level name for the image deploying tools.
It is confusing yes. And NXP doesn't really deal with it, they just said "here's a new tool, let's forget about the old one".
Quoted 3 lines
In mfgtools 2 there was a seperate Windows and Linux build of the 'MfgToolLib', the linux command line utility was 'mfgtoolcli'. The linux branch ended with v0.02, the windows branch with 0.06 -> 2.8.0.
Yes the versioning is also confusing. Buildroot automated email keeps reminding me that mfgtools isn't at its latest release whereas it is, new 'versions' are just for a different tool really.
Quoted 8 lines
Both branches are abandoned and replaced by libuuu and the command line utility uuu. This new library and tool are introduced of an evolving mfgtools 3.0.
So, indeed there are two different tools, the old and abandoned mfgtools 2 and the new mfgtools 3 (a.k.a uuu).
Note, that for the mfgtools 2 the tag v0.02 was only labeld as "Pre- release" on Github.
Yes, but Yann's thoughts were that since it was in Buildroot for a long time, people might have scripts relying on mfgtools, and therefore might be useful to keep it around [1].
Then at the time I made the point about imx-uuc which wasn't valid. Now that the build is fixed, I agree that we should keep mfgtools as-is.
Quoted 9 lines
Quoted 5 lines
So since 'mfgtools' doesn't have any more build issues, I'd say we keep it as-is for people that use it. So the idea is _not_ to drop it.
Then just have your uuu addition patch, so basically both tools co-exist in Buildroot (as they serve different purposes).
If we really want to keep the mfgtools 2 package, we have to decide how to name the new package:
Quoted 8 lines
a) imx-uuu
b) mfgtools3
c)mfgtools_uuu
d) something elseI'm voting for b) mfgtools3, as the github project name is still 'mfgtools' and the project is described as "uuu (Universal Update Utility), mfgtools 3.0".
I'd personnaly prefer a name with uuu in it as mfgtools is only mentioned for legacy reasons from NXP. But then in every doc they only say uuu [2]. So from a user perspective, I'd look for 'uuu' in menuconfig.
I wish NXP would have switched to another repository...
Regards,
Gary
[1] http://lists.busybox.net/pipermail/buildroot/2019-June/252440.html
[2] https://github.com/NXPmicro/mfgtools/releases/download/uuu_1.3.154/UUU.pdf