flash OS image fail on new TX2 modules.

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

We have purchased 4 unit TX2 modules from a agent, when we mounted them on Jetson TX2 Developer Kit base board and try to flash OS with jetpack3.0 , it always fail with all those modules. We have changed several Jetson TX2 Developer Kit base board and Ubuntu host PC, but the fault as before. We have connect a serial cable to the console and found there was something wrong when boot, the related message is:

[    2.114554] tegradc 15210000.nvdisplay: DT parsed successfully
[    2.114654] ------------[ cut here ]------------
[    2.114657] WARNING: at ffffffc0007c4470 [verbose debug info unavailable]
[    2.114665] Modules linked in:
[    2.114667] 
[    2.114685] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.4.15-tegra #1
[    2.114687] Hardware name: quill (DT)
[    2.114691] task: ffffffc1f6870000 ti: ffffffc1f6878000 task.ti: ffffffc1f6878000
[    2.114722] PC is at __tegra_isomgr_register+0x30c/0x4d4
[    2.114726] LR is at __tegra_isomgr_register+0x30c/0x4d4
[    2.114750] pc : [<ffffffc0007c4470>] lr : [<ffffffc0007c4470>] pstate: 80000045
[    2.114764] sp : ffffffc1f687bb30
[    2.114792] x29: ffffffc1f687bb30 x28: 0000000000000380 
[    2.114806] x27: ffffffc001320000 x26: ffffffc001260000 
[    2.114814] x25: ffffffc000b4b000 x24: 0000000000000000 
[    2.114819] x23: 0000000000000000 x22: 0000000000000008 
[    2.114827] x21: 000000000016e360 x20: ffffffc001320c40 
[    2.114834] x19: ffffffc001321020 x18: 000000000000000b 
[    2.114842] x17: ffffffc000a6da80 x16: ffffffc000a6da80 
[    2.114858] x15: 00000000fa83b2da x14: 2c30303030353231 
[    2.114876] x13: 3d77625f6f73695f x12: 7073692072657473 
[    2.114890] x11: 696765725f72676d x10: ffffffc0012bae88 
[    2.114953] x9 : ffffffc1f687ba80 x8 : 206d6f726620424b 
[    2.114961] x7 : 3030303030353120 x6 : ffffffc0012bb838 
[    2.114970] x5 : 0000000003e7c423 x4 : 0000000000000000 
[    2.114975] x3 : ffffffc1f687b9a0 x2 : 0000000000000000 
[    2.114980] x1 : 0000000000000000 x0 : 000000000000002b 
[    2.114981] 
[    2.115018] ---[ end trace 95e315db6bb23a16 ]---
[    2.115022] Call trace:
[    2.115029] [<ffffffc0007c4470>] __tegra_isomgr_register+0x30c/0x4d4
[    2.115035] [<ffffffc0007c4654>] tegra_isomgr_register+0x1c/0x2c
[    2.115054] [<ffffffc000417748>] tegra_camera_probe+0x270/0x3d8
[    2.115073] [<ffffffc000532948>] platform_drv_probe+0x50/0xbc
[    2.115080] [<ffffffc000530468>] driver_probe_device+0xc8/0x408
[    2.115083] [<ffffffc000530844>] __driver_attach+0x9c/0xa0
[    2.115130] [<ffffffc00052e4e4>] bus_for_each_dev+0x58/0x98
[    2.115135] [<ffffffc00052ff10>] driver_attach+0x20/0x28
[    2.115139] [<ffffffc00052fa80>] bus_add_driver+0x1f0/0x294
[    2.115145] [<ffffffc00053162c>] driver_register+0x68/0x108
[    2.115150] [<ffffffc000532850>] __platform_driver_register+0x54/0x5c
[    2.115157] [<ffffffc000fe59d8>] tegra_camera_init+0x18/0x20
[    2.115172] [<ffffffc000081ab4>] do_one_initcall+0xc8/0x1c0
[    2.115192] [<ffffffc000fbab60>] kernel_init_freeable+0x1d0/0x274
[    2.115212] [<ffffffc000a5cd6c>] kernel_init+0x10/0xe0
[    2.115222] [<ffffffc000084e10>] ret_from_fork+0x10/0x40
[    2.115226] __tegra_isomgr_register(): ISO BW usage:
[    2.115230] __tegra_isomgr_register(): client=disp_0, iso dedi bw=0KB
[    2.115233] __tegra_isomgr_register(): client=disp_1, iso dedi bw=0KB
[    2.115236] __tegra_isomgr_register(): client=disp_2, iso dedi bw=0KB
[    2.115238] __tegra_isomgr_register(): client=isp_a, iso dedi bw=0KB
[    2.115241] __tegra_isomgr_register(): client=tegra_camera_ctrl, iso dedi bw=1500000KB
[    2.115243] __tegra_isomgr_register(): client=ape_adma, iso dedi bw=0KB
[    2.115246] __tegra_isomgr_register(): client=eqos, iso dedi bw=0KB
[    2.115248] __tegra_isomgr_register(): revisit BW usage of iso clients
[    2.129223] tegradc 15210000.nvdisplay: vblank syncpt # 7 for dc 1
...
...
...

[    4.658688] bcm54xx_low_power_mode(): put phy in iddq-lp mode
[    4.659621] max_iso_bw is relaxed to 1581920KB from 1500000KB
[    4.659622] ------------[ cut here ]------------
[    4.659625] WARNING: at ffffffc0007c4470 [verbose debug info unavailable]
[    4.659628] Modules linked in:
[    4.659630] 
[    4.659641] CPU: 0 PID: 53 Comm: kworker/u12:1 Tainted: G        W       4.4.15-tegra #1
[    4.659643] Hardware name: quill (DT)
[    4.659668] Workqueue: events_unbound async_run_entry_fn
[    4.659671] task: ffffffc1f5923e80 ti: ffffffc1f59b8000 task.ti: ffffffc1f59b8000
[    4.659689] PC is at __tegra_isomgr_register+0x30c/0x4d4
[    4.659691] LR is at __tegra_isomgr_register+0x30c/0x4d4
[    4.659695] pc : [<ffffffc0007c4470>] lr : [<ffffffc0007c4470>] pstate: 80000045
[    4.659696] sp : ffffffc1f59bba80
[    4.659698] x29: ffffffc1f59bba80 x28: 0000000000000460 
[    4.659701] x27: ffffffc001320000 x26: ffffffc001260000 
[    4.659703] x25: ffffffc000b4b000 x24: 0000000000000000 
[    4.659705] x23: 0000000000000000 x22: 000000000000000a 
[    4.659707] x21: 0000000000014000 x20: ffffffc001320c40 
[    4.659709] x19: ffffffc001321100 x18: ffffffc000ad5840 
[    4.659710] x17: ffffffc000a6da80 x16: 00000000fa83b2da 
[    4.659712] x15: 000000000002ec2b x14: 000129087a9750c5 
[    4.659714] x13: 0000000000000000 x12: 0000000000000400 
[    4.659716] x11: 00000000000387f9 x10: ffffffc0012bae88 
[    4.659718] x9 : ffffffc1f59bb9d0 x8 : 206d6f726620424b 
[    4.659719] x7 : 3032393138353120 x6 : ffffffc0012bb838 
[    4.659721] x5 : 0000000008a553db x4 : 0000000000000000 
[    4.659723] x3 : ffffffc1f59bb8f0 x2 : 0000000000000000 
[    4.659724] x1 : 0000000000000000 x0 : 0000000000000031 
[    4.659725] 
[    4.659727] ---[ end trace 95e315db6bb23a17 ]---
[    4.659730] Call trace:
[    4.659732] [<ffffffc0007c4470>] __tegra_isomgr_register+0x30c/0x4d4
[    4.659735] [<ffffffc0007c4654>] tegra_isomgr_register+0x1c/0x2c
[    4.659752] [<ffffffc00086c660>] eqos_probe+0x964/0xfac
[    4.659765] [<ffffffc000532948>] platform_drv_probe+0x50/0xbc
[    4.659769] [<ffffffc000530468>] driver_probe_device+0xc8/0x408
[    4.659770] [<ffffffc000530844>] __driver_attach+0x9c/0xa0
[    4.659776] [<ffffffc00052e4e4>] bus_for_each_dev+0x58/0x98
[    4.659779] [<ffffffc00052ff10>] driver_attach+0x20/0x28
[    4.659782] [<ffffffc00052e9a0>] driver_attach_async+0x14/0x50
[    4.659784] [<ffffffc0000bf830>] async_run_entry_fn+0x44/0x180
[    4.659793] [<ffffffc0000b7240>] process_one_work+0x154/0x434
[    4.659795] [<ffffffc0000b7654>] worker_thread+0x134/0x40c
[    4.659800] [<ffffffc0000bcebc>] kthread+0xe0/0xf4
[    4.659808] [<ffffffc000084e10>] ret_from_fork+0x10/0x40
[    4.659810] __tegra_isomgr_register(): ISO BW usage:
[    4.659812] __tegra_isomgr_register(): client=disp_0, iso dedi bw=0KB
[    4.659814] __tegra_isomgr_register(): client=disp_1, iso dedi bw=0KB
[    4.659816] __tegra_isomgr_register(): client=disp_2, iso dedi bw=0KB
[    4.659817] __tegra_isomgr_register(): client=isp_a, iso dedi bw=0KB
[    4.659820] __tegra_isomgr_register(): client=tegra_camera_ctrl, iso dedi bw=1500000KB
[    4.659821] __tegra_isomgr_register(): client=ape_adma, iso dedi bw=0KB
[    4.659822] __tegra_isomgr_register(): client=eqos, iso dedi bw=81920KB
[    4.659823] __tegra_isomgr_register(): revisit BW usage of iso clients
[    5.013095] tegra210-adsp adsp_audio: Default param-type to BYTE for spkprot
[    5.021069] tegra210-adsp adsp_audio: Default param-type to BYTE for src
[    5.028561] tegra210-adsp adsp_audio: Default param-type to BYTE for aac-dec1
[    5.036503] tegra210-adsp adsp_audio: Default param-type to BYTE for aec
[    5.043568] tegra210-adsp adsp_audio: adma channel page address dt entry not found
[    5.051840] tegra210-adsp adsp_audio: using adma channel page 0
[    5.058326] tegra210_adsp_audio_platform_probe probe successfull.max_iso_bw is relaxed to 1606496KB from 1581920KB
[    5.073574] ------------[ cut here ]------------
[    5.079189] WARNING: at ffffffc0007c4470 [verbose debug info unavailable]
[    5.086383] Modules linked in:
[    5.089864] 
[    5.091778] CPU: 2 PID: 1 Comm: swapper/0 Tainted: G        W       4.4.15-tegra #1
[    5.100263] Hardware name: quill (DT)
[    5.104376] task: ffffffc1f6870000 ti: ffffffc1f6878000 task.ti: ffffffc1f6878000
[    5.112808] PC is at __tegra_isomgr_register+0x30c/0x4d4
[    5.118624] LR is at __tegra_isomgr_register+0x30c/0x4d4
[    5.124452] pc : [<ffffffc0007c4470>] lr : [<ffffffc0007c4470>] pstate: 60000045
[    5.132779] sp : ffffffc1f687b790
[    5.136568] x29: ffffffc1f687b790 x28: 00000000000003f0 
[    5.142409] x27: ffffffc001320000 x26: ffffffc001260000 
[    5.148235] x25: ffffffc000b4b000 x24: ffffffc1efa14000 
[    5.154072] x23: ffffffc0008c8334 x22: 0000000000000009 
[    5.159904] x21: 0000000000006000 x20: ffffffc001320c40 
[    5.165752] x19: ffffffc001321090 x18: 0000000000000000 
[    5.171605] x17: 0000000000000000 x16: ffffffc000a6da80 
[    5.177436] x15: ffffffc000a6da80 x14: 0000000000000008 
[    5.183254] x13: ffffffc1f4131630 x12: 0000000000000001 
[    5.189059] x11: 00000000ffffffff x10: ffffffc0011114a8 
[    5.194871] x9 : 00000000000002ca x8 : ffffffc000ac2e00 
[    5.200656] x7 : 0000000000000001 x6 : 0000000000000000 
[    5.206437] x5 : 0000000000000000 x4 : 0000000000000000 
[    5.212193] x3 : ffffffc1f687b600 x2 : 0000000000000000 
[    5.217953] x1 : 0000000000000000 x0 : 0000000000000031 
[    5.223691] 
[    5.225555] ---[ end trace 95e315db6bb23a18 ]---
[    5.230558] Call trace:
[    5.233382] [<ffffffc0007c4470>] __tegra_isomgr_register+0x30c/0x4d4
[    5.240112] [<ffffffc0007c4654>] tegra_isomgr_register+0x1c/0x2c
[    5.246505] [<ffffffc0008c83c0>] tegra_isomgr_adma_register+0x88/0xe8
[    5.253332] [<ffffffc0008c92c8>] tegra210_admaif_probe+0x138/0x450
[    5.259896] [<ffffffc000532948>] platform_drv_probe+0x50/0xbc
[    5.266004] [<ffffffc000530468>] driver_probe_device+0xc8/0x408
[    5.272284] [<ffffffc000530900>] __device_attach_driver+0x8c/0xb0
[    5.278733] [<ffffffc00052e59c>] bus_for_each_drv+0x54/0x94
[    5.284668] [<ffffffc000530290>] __device_attach+0xc0/0x150
[    5.290602] [<ffffffc000530a40>] device_initial_probe+0x10/0x18
[    5.296889] [<ffffffc00052f738>] bus_probe_device+0x90/0x98
[    5.302832] [<ffffffc00052d430>] device_add+0x3ac/0x584
[    5.308434] [<ffffffc0007a8af8>] of_device_add+0x50/0x5c
[    5.314118] [<ffffffc0007a9454>] of_platform_device_create_pdata+0x90/0xe8
[    5.321372] [<ffffffc0007a95ac>] of_platform_bus_create+0xe4/0x3c0
[    5.327930] [<ffffffc0007a99f0>] of_platform_populate+0x48/0xac
[    5.334229] [<ffffffc0008d6088>] tegra186_xbar_registration+0x7c/0x110
[    5.341155] [<ffffffc0008d6c20>] tegra210_xbar_probe+0x2a8/0x418
[    5.347557] [<ffffffc000532948>] platform_drv_probe+0x50/0xbc
[    5.353702] [<ffffffc000530468>] driver_probe_device+0xc8/0x408
[    5.360021] [<ffffffc000530844>] __driver_attach+0x9c/0xa0
[    5.365914] [<ffffffc00052e4e4>] bus_for_each_dev+0x58/0x98
[    5.371883] [<ffffffc00052ff10>] driver_attach+0x20/0x28
[    5.377589] [<ffffffc00052fa80>] bus_add_driver+0x1f0/0x294
[    5.383554] [<ffffffc00053162c>] driver_register+0x68/0x108
[    5.389518] [<ffffffc000532850>] __platform_driver_register+0x54/0x5c
[    5.396347] [<ffffffc001000bb4>] tegra210_xbar_driver_init+0x18/0x20
[    5.403106] [<ffffffc000081ab4>] do_one_initcall+0xc8/0x1c0
[    5.409088] [<ffffffc000fbab60>] kernel_init_freeable+0x1d0/0x274
[    5.415592] [<ffffffc000a5cd6c>] kernel_init+0x10/0xe0
[    5.421130] [<ffffffc000084e10>] ret_from_fork+0x10/0x40
[    5.426878] __tegra_isomgr_register(): ISO BW usage:
[    5.432252] __tegra_isomgr_register(): client=disp_0, iso dedi bw=0KB
[    5.439114] __tegra_isomgr_register(): client=disp_1, iso dedi bw=0KB
[    5.445949] __tegra_isomgr_register(): client=disp_2, iso dedi bw=0KB
[    5.452769] __tegra_isomgr_register(): client=isp_a, iso dedi bw=0KB
[    5.459524] __tegra_isomgr_register(): client=tegra_camera_ctrl, iso dedi bw=1500000KB
[    5.469626] __tegra_isomgr_register(): client=ape_adma, iso dedi bw=24576KB
[    5.476993] __tegra_isomgr_register(): client=eqos, iso dedi bw=81920KB
[    5.484026] __tegra_isomgr_register(): revisit BW usage of iso clients
[    5.505001] OPE platform probe
[    5.509050] OPE platform probe successful
[    5.539550] tegra-snd-t186ref-mobile-rt565x sound: Failed to get HP Det GPIO, should be handled by codec
[    5.640538] tegra-snd-t186ref-mobile-rt565x sound: ADMAIF1 <-> ADMAIF1 mapping ok
[    5.649315] tegra-snd-t186ref-mobile-rt565x sound: ADMAIF2 <-> ADMAIF2 mapping ok
[    5.657979] tegra-snd-t186ref-mobile-rt565x sound: ADMAIF3 <-> ADMAIF3 mapping ok
...
...
...
[  317.913620] rc.local[723]: RTNETLINK answers: Network is unreachable
[  318.923111] rc.local[723]: RTNETLINK answers: Network is unreachable
[  319.931058] rc.local[723]: RTNETLINK answers: Network is unreachable
[  320.939568] rc.local[723]: RTNETLINK answers: Network is unreachable
[  321.948476] rc.local[723]: RTNETLINK answers: Network is unreachable

But when we mounted the TX2 module from the Developer Kit, the flash always success, so we think maybe there are something wrong with those “brand new” modules.we have purchased 25pcs modules from the same agent last time, and there are 2pcs have the same fault. can you give us the reason? if necessary, we can provide the SN of those modules.

the full log message and jetpack screen shot are in the attachments:

flash-fail-log.txt (127 KB)

ubuntu14.04@vmware-2019-05-09-10-14-41.png
ubuntu14.04@vmware-2019-05-09-10-14-41.png1440×900 472 KB

2

Some suggestion here

  1. If you want to share dmesg, please do not just copy and paste it. Forum may cut off your comments.
    You could use code block or just attach the file here.
  2. Could you try rel-28.1 or rel-28.2? They are much more stable release.
3

Tips: Hover your mouse over the upper right corner quote icon of an existing post. Other icons will show up. One is pencil for edit, another is the paper clip for file attach.

If you edit and highlight any code or log, and then click the “code” icon (looks like “</>”), then scroll bars will be added and formatting preserved.

4

Yes, we have tried the jetpack3.1(r28.1) and jetpack3.3(r28.2), it seems ok, there is no kernel thread broken when boot linux on those TX2 modules. but the applications we developed are based on jetpack3.0 (the drivers, dts, scripts, third-party software packages and so on), so we want to continue using it, could you give us a way to fix the problem? thanks a lot!

5

Hi ericbin,

Your log seems not match what you said in first comment. In first comment, if I understand correctly, you said it is a “flash” problem, but what we saw is a kernel panic log, which seems also not fatal.

Could you give a more brief description for us to explain the problem?

6

Yes, the “flash” is almost success, the uboot, kernel, rootfs have been written in to the TX2 module. but when booting the kernel for the second stage “flash” (CUDA, tensorRT, visionworks and so on), it will fail. and the reason is there are threads broken when kernel booting,it seems the r27.1 linux kernel can not boot on the TX2 modules which produced recently, but we want to continue using R27.1 kernel, is there any way to fix this problem? thanks

These message below means there are threads broken:

[ 2.114685] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.4.15-tegra #1
[ 2.114687] Hardware name: quill (DT)
[ 2.114691] task: ffffffc1f6870000 ti: ffffffc1f6878000 task.ti: ffffffc1f6878000
[ 2.114722] PC is at __tegra_isomgr_register+0x30c/0x4d4
[ 2.114726] LR is at __tegra_isomgr_register+0x30c/0x4d4
[ 2.114750] pc : [] lr : [] pstate: 80000045
[ 2.114764] sp : ffffffc1f687bb30
[ 2.114792] x29: ffffffc1f687bb30 x28: 0000000000000380
[ 2.114806] x27: ffffffc001320000 x26: ffffffc001260000
[ 2.114814] x25: ffffffc000b4b000 x24: 0000000000000000
[ 2.114819] x23: 0000000000000000 x22: 0000000000000008
[ 2.114827] x21: 000000000016e360 x20: ffffffc001320c40
[ 2.114834] x19: ffffffc001321020 x18: 000000000000000b
[ 2.114842] x17: ffffffc000a6da80 x16: ffffffc000a6da80
[ 2.114858] x15: 00000000fa83b2da x14: 2c30303030353231
[ 2.114876] x13: 3d77625f6f73695f x12: 7073692072657473
[ 2.114890] x11: 696765725f72676d x10: ffffffc0012bae88
[ 2.114953] x9 : ffffffc1f687ba80 x8 : 206d6f726620424b
[ 2.114961] x7 : 3030303030353120 x6 : ffffffc0012bb838
[ 2.114970] x5 : 0000000003e7c423 x4 : 0000000000000000
[ 2.114975] x3 : ffffffc1f687b9a0 x2 : 0000000000000000
[ 2.114980] x1 : 0000000000000000 x0 : 000000000000002b
[ 2.114981]
[ 2.115018] —[ end trace 95e315db6bb23a16 ]—
[ 2.115022] Call trace:
[ 2.115029] [] __tegra_isomgr_register+0x30c/0x4d4
[ 2.115035] [] tegra_isomgr_register+0x1c/0x2c
[ 2.115054] [] tegra_camera_probe+0x270/0x3d8
[ 2.115073] [] platform_drv_probe+0x50/0xbc
[ 2.115080] [] driver_probe_device+0xc8/0x408
[ 2.115083] [] __driver_attach+0x9c/0xa0
[ 2.115130] [] bus_for_each_dev+0x58/0x98
[ 2.115135] [] driver_attach+0x20/0x28
[ 2.115139] [] bus_add_driver+0x1f0/0x294
[ 2.115145] [] driver_register+0x68/0x108
[ 2.115150] [] __platform_driver_register+0x54/0x5c
[ 2.115157] [] tegra_camera_init+0x18/0x20
[ 2.115172] [] do_one_initcall+0xc8/0x1c0
[ 2.115192] [] kernel_init_freeable+0x1d0/0x274
[ 2.115212] [] kernel_init+0x10/0xe0
[ 2.115222] [] ret_from_fork+0x10/0x40
[ 2.115226] __tegra_isomgr_register(): ISO BW usage:
[ 2.115230] __tegra_isomgr_register(): client=disp_0, iso dedi bw=0KB
[ 2.115233] __tegra_isomgr_register(): client=disp_1, iso dedi bw=0KB
[ 2.115236] __tegra_isomgr_register(): client=disp_2, iso dedi bw=0KB
[ 2.115238] __tegra_isomgr_register(): client=isp_a, iso dedi bw=0KB
[ 2.115241] __tegra_isomgr_register(): client=tegra_camera_ctrl, iso dedi bw=1500000KB
[ 2.115243] __tegra_isomgr_register(): client=ape_adma, iso dedi bw=0KB
[ 2.115246] __tegra_isomgr_register(): client=eqos, iso dedi bw=0KB
[ 2.115248] __tegra_isomgr_register(): revisit BW usage of iso clients
[ 2.129223] tegradc 15210000.nvdisplay: vblank syncpt # 7 for dc 1

7

ok, I just wanted to confirm the “flash” does not have error. To be more precisely, there are some kernel panic during boot up.

So these errors only happen to 2 pcs of tx2 and they are “brand new”? I notice there are some numbers you mentioned before. Could you readdress them again?

I just want to make sure if “all” brand new modules have this problem or just few of brand new one have it.
If only few (2 pcs) of them have this issue, I would suggest to RMA them.

8

We purchased 25 pcs brand new modules last year, and there are 2pcs modules has this problem, and we purchased 4pcs new modules this week, all of these 4pcs modules can not boot R27.1 kernel and show the threads broken message on console. We have consulted the agent(www.synnex.com.tw), they suggest us try to flash R28.1 and R28.2. and it seems everything ok with those two versions. So we think maybe there is something changed with the hardware and the R27.1 can not run on it any longer. should we return them back to the agent?

9

Could you confirm the serial number as this issue?

https://devtalk.nvidia.com/default/topic/1051568/jetson-tx2/flashing-error-err-unsupported-board-revision-d01/post/5337812/#5337812

10

S/N 0420819050311
699-83310-1000-D00 E

S/N 0420819050821
699-83310-1000-D00 E

11

Thanks. I will check with our internal team.

12

Is there any news about this issue? thanks.

13

ericbin,

We are still checking this internally.

14

Hi ericbin,

Could you upgrade to your development to rel-28? Since rel-27.1 is only a developer preview, we may not put too much effort on it.

If you have strong business requirement, please contact NV sales for this. Sorry for inconvenience.

15

so, does it means that there have no problem with those modules and we can use them in our product, we should not RMA them ?

16

Please test it on rel-28 based release. Another forum topic already had no problem on rel-28.

17

Hi ericbin,

What’s the serial number of the modules that are successfully to run rel-27.1?

18

hi, WayneWWW, We have fully tested 3pcs modules with jetpack3.3(r28.2.1). and did not find anything wrong with 2pcs modules (SN 0420819050304 0420819050311) still, but the other module(SN 0420819050821) has something wrong with the ethernet. we tried to ping it from a PC, and lost serveral packets every 10 seconds about, on the serial console, it will show the message about link down/up every 100 seconds. but there is no such issue on the other 2pcs modules.
so we want to know is there any way for customers to check whether the module is Original authentic product? thanks.

the ping log and serial console message are in the attachments
ping-log.txt (30.7 KB)
serial-console.txt (633 KB)

19

Hi, Trumany, there are 2 SN of the modules that are successfully to run rel-27.1:
0322417006207
0422018036013

20

Hi ericbin,

For the ethernet issue could you try to use jetpack3.1 and see if it is always reproducible?