Failure in creating device certificate & provisioning it

I am creating device certificate as per steps mentioned at 

https://nordicsemiconductor.github.io/asset-tracker-cloud-docs/saga/docs/azure/GettingStarted/DeviceCredentials.html

Create root & intermediate certificates works fine, 

But when we issue 

node cli create-and-provision-device-cert

to create device certificate & provision it, it results in failure as follows:

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

Using Ubunto 20.x lts, using asset tracker 1.9x , firmware is created fine, it also works if I generate certificate using microsoft method for testing. 

@oys Let me know if you need more information

  • 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 ?

  • 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
    

  • 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

  • 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. 

Related