Failure in creating device certificate & provisioning it

RE: Failure in creating device certificate & provisioning it

Charlie — Wed, 22 Jun 2022 12:32:36 GMT

Hi Pramod,

I try to organize some resources to help you do a remote debug, but I did not get any reply from our development team expert by far.

I feel really sorry for the delay due to summer vacation time coming.

Best regards,

Charlie

RE: Failure in creating device certificate & provisioning it

PKK — Tue, 21 Jun 2022 13:56:34 GMT

Already did, and also deleted, and did fresh git pull. Are you part of development team ? if so, I am willing to give you remote access to figure out what is happening.

RE: Failure in creating device certificate & provisioning it

Charlie — Tue, 21 Jun 2022 13:39:54 GMT

Hi Pramod,

Unfortunately, I did not have any chance to repeat this issue by far, are you able to try this process with a completely new ubuntu installation? Maybe this will help to find some clues.

Best regards,

Charlie

RE: Failure in creating device certificate & provisioning it

PKK — Tue, 21 Jun 2022 12:06:51 GMT

@charlie-shao Any update ?

RE: Failure in creating device certificate & provisioning it

PKK — Mon, 20 Jun 2022 09:38:54 GMT

using Zypher tool Monitor, we can access the port file, so its only create certificate command which can't read

[00:07:05.779,846] <inf> event_manager: DATA_EVT_NEIGHBOR_CELLS_DATA_SEND
Encoded message:
{
	"roam":	{
		"v":	{
			"rsrp":	-87
		},
		"ts":	1655717472102
	},
	"bat":	{
		"v":	5066,
		"ts":	1655717472231
	}
}
[00:07:05.805,145] <dbg> data_module: data_encode: Data encoded successfully
[00:07:05.812,713] <dbg> data_module: data_list_add_pending: Pending data added: 0x2001b400
[00:07:05.821,655] <inf> event_manager: DATA_EVT_DATA_SEND
[00:07:05.829,040] <dbg> cloud_codec: cloud_codec_encode_batch_data: No data to encode, JSON string empty...
[00:07:05.839,477] <dbg> data_module: data_encode: No batch data to encode, ringbuffers are empty
[00:07:05.849,975] <dbg> cloud_module: neighbor_cells_data_send: Neighbor cell data sent, data pointer: 0x2001b720
[00:07:05.860,931] <inf> event_manager: CLOUD_EVT_DATA_ACK
[00:07:05.867,797] <dbg> data_module: data_ack: Pending data ACKed: 0x2001b720
[00:07:05.876,464] <dbg> cloud_module: data_send: Data sent, data pointer: 0x2001b400
[00:07:05.884,918] <inf> event_manager: CLOUD_EVT_DATA_ACK
[00:07:05.891,540] <dbg> data_module: data_ack: Pending data ACKed: 0x2001b400
+CSCON: 1
[00:07:05.963,531] <dbg> modem_module: lte_evt_handler: RRC mode: Connected
GS[00:07:07.056,365] <dbg> azure_iot_hub_integration: azure_iot_hub_event_handler: AZURE_IOT_HUB_EVT_TWIN_RESULT_SUCCESS
N=1+CSCON: 0
[00:07:10.387,420] <dbg> modem_module: lte_evt_handler: RRC mode: Idle

AT+C[00:07:30.325,225] <dbg> watchdog: primary_feed_worker: Feeding watchdog
GSN=1
AT+CGSN=1
exit

RE: Failure in creating device certificate & provisioning it

PKK — Mon, 20 Jun 2022 08:59:19 GMT

Hi Charlie,

I am not sure, what are you askign for, AT commonds work through NRF LTE LINK Monitor fine with current hex file and also with AT_host hex file, but command to generate device certificate fails with same error in both cases.

Do you think if I give you remote to the system, will it help you ?

RE: Failure in creating device certificate & provisioning it

Charlie — Fri, 17 Jun 2022 13:44:36 GMT

Hi Pramod,

Does flashing the AT host manually work? And can you run AT commands? like AT+CGSN=1

https://github.com/NordicSemiconductor/at_host-hex

Best regards,

Charlie

RE: Failure in creating device certificate & provisioning it

PKK — Thu, 16 Jun 2022 19:21:39 GMT

If I use USB in JLinkExe, it shows the board, if I just use connect /dev/ttyACM0 it cant connect

