# Jetson-TX2 - updating device-tree

**URL:** https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124
**Category:** General Discussions
**Tags:** yocto
**Created:** [June 30, 2020, 10:28am UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124 "2020-06-30T10:28:29Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![naro](https://avatars.discourse-cdn.com/v4/letter/n/5f9b8f/32.png) [@naro](https://hub.mender.io/u/naro)
#### Post date: [June 30, 2020, 10:28am UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/1 "2020-06-30T10:28:29Z")

</div>

Hi guys,

We are struggling to understand if and how the device tree gets updated on a Jetson-TX2.  
A rootfs image created by yocto (“zeus”) does not seem to update the device tree when updating through mender.  
How can we update the device-tree partition(s)?

Thanks!

---

<div class="post-metadata">

### Author: ![oleorhagen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/oleorhagen/32/297_2.png) [@oleorhagen](https://hub.mender.io/u/oleorhagen)
#### Post date: [June 30, 2020, 10:37am UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/2 "2020-06-30T10:37:36Z")

</div>

Not the same board, but some inspiration: [Updating a Raspberry boot partition](https://hub.mender.io/t/updating-a-raspberry-boot-partition/1633/6)

So, it requires the dtb to be present in your rootfs.

---

<div class="post-metadata">

### Author: ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [June 30, 2020, 11:03am UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/3 "2020-06-30T11:03:16Z")

</div>

@dwalkes probably knows this better, but I believe on the NVIDIA boards the `nv_update_engine` is used to update U-boot/kernel/dtb.

With this state-script containing the gist of it:

> <https://github.com/mendersoftware/meta-mender-community/blob/zeus-test/meta-mender-tegra/recipes-mender/tegra-state-scripts/files/redundant-boot-install-script#L62>

---

<div class="post-metadata">

### Author: ![naro](https://avatars.discourse-cdn.com/v4/letter/n/5f9b8f/32.png) [@naro](https://hub.mender.io/u/naro)
#### Post date: [June 30, 2020, 11:07am UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/4 "2020-06-30T11:07:34Z")

</div>

thanks for your reply!  
We tried running the nv\_update\_engine. It didn’t update the device tree. But my understanding is that the devicetree is not part of the BUP?

If it helps we get the following entry\_table in the /opt/ota\_package directory after running nv\_update\_engine:  
root@jetson-tx2:~# cat /opt/ota\_package/entry\_table  
[2020-06-30 13:05:58] bpmp-fw,1368,533904,2,1,1  
[2020-06-30 13:05:58] sce-fw,535272,125568,2,1,1  
[2020-06-30 13:05:58] cpu-bootloader,660840,284128,2,1,1  
[2020-06-30 13:05:58] mb2,944968,116816,2,0,1  
[2020-06-30 13:05:58] spe-fw,1061784,95984,2,0,1  
[2020-06-30 13:05:58] secure-os,1157768,313152,2,1,1  
[2020-06-30 13:05:58] mb1,1470920,99664,2,2,1  
[2020-06-30 13:05:58] mts-bootpack,1570584,2082144,2,1,1  
[2020-06-30 13:05:58] mts-preboot,3652728,63104,2,0,1  
[2020-06-30 13:05:58] sc7,3715832,23632,2,1,1  
[2020-06-30 13:05:58] kernel,3739464,483728,2,1,1

---

<div class="post-metadata">

### Author: ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [June 30, 2020, 11:20am UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/5 "2020-06-30T11:20:22Z")

</div>

Ok, then I am not sure how it works. So will defer to @dwalkes or @madisox who have primarily been involved in the tegra integrations…

---

<div class="post-metadata">

### Author: ![madisox](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/madisox/32/446_2.png) [@madisox](https://hub.mender.io/u/madisox)
#### Post date: [June 30, 2020, 11:55am UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/6 "2020-06-30T11:55:52Z")

</div>

Parts of the BUP payload, like the DTB, are specific to a version of the TX2 module you have in your device. Only if a copy in the payload matches the version of your module will nv\_update\_engine install it.

The version information it uses for matching is in `/etc/nv_boot_control.conf` on the TNSPEC line. Can you post that here?

---

<div class="post-metadata">

### Author: ![naro](https://avatars.discourse-cdn.com/v4/letter/n/5f9b8f/32.png) [@naro](https://hub.mender.io/u/naro)
#### Post date: [June 30, 2020, 12:02pm UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/7 "2020-06-30T12:02:35Z")

</div>

Thanks for your help!  
Here is the requested output

[2020-06-30 13:57:57] root@jetson-tx2:~# cat /etc/nv\_boot\_control.conf  
[2020-06-30 13:57:59] TNSPEC 3310-D00-1000-F.0-1-0-jetson-tx2-mmcblk0p1  
[2020-06-30 13:57:59] TEGRA\_CHIPID 0x18  
[2020-06-30 13:57:59] TEGRA\_OTA\_BOOT\_DEVICE /dev/mmcblk0boot0  
[2020-06-30 13:57:59] TEGRA\_OTA\_GPT\_DEVICE /dev/mmcblk0boot1

---

<div class="post-metadata">

### Author: ![naro](https://avatars.discourse-cdn.com/v4/letter/n/5f9b8f/32.png) [@naro](https://hub.mender.io/u/naro)
#### Post date: [June 30, 2020, 1:05pm UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/8 "2020-06-30T13:05:37Z")

</div>

and for what it’s worth I get this when I grep for 3310 in the bl\_update\_payload (not sure if it’s relevant):

root@jetson-tx2:~# strings /opt/ota\_package/bl\_update\_payload | grep 3310  
3310-1000-B00-A

---

<div class="post-metadata">

### Author: ![madisox](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/madisox/32/446_2.png) [@madisox](https://hub.mender.io/u/madisox)
#### Post date: [June 30, 2020, 3:28pm UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/9 "2020-06-30T15:28:50Z")

</div>

Yes, that’s the problem, then. If you’re using the zeus branch in meta-tegra (based on L4T R32.2.3), BUP payloads built only support a single board revision. The zeus-l4t-r32.3.1 branch builds multi-spec BUP payloads, and it _should_ be including the necessary artifacts for the revision D00 FAB.

---

<div class="post-metadata">

### Author: ![naro](https://avatars.discourse-cdn.com/v4/letter/n/5f9b8f/32.png) [@naro](https://hub.mender.io/u/naro)
#### Post date: [June 30, 2020, 3:51pm UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/10 "2020-06-30T15:51:43Z")

</div>

We are on the zeus-l4t-r32.3.1 branch, actually. Is there a specific (recent) commit that we need to be aware of?  
Is is possible to misconfigure/misuse this feature somehow on our end?  
Can I check something in my build to verify the generation of the payload works as expected?

Thanks!

---

<div class="post-metadata">

### Author: ![naro](https://avatars.discourse-cdn.com/v4/letter/n/5f9b8f/32.png) [@naro](https://hub.mender.io/u/naro)
#### Post date: [June 30, 2020, 6:09pm UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/11 "2020-06-30T18:09:17Z")

</div>

I tried to dig a bit deeper. But to be honst I don’t quite understand how the different bup payloads are getting build and deployed. I see multiple payloads being deployed in the images directory (e.g. u-boot-dtb.bin.bl\_only.bup-payload) but they all contain only the 3310-1000-B00-A string.

But the generated generate\_bup\_payload.sh file looks like this and does contain the paramenters specified in jeston-tx2.conf:

> #!/bin/bash  
> rm -rf signed multi\_signed rollback.bin payloads\_t18x  
> export BOARDID=3310  
> export fuselevel=fuselevel\_production  
> export localbootfile=boot.img  
> export CHIPREV=0  
> MACHINE=jetson-tx2 FAB=“B00” BOARDSKU=“” BOARDREV=“” ./tegra186-flash-helper.sh --bup ./flash.xml.in tegra186-quill-p3310-1000-c03-00-base.dtb jetson-tx2.cfg 0x7090000 “$@”  
> MACHINE=jetson-tx2 FAB=“B02” BOARDSKU=“” BOARDREV=“” ./tegra186-flash-helper.sh --bup ./flash.xml.in tegra186-quill-p3310-1000-c03-00-base.dtb jetson-tx2.cfg 0x7090000 “$@”  
> MACHINE=jetson-tx2 FAB=“C04” BOARDSKU=“” BOARDREV=“” ./tegra186-flash-helper.sh --bup ./flash.xml.in tegra186-quill-p3310-1000-c03-00-base.dtb jetson-tx2.cfg 0x7090000 “$@”  
> MACHINE=jetson-tx2 FAB=“D00” BOARDSKU=“” BOARDREV=“” ./tegra186-flash-helper.sh --bup ./flash.xml.in tegra186-quill-p3310-1000-c03-00-base.dtb jetson-tx2.cfg 0x7090000 “$@”  
> MACHINE=jetson-tx2 FAB=“D01” BOARDSKU=“” BOARDREV=“” ./tegra186-flash-helper.sh --bup ./flash.xml.in tegra186-quill-p3310-1000-c03-00-base.dtb jetson-tx2.cfg 0x7090000 “$@”

Should this build result in one BUP package that will work on all specified board revisions? Or do we need to explicitly set this information somewhere?

---

<div class="post-metadata">

### Author: ![madisox](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/madisox/32/446_2.png) [@madisox](https://hub.mender.io/u/madisox)
#### Post date: [June 30, 2020, 9:42pm UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/12 "2020-06-30T21:42:15Z")

</div>

> Should this build result in one BUP package that will work on all specified board revisions?

It should, yes, once it’s done. You can verify this with the `BUP_generator.py` script, which you can extract from the L4T BSP (in the `Linux_for_Tegra/bootloader` directory).

Example from one of my builds:

```auto
$ BUP_generator.py -c u-boot-dtb.bin.bup-payload 
BLOB PATH:
/build/madison/zeus-l4t-r32.3.1/build/tmp/deploy/images/jetson-tx2/u-boot-jetson-tx2.bin.bup-payload

BLOB HEADER:
       Magic: NVIDIA __BLOB__ V2
     Version: 0x00020000
   Blob Size: 10,472,000 bytes
 Header Size: 48 bytes
 Entry Count: 36 partition(s)
        Type: 0 (0 for update, 1 for BMP)
Uncompressed
   Blob Size: 10,472,000 bytes
   Accessory: 0x0000000000000000

ENTRY TABLE:
| part_name | offset | part_size | version | op_mode | tnspec |
| bpmp-fw | 4368 | 533904 | 2 | 0 | |
| sce-fw | 538272 | 125568 | 2 | 0 | |
| cpu-bootloader | 663840 | 284128 | 2 | 0 | |
| mb2 | 947968 | 116816 | 2 | 0 | |
| spe-fw | 1064784 | 95984 | 2 | 0 | |
| secure-os | 1160768 | 243520 | 2 | 0 | |
| mb1 | 1404288 | 99664 | 2 | 2 | |
| mts-bootpack | 1503952 | 2082144 | 2 | 2 | |
| mts-preboot | 3586096 | 63104 | 2 | 2 | |
| sc7 | 3649200 | 23632 | 2 | 2 | |
| bpmp-fw-dtb | 3672832 | 466240 | 2 | 0 | 3310-B00-1000--1-0-jetson-tx2-mmcblk0p1 |
| bpmp-fw-dtb | 4139072 | 466240 | 2 | 0 | 3310-B02-1000--1-0-jetson-tx2-mmcblk0p1 |
| bpmp-fw-dtb | 4605312 | 466240 | 2 | 0 | 3310-C04-1000--1-0-jetson-tx2-mmcblk0p1 |
| bpmp-fw-dtb | 5071552 | 466240 | 2 | 0 | 3310-D00-1000--1-0-jetson-tx2-mmcblk0p1 |
| bpmp-fw-dtb | 5537792 | 466240 | 2 | 0 | 3310-D01-1000--1-0-jetson-tx2-mmcblk0p1 |
| bootloader-dtb | 6004032 | 371584 | 2 | 0 | 3310-B00-1000--1-0-jetson-tx2-mmcblk0p1 |
| bootloader-dtb | 6375616 | 371584 | 2 | 0 | 3310-B02-1000--1-0-jetson-tx2-mmcblk0p1 |
| bootloader-dtb | 6747200 | 371584 | 2 | 0 | 3310-C04-1000--1-0-jetson-tx2-mmcblk0p1 |
| bootloader-dtb | 7118784 | 371584 | 2 | 0 | 3310-D00-1000--1-0-jetson-tx2-mmcblk0p1 |
| bootloader-dtb | 7490368 | 371584 | 2 | 0 | 3310-D01-1000--1-0-jetson-tx2-mmcblk0p1 |
| BCT | 7861952 | 3584 | 2 | 2 | 3310-B00-1000--1-0-jetson-tx2-mmcblk0p1 |
| BCT | 7865536 | 3584 | 2 | 2 | 3310-B02-1000--1-0-jetson-tx2-mmcblk0p1 |
| BCT | 7869120 | 3584 | 2 | 2 | 3310-C04-1000--1-0-jetson-tx2-mmcblk0p1 |
| BCT | 7872704 | 3584 | 2 | 2 | 3310-D00-1000--1-0-jetson-tx2-mmcblk0p1 |
| BCT | 7876288 | 3584 | 2 | 2 | 3310-D01-1000--1-0-jetson-tx2-mmcblk0p1 |
| MB1_BCT | 7879872 | 50096 | 2 | 0 | 3310-B00-1000--1-0-jetson-tx2-mmcblk0p1 |
| MB1_BCT | 7929968 | 50096 | 2 | 0 | 3310-B02-1000--1-0-jetson-tx2-mmcblk0p1 |
| MB1_BCT | 7980064 | 50096 | 2 | 0 | 3310-C04-1000--1-0-jetson-tx2-mmcblk0p1 |
| MB1_BCT | 8030160 | 50096 | 2 | 0 | 3310-D00-1000--1-0-jetson-tx2-mmcblk0p1 |
| MB1_BCT | 8080256 | 50096 | 2 | 0 | 3310-D01-1000--1-0-jetson-tx2-mmcblk0p1 |
| kernel | 8130352 | 483728 | 2 | 0 | |
| kernel-dtb | 8614080 | 371584 | 2 | 0 | 3310-B00-1000--1-0-jetson-tx2-mmcblk0p1 |
| kernel-dtb | 8985664 | 371584 | 2 | 0 | 3310-B02-1000--1-0-jetson-tx2-mmcblk0p1 |
| kernel-dtb | 9357248 | 371584 | 2 | 0 | 3310-C04-1000--1-0-jetson-tx2-mmcblk0p1 |
| kernel-dtb | 9728832 | 371584 | 2 | 0 | 3310-D00-1000--1-0-jetson-tx2-mmcblk0p1 |
| kernel-dtb | 10100416 | 371584 | 2 | 0 | 3310-D01-1000--1-0-jetson-tx2-mmcblk0p1 |

```

---

<div class="post-metadata">

### Author: ![naro](https://avatars.discourse-cdn.com/v4/letter/n/5f9b8f/32.png) [@naro](https://hub.mender.io/u/naro)
#### Post date: [July 1, 2020, 6:37pm UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/13 "2020-07-01T18:37:26Z")

</div>

Hi @madisox,

I have the feeling I am missing something very basic in my configuration.  
This is the output for the same file on my build. There are no devicetrees included:

```
> naro@naro:~/drive_yocto/yocto_43/build/tmp/deploy/images/jetson-tx2$ ./BUP_generator.py -c u-boot-jetson-tx2.bin.bup-payload
> BLOB PATH:
> /home/naro/drive_yocto/yocto_43/build/tmp/deploy/images/jetson-tx2/u-boot-jetson-tx2.bin.bup-payload
> 
> BLOB HEADER:
> Magic: NVIDIA __BLOB__ V2
> Version: 0x00020000
> Blob Size: 4,223,192 bytes
> Header Size: 48 bytes
> Entry Count: 11 partition(s)
> Type: 0 (0 for update, 1 for BMP)
> Uncompressed
> Blob Size: 4,223,192 bytes
> Accessory: 0x0000000000000000
> 
> ENTRY TABLE:
> | part_name | offset | part_size | version | op_mode | tnspec |
> | bpmp-fw | 1368 | 533904 | 2 | 0 | |
> | sce-fw | 535272 | 125568 | 2 | 0 | |
> | cpu-bootloader | 660840 | 284128 | 2 | 0 | |
> | mb2 | 944968 | 116816 | 2 | 0 | |
> | spe-fw | 1061784 | 95984 | 2 | 0 | |
> | secure-os | 1157768 | 313152 | 2 | 0 | |
> | mb1 | 1470920 | 99664 | 2 | 2 | |
> | mts-bootpack | 1570584 | 2082144 | 2 | 2 | |
> | mts-preboot | 3652728 | 63104 | 2 | 2 | |
> | sc7 | 3715832 | 23632 | 2 | 2 | |
> | kernel | 3739464 | 483728 | 2 | 0 | |
```

---

<div class="post-metadata">

### Author: ![madisox](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/madisox/32/446_2.png) [@madisox](https://hub.mender.io/u/madisox)
#### Post date: [July 1, 2020, 6:57pm UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/14 "2020-07-01T18:57:57Z")

</div>

Yes, that’s definitely incomplete. Check the log file for the u-boot-bup-payload do\_deploy task, which should be at `$BUILDDIR/tmp/work/jetson_tx2-poky-linux/u-boot-bup-payload/1.0/temp/log.do_deploy` (or something similar, depending on your distro configuration). I have seen cases where the BUP generator script encounters (and logs) errors but doesn’t fail out the execution of the task. That could be happening here.

---

<div class="post-metadata">

### Author: ![naro](https://avatars.discourse-cdn.com/v4/letter/n/5f9b8f/32.png) [@naro](https://hub.mender.io/u/naro)
#### Post date: [July 1, 2020, 7:17pm UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/15 "2020-07-01T19:17:53Z")

</div>

Ok, some of the sections look suspicious. It seems the script can’t find relevant files. Do I interpret that correctly? Is there a dependency missing?

```
[7.0670] Copying signed file in /home/naro/drive_yocto/yocto_43/build/tmp/work/jetson_tx2-poky-linux/u-boot-bup-payload/1.0-r0/bup-payload/signed
[13.0453] tegraparser_v2 --pt flash.xml.bin --generateflashindex /home/naro/drive_yocto/yocto_43/build/tmp/work/jetson_tx2-poky-linux/u-boot-bup-payload/1.0-r0/bup-payload/signed/flash.xm
l.tmp flash.idx
[13.0504] File u-boot-bup-payload-jetson-tx2.dataimg open failed
[13.1515]
Error: Return value 19
Command tegraparser_v2 --pt flash.xml.bin --generateflashindex /home/naro/drive_yocto/yocto_43/build/tmp/work/jetson_tx2-poky-linux/u-boot-bup-payload/1.0-r0/bup-payload/signed/flash.xml.tmp
 flash.idx

signing images failed

Creating update payloads for Jetson-3310-D00-1000--1-0-jetson-tx2-mmcblk0p1 board ...
ls: cannot access 'multi_signed/*/tegra186*bpmp*_sigheader.dtb.encrypt': No such file or directory
WARNING: Failed to find image for bpmp-fw-dtb
ls: cannot access 'multi_signed/*/tegra186-quill*_sigheader.dtb.encrypt': No such file or directory
WARNING: Failed to find image for bootloader-dtb
ls: cannot access 'multi_signed/*/tegra186-quill*_sigheader.dtb.encrypt': No such file or directory
WARNING: Failed to find image for kernel-dtb
ls: cannot access 'multi_signed/*/br_bct*.bct': No such file or directory
WARNING: Failed to find image for BCT
ls: cannot access 'multi_signed/*/mb1_cold_boot*.bct.encrypt': No such file or directory
WARNING: Failed to find image for MB1_BCT
creating bl_and_kernel payload

```

Thanks a lot for your help on this! I really appreciate it!

---

<div class="post-metadata">

### Author: ![madisox](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/madisox/32/446_2.png) [@madisox](https://hub.mender.io/u/madisox)
#### Post date: [July 1, 2020, 7:49pm UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/16 "2020-07-01T19:49:33Z")

</div>

Yep, that’s the problem. I think this is due to some recent commits in meta-tegra that need some corresponding changes in the meta-mender-community/meta-mender-tegra layer.

I have some changes on [a branch in my fork](https://github.com/madisongh/meta-mender-community/tree/patches-zeus-test) of that repository that should fix this. In particular, [this commit](https://github.com/madisongh/meta-mender-community/commit/e1226d046b2db44ce1bed5dcbb719e8cb3c7d572).

---

<div class="post-metadata">

### Author: ![naro](https://avatars.discourse-cdn.com/v4/letter/n/5f9b8f/32.png) [@naro](https://hub.mender.io/u/naro)
#### Post date: [July 2, 2020, 8:53am UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/17 "2020-07-02T08:53:17Z")

</div>

Awesome! Your patches fixed it for me, the payload contains the devicetrees now!  
Many thanks again for your quick help with this issue!

@mirzak, do you have a timeframe when those patches will make it into mender?

---

<div class="post-metadata">

### Author: ![madisox](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/madisox/32/446_2.png) [@madisox](https://hub.mender.io/u/madisox)
#### Post date: [July 2, 2020, 11:23am UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/18 "2020-07-02T11:23:00Z")

</div>

I thought @dwalkes had already picked up those patches to upstream to meta-mender-community… I’ll work with him to get them there.

---

<div class="post-metadata">

### Author: ![jgrahsl](https://avatars.discourse-cdn.com/v4/letter/j/ecc23a/32.png) [@jgrahsl](https://hub.mender.io/u/jgrahsl)
#### Post date: [July 2, 2020, 11:45am UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/19 "2020-07-02T11:45:26Z")

</div>

I can confirm that these patches enabled me to update the dtb using nv\_update\_engine.

Thank you @madisox and @naro

---

<div class="post-metadata">

### Author: ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [July 2, 2020, 11:48am UTC](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124/20 "2020-07-02T11:48:13Z")

</div>

There was a big update merged from @dwalkes ([link](https://github.com/mendersoftware/meta-mender-community/pull/147)) but I can not see that the mentioned change-set was part of that PR.

[Next page](https://hub.mender.io/t/jetson-tx2-updating-device-tree/2124.md?page=2)