J-Link>USB
Disconnecting from J-Link...O.K.
Connecting to J-Link via USB...O.K.
Firmware: J-Link OB-K22-NordicSemi compiled Dec  3 2021 15:46:55
Hardware version: V1.00
S/N: 960042976
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
VTref=3.300V

I hope this helps you in finding the solution.

RE: Failure in creating device certificate & provisioning it

PKK — Thu, 16 Jun 2022 18:48:01 GMT

that was wrong command, correct out is

$ JLinkExe
SEGGER J-Link Commander V7.62b (Compiled Mar  8 2022 15:15:29)
DLL version V7.62b, compiled Mar  8 2022 15:15:15

Connecting to J-Link via USB...O.K.
Firmware: J-Link OB-K22-NordicSemi compiled Dec  3 2021 15:46:55
Hardware version: V1.00
S/N: 960042976
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
VTref=3.300V


Type "connect" to establish a target connection, '?' for help
J-Link>

RE: Failure in creating device certificate & provisioning it

PKK — Thu, 16 Jun 2022 18:38:52 GMT

$jlink
bash: /usr/bin/jlink: No such file or directory

Running jlink in shell gives above output, but in is installed, as you can see in attached screenshot.
Whereas if I goto ubuntu softwares through gui, it shows segger jlink installed.

RE: Failure in creating device certificate & provisioning it

Charlie — Thu, 16 Jun 2022 14:03:32 GMT

Hi Pramod,

A correct run should look like this:

$ node cli create-and-provision-device-cert --dk --debug --delete-private-key
Flasing certificate /dev/ttyACM0 
Connecting to /dev/ttyACM0
Inactivity timeout 10 seconds
/dev/ttyACM0 connected
AT Host h  
w4 4001e504 2
w4 4001e50c 1
sleep 100
rx 1000
h
w4 4001e504 1
loadfile /home/mata/nrf-asset-tracker/azure/node_modules/@nordicsemiconductor/firmware-ci-device-helpers/at_host/91dk_at_host_increased_buf.hex
rx 1000
g
exit
AT Host SEGGER J-Link Commander V7.64 (Compiled Apr  1 2022 16:09:33)
AT Host DLL version V7.64, compiled Apr  1 2022 16:09:18
AT Host J-Link Command File read successfully.
AT Host Processing script file...
AT Host J-Link>h  
AT Host J-Link connection not established yet but required for command.
AT Host Connecting to J-Link via USB...
AT Host O.K.
AT Host Firmware: J-Link OB-K22-NordicSemi compiled Dec  3 2021 15:46:55
AT Host Hardware version: V1.00
AT Host S/N: 960013621
AT Host License(s): RDI, FlashBP, FlashDL, JFlash, GDB
AT Host VTref=3.300V
AT Host Target connection not established yet but required for command.
AT Host Device "NRF9160_XXAA" selected.
AT Host Connecting to target via SWD
AT Host ConfigTargetSettings() start
AT Host ---Setting ROM table---
AT Host ConfigTargetSettings() end
AT Host Found SW-DP with ID 0x6BA02477
AT Host DPIDR: 0x6BA02477
AT Host CoreSight SoC-400 or earlier
AT Host Scanning AP map to find all available APs
AT Host AP[7]: Stopped AP scan as end of AP map has been reached
AT Host AP[0]: AHB-AP (IDR: 0x84770001)
AT Host AP[1]: AHB-AP (IDR: 0x24770011)
AT Host AP[2]: JTAG-AP (IDR: 0x12880000)
AT Host AP[3]: APB-AP (IDR: 0x54770002)
AT Host AP[4]: JTAG-AP (IDR: 0x12880000)
AT Host AP[5]: JTAG-AP (IDR: 0x12880000)
AT Host AP[6]: MEM-AP (IDR: 0x128800A1)
AT Host Iterating through AP map to find AHB-AP to use
AT Host AP[0]: Core found
AT Host AP[0]: AHB-AP ROM base: 0xE00FF000
AT Host CPUID register: 0x410FD212. Implementer code: 0x41 (ARM)
AT Host Feature set: Mainline
AT Host Found Cortex-M33 r0p2, Little endian.
AT Host FPUnit: 8 code (BP) slots and 0 literal slots
AT Host Security extension: implemented
AT Host Secure debug: enabled
AT Host CoreSight components:
AT Host ROMTbl[0] @ E00FF000
AT Host [0][0]: E000E000 CID B105900D PID 000BBD21 DEVARCH 47702A04 DEVTYPE 00 Cortex-M33
AT Host [0][1]: E0001000 CID B105900D PID 000BBD21 DEVARCH 47701A02 DEVTYPE 00 DWT
AT Host [0][2]: E0002000 CID B105900D PID 000BBD21 DEVARCH 47701A03 DEVTYPE 00 FPB
AT Host [0][3]: E0000000 CID B105900D PID 000BBD21 DEVARCH 47701A01 DEVTYPE 43 ITM
AT Host [0][5]: E0041000 CID B105900D PID 002BBD21 DEVARCH 47724A13 DEVTYPE 13 ETM
AT Host [0][6]: E0042000 CID B105900D PID 000BBD21 DEVARCH 47701A14 DEVTYPE 14 CSS600-CTI
AT Host Cortex-M33 identified.
AT Host PC = 0002FB1E, CycleCnt = 00121090
AT Host R0 = 00000000, R1 = 00000000, R2 = 00000000, R3 = 00000001
AT Host R4 = 20017208, R5 = 2001E25D, R6 = 00000000, R7 = 00000000
AT Host R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
AT Host R12= AAAAAAAA
AT Host SP(R13)= 20023E18, MSP= 20024628, PSP= 20023E18, R14(LR) = 00046153
AT Host XPSR = 61000000: APSR = nZCvq, EPSR = 01000000, IPSR = 000 (NoException)
AT Host CFBP = 02000001, CONTROL = 02, FAULTMASK = 00, BASEPRI = 00, PRIMASK = 01
AT Host MSPLIM = 20023E28
AT Host PSPLIM = 20023CE8
AT Host Security extension regs:
AT Host MSP_S = 20002EC8, MSP_NS = 20024628
AT Host MSPLIM_S = 200026C8, MSPLIM_NS = 20023E28
AT Host PSP_S = 200024A8, PSP_NS = 20023E18
AT Host PSPLIM_S = 20001588, PSPLIM_NS = 20023CE8
AT Host CONTROL_S  = 02, FAULTMASK_S  = 00, BASEPRI_S  = 00, PRIMASK_S  = 00
AT Host CONTROL_NS = 02, FAULTMASK_NS = 00, BASEPRI_NS = 00, PRIMASK_NS = 01
AT Host FPS0 = 00000000, FPS1 = 00000000, FPS2 = 00000000, FPS3 = 00000000
AT Host FPS4 = 00000000, FPS5 = 00000000, FPS6 = 00000000, FPS7 = 00000000
AT Host FPS8 = 00000000, FPS9 = 00000000, FPS10= 00000000, FPS11= 00000000
AT Host FPS12= 00000000, FPS13= 00000000, FPS14= 00000000, FPS15= 00000000
AT Host FPS16= 00000000, FPS17= 00000000, FPS18= 00000000, FPS19= 00000000
AT Host FPS20= 00000000, FPS21= 00000000, FPS22= 00000000, FPS23= 00000000
AT Host FPS24= 00000000, FPS25= 00000000, FPS26= 00000000, FPS27= 00000000
AT Host FPS28= 00000000, FPS29= 00000000, FPS30= 00000000, FPS31= 00000000
AT Host FPSCR= 00000000
AT Host J-Link>w4 4001e504 2
AT Host Writing 00000002 -> 4001E504
AT Host J-Link>w4 4001e50c 1
AT Host Writing 00000001 -> 4001E50C
AT Host J-Link>sleep 100
AT Host Sleep(100)
AT Host J-Link>rx 1000
AT Host Reset delay: 1000 ms
AT Host Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
AT Host Reset: ARMv8M core with Security Extension enabled detected.
AT Host Reset: Halt core after reset via DEMCR.VC_CORERESET.
AT Host Reset: Reset device via AIRCR.SYSRESETREQ.
AT Host J-Link>h
AT Host PC = 00002108, CycleCnt = 00000000
AT Host R0 = 00000000, R1 = 00000000, R2 = 00000000, R3 = 00000000
AT Host R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 00000000
AT Host R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
AT Host R12= AAAAAAAA
AT Host SP(R13)= 20013CE8, MSP= 20013CE8, PSP= 00000000, R14(LR) = FFFFFFFF
AT Host XPSR = F9000000: APSR = NZCVQ, EPSR = 01000000, IPSR = 000 (NoException)
AT Host CFBP = 00000000, CONTROL = 00, FAULTMASK = 00, BASEPRI = 00, PRIMASK = 00
AT Host MSPLIM = 00000000
AT Host PSPLIM = 00000000
AT Host Security extension regs:
AT Host MSP_S = 20013CE8, MSP_NS = 00000000
AT Host MSPLIM_S = 00000000, MSPLIM_NS = 00000000
AT Host PSP_S = 00000000, PSP_NS = 20023E18
AT Host PSPLIM_S = 00000000, PSPLIM_NS = 00000000
AT Host CONTROL_S  = 00, FAULTMASK_S  = 00, BASEPRI_S  = 00, PRIMASK_S  = 00
AT Host CONTROL_NS = 00, FAULTMASK_NS = 00, BASEPRI_NS = 00, PRIMASK_NS = 00
AT Host FPS0 = 00000000, FPS1 = 00000000, FPS2 = 00000000, FPS3 = 00000000
AT Host FPS4 = 00000000, FPS5 = 00000000, FPS6 = 00000000, FPS7 = 00000000
AT Host FPS8 = 00000000, FPS9 = 00000000, FPS10= 00000000, FPS11= 00000000
AT Host FPS12= 00000000, FPS13= 00000000, FPS14= 00000000, FPS15= 00000000
AT Host FPS16= 00000000, FPS17= 00000000, FPS18= 00000000, FPS19= 00000000
AT Host FPS20= 00000000, FPS21= 00000000, FPS22= 00000000, FPS23= 00000000
AT Host FPS24= 00000000, FPS25= 00000000, FPS26= 00000000, FPS27= 00000000
AT Host FPS28= 00000000, FPS29= 00000000, FPS30= 00000000, FPS31= 00000000
AT Host FPSCR= 00000000
AT Host J-Link>w4 4001e504 1
AT Host Writing 00000001 -> 4001E504
AT Host J-Link>loadfile /home/mata/nrf-asset-tracker/azure/node_modules/@nordicsemiconductor/firmware-ci-device-helpers/at_host/91dk_at_host_increased_buf.hex
AT Host Downloading file [/home/mata/nrf-asset-tracker/azure/node_modules/@nordicsemiconductor/firmware-ci-device-helpers/at_host/91dk_at_host_increased_buf.hex]...
AT Host Comparing flash   [000%]
AT 010%]
AT 010%]
AT 050%]
AT 100%] Done.
AT Host Erasing flash     [000%]
AT 040%]
AT 045%]
AT 100%] Done.
AT Host Programming flash [000%]
AT 000%]
AT 000%]
...
AT 095%]
AT 100%] Done.
AT Host J-Link: Flash download: Bank 2 @ 0x00000000: 2 ranges affected (94208 bytes)
AT Host J-Link: Flash download: Total: 2.760s (Prepare: 0.122s, Compare: 0.011s, Erase: 1.286s, Program & Verify: 1.254s, Restore: 0.085s)
AT Host J-Link: Flash download: Program & Verify speed: 73 KB/s
AT Host O.K.
AT Host J-Link>rx 1000
AT Host Reset delay: 1000 ms
AT Host Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
AT Host Reset: ARMv8M core with Security Extension enabled detected.
AT Host Reset: Halt core after reset via DEMCR.VC_CORERESET.
AT Host Reset: Reset device via AIRCR.SYSRESETREQ.
AT Host J-Link>g
AT Host J-Link>exit
AT Host Script processing completed.
/dev/ttyACM0 `��▒���/�0f2؛���q��X4t!T�Na!�"�c馗<�j)c`��q?I-~ �J!\-��    �?�r
!\���8�
!��     �
!n�apc�
���`Mѥa�%l�!��!lm%i��
!�{�*** Booting Zephyr OS build 0a904d0c176a  ***
/dev/ttyACM0 The AT host sample started
/dev/ttyACM0 AT> AT+CGSN=1
/dev/ttyACM0 +CGSN: "352656100391948"
/dev/ttyACM0 <AT +CGSN: "352656100391948"
/dev/ttyACM0 OK
/dev/ttyACM0 <AT OK
IMEI: 352656100391948 
/dev/ttyACM0 AT> AT+CGMR
/dev/ttyACM0 mfw_nrf9160_1.3.1
/dev/ttyACM0 <AT mfw_nrf9160_1.3.1
/dev/ttyACM0 OK
/dev/ttyACM0 <AT OK
/dev/ttyACM0 AT> AT+CGSN=1
/dev/ttyACM0 +CGSN: "352656100391948"
/dev/ttyACM0 <AT +CGSN: "352656100391948"
/dev/ttyACM0 OK
/dev/ttyACM0 <AT OK
/dev/ttyACM0 AT> AT+CFUN=4
/dev/ttyACM0 OK
/dev/ttyACM0 <AT OK
/dev/ttyACM0 AT> AT%CMNG=3,42,2
/dev/ttyACM0 OK
/dev/ttyACM0 <AT OK
/dev/ttyACM0 AT> AT%KEYGEN=42,2,0,"CN=352656100391948","101010000"
/dev/ttyACM0 %KEYGEN: "MIH2MIGaAgEAMBoxGDAWBgNVBAMMDzM1MjY1NjEwMDM5MTk0ODBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IABMpbExoTaobz-NQv0ZRZ5EuoxycdXS-EUv23HgPLTJwiTET_luQ5-Gkd3wJqXT4LV7TYsu6jgTj_ascf-3_n0OOgHjAcBgkqhkiG9w0
BCQ4xDzANMAsGA1UdDwQEAwIDqDAMBggqhkjOPQQDAgUAA0kAMEYCIQDiF7uUez3s29iG0S1GcuOG3B5f_yPMeAAaLhvBGQ9RsgIhAPkkgm5FxcME9d9OhbcJAsXg8n7FYH42tHW2OIUC6lf-.0oRDoQEmoQRBIVhM2dn3hQlQUDYxVDkwTViAwhgVjzEMRkIYKlggfu04JsZfjiBO
lMf2jmjvo8mJRO0ulYft6wRsxrI9oNJQqdQ73UzJP7TZTMRRtHZQaFhA-2yKi-nYYUAcZyBt0f7LvYBzC7ufZnS7xCfNkfSpqBU5WLaTGcFfZfGkIFGBIb13L5Po3QyUh-Ay34c9bJbAqQ"
/dev/ttyACM0 <AT %KEYGEN: "MIH2MIGaAgEAMBoxGDAWBgNVBAMMDzM1MjY1NjEwMDM5MTk0ODBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IABMpbExoTaobz-NQv0ZRZ5EuoxycdXS-EUv23HgPLTJwiTET_luQ5-Gkd3wJqXT4LV7TYsu6jgTj_ascf-3_n0OOgHjAcBgkqhki
G9w0BCQ4xDzANMAsGA1UdDwQEAwIDqDAMBggqhkjOPQQDAgUAA0kAMEYCIQDiF7uUez3s29iG0S1GcuOG3B5f_yPMeAAaLhvBGQ9RsgIhAPkkgm5FxcME9d9OhbcJAsXg8n7FYH42tHW2OIUC6lf-.0oRDoQEmoQRBIVhM2dn3hQlQUDYxVDkwTViAwhgVjzEMRkIYKlggfu04JsZf
jiBOlMf2jmjvo8mJRO0ulYft6wRsxrI9oNJQqdQ73UzJP7TZTMRRtHZQaFhA-2yKi-nYYUAcZyBt0f7LvYBzC7ufZnS7xCfNkfSpqBU5WLaTGcFfZfGkIFGBIb13L5Po3QyUh-Ay34c9bJbAqQ"
/dev/ttyACM0 OK
/dev/ttyACM0 <AT OK
/dev/ttyACM0 AT> AT+CFUN=1

I doubt again if your device is connected. Is the Ubuntu 20.x running natively, WSL on Windows or VM? If you run Jlink, could you see the following information?

JLinkExe

SEGGER J-Link Commander V7.64 (Compiled Apr 1 2022 16:09:33)
DLL version V7.64, compiled Apr 1 2022 16:09:18
Connecting to J-Link via USB...O.K.
Firmware: J-Link OB-K22-NordicSemi compiled Dec 3 2021 15:46:55
Hardware version: V1.00
S/N: 960013621
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
VTref=3.300V

Type "connect" to establish a target connection, '?' for help
J-Link>

Best regards,

Charlie

RE: Failure in creating device certificate & provisioning it

PKK — Thu, 16 Jun 2022 02:11:24 GMT

Yes, same response.

$ npx tsc
$ node cli create-and-provision-device-cert --dk --debug --delete-private-key
Flasing certificate /dev/ttyACM0
Connecting to /dev/ttyACM0
Inactivity timeout 10 seconds
 ERROR  create-and-provision-device-cert failed!
 ERROR  Readline is not a constructor

RE: Failure in creating device certificate & provisioning it

Charlie — Wed, 15 Jun 2022 14:26:05 GMT

then log of following commands? same as before?

# Compile code
npx tsc

# Run the command again
node cli create-and-provision-device-cert --dk --debug --delete-private-key

RE: Failure in creating device certificate & provisioning it

PKK — Wed, 15 Jun 2022 13:58:21 GMT

npm ci
npm WARN deprecated flatten@1.0.3: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See v8.dev/.../math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See v8.dev/.../math-random for details.
npm WARN deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See v8.dev/.../math-random for details.
npm WARN deprecated @azure/arm-deviceprovisioningservices@3.0.0: Please note, versions of this package with version numbers 3.0.0 and below have been deprecated as of 31-March-2022. We strongly encourage you to upgrade to version 4.0.0 or above to continue receiving updates. Refer to our deprecation policy: azure.github.io/.../policies_support.html for more details.
npm WARN deprecated @azure/arm-appservice@9.0.0: Please note, versions of this package with version numbers 9.0.0 and below have been deprecated as of 31-March-2022. We strongly encourage you to upgrade to version 10.0.0 or above to continue receiving updates. Refer to our deprecation policy: azure.github.io/.../policies_support.html for more details.

> @nordicsemiconductor/asset-tracker-cloud-azure@0.0.0-development postinstall
> husky install && check-node-version --package

husky - Git hooks installed

added 1289 packages, and audited 1290 packages in 9s

120 packages are looking for funding
run `npm fund` for details

found 0 vulnerabilities
npm notice
npm notice New minor version of npm available! 8.11.0 -> 8.12.1
npm notice Changelog: github.com/.../v8.12.1
npm notice Run npm install -g npm@8.12.1 to update!
npm notice

Is this fine OR do we need to fix anything in this before generating certificate ?

RE: Failure in creating device certificate & provisioning it

Charlie — Wed, 15 Jun 2022 13:41:58 GMT

Hi Pramond,

Ok, looks correct. Could you run the following commands and share the logs printout?

# reinstall dependencies
npm ci

# Compile code
npx tsc

# Run the command again
node cli create-and-provision-device-cert --dk --debug --delete-private-key

Best regards,

Charlie

RE: Failure in creating device certificate & provisioning it

PKK — Wed, 15 Jun 2022 11:08:46 GMT

both are installed, as follows:-

keyssin@Heimdall:~$ npm -v
8.11.0
keyssin@Heimdall:~$ node -v
v16.15.1

Pramod

RE: Failure in creating device certificate & provisioning it

Charlie — Wed, 15 Jun 2022 10:44:08 GMT

"ERROR Readline is not a constructor" shows the environment seems not set up properly. Could you check the Node.js version with the following commands?
npm -v
node -v

BR,

Charlie

RE: Failure in creating device certificate & provisioning it

PKK — Wed, 15 Jun 2022 10:22:38 GMT

Yes, device is connected and working fine. Port is also the same.

RE: Failure in creating device certificate & provisioning it

Charlie — Wed, 15 Jun 2022 10:21:37 GMT

Hi Pramod,

Did you check if the device was actually connected on /dev/ttyACM0? or it is assigned another port by the system?

Best regards,

Charlie

RE: Failure in creating device certificate & provisioning it

Charlie — Tue, 14 Jun 2022 13:40:54 GMT

Hi Pramod,

Sorry for late reply.

I will need some time to set up an environment to do the test.

At the same time, I am trying to inquire our development team for this issue and will feedback to you once there is any progress.

Best regards,
Charlie

RE: Failure in creating device certificate & provisioning it

PKK — Tue, 14 Jun 2022 11:32:00 GMT

Charlie Øyvind, Any update on this ?