can't get modem trace in cellular monitor for AWS sample code.

[purushothaman]

Hi,
    

I'm facing connectivity issues with my nRF9160DK board,SDK Version: 2.6.0,Modem Firmware Version: 1.3.6.while trying to connect to AWS IoT using the sample code provided. Despite following the instructions, I couldn't establish network connectivity.

Your team member suggested providing a modem trace file using the cellular monitor to diagnose the issue. However, I encountered an error when trying to enable modem trace functionality by adding CONFIG_NRF_MODEM_LIB_TRACE in the project configuration.

FAILED: zephyr/isr_tables.c zephyr/isr_tables_vt.ld zephyr/isr_tables_swi.ld C:/Users/pmariyappan/ncs/aws_iot/aws_iot_17/build/zephyr/isr_tables.c C:/Users/pmariyappan/ncs/aws_iot/aws_iot_17/build/zephyr/isr_tables_vt.ld C:/Users/pmariyappan/ncs/aws_iot/aws_iot_17/build/zephyr/isr_tables_swi.ld
cmd.exe /C "cd /D C:\Users\pmariyappan\ncs\aws_iot\aws_iot_17\build\zephyr && C:\ncs\toolchains\cf2149caf2\opt\bin\python.exe C:/Users/pmariyappan/ncs/v2.6.0/zephyr/scripts/build/gen_isr_tables.py --output-source isr_tables.c --linker-output-files isr_tables_vt.ld isr_tables_swi.ld --kernel C:/Users/pmariyappan/ncs/aws_iot/aws_iot_17/build/zephyr/zephyr_pre0.elf --intlist-section .intList --intlist-section intList --sw-isr-table --vector-table"
gen_isr_tables.py: error: multiple registrations at table_index 9 for irq 9 (0x9)
Existing handler 0x25c9f, new handler 0x25f81
Has IRQ_CONNECT or IRQ_DIRECT_CONNECT accidentally been invoked on the same irq multiple times?

ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\cf2149caf2\opt\bin\cmake.EXE' --build 'c:\Users\pmariyappan\ncs\aws_iot\aws_iot_17\build'

* The terminal process terminated with exit code: 1.
* Terminal will be reused by tasks, press any key to close it.

Without this configuration, trace functionality remains disabled, hindering our efforts to identify the connectivity issue see below screenshot just red mark in trace no further moves.

Could you please guide me on how to successfully enable modem trace functionality or suggest alternative methods to diagnose the network connectivity issue?

I've attached the document provided by your team member for your reference.

Let me know if you need any further information or logs regarding my setup and the encountered error.

Thank you for your assistance.

[dejans]

Hi,

Have you checked that you built the sample for _ns target as specified in the AWS IoT sample requirements?

It seems that there are 2 more tickets where similar/same issue has been discussed - this one, the second and the third. Could you please provide information which problem you hope to get resolved in each of these tickets and what are the differences between them?

Best regards,
Dejan

[purushothaman]

Hi dejans,

Thank you for your prompt response. I understand your concern about the multiple tickets regarding similar issues. I apologize for any confusion caused by creating multiple tickets. To clarify, my main concern across these tickets is the inability to connect to AWS IoT despite following the specified steps, particularly in building the sample for _ns target as per the AWS IoT sample requirements.

Regarding the other tickets, here's a breakdown of my concerns:

• [Ticket 1]: Difficulty establishing AWS IoT connection. In this ticket, clarification is needed on why I am trying to obtain modem trace. I am unable to get modem trace in the cellular monitor for the AWS sample code. If I add some project configurations mentioned in the documentation, I encounter errors preventing me from obtaining the expected modem trace. I seek assistance in resolving this issue.

• [Ticket 2]: Clarification on error messages encountered during connection attempts. Despite following the AWS documentation, other sample codes like NRF multiservice establish network connections and connect to NRF cloud successfully. However, with the AWS IoT sample, I am unable to establish network connections and only receive two outputs, as shown in the attached screenshot. Insights into this discrepancy and potential solutions would be greatly appreciated.

• [Ticket 3]: Inquiry about potential compatibility issues with the _ns target. Here, I have encountered confusion regarding errors. I removed the if condition (if (IS_ENABLED(CONFIG_BOARD_QEMU_X86) || IS_ENABLED(CONFIG_BOARD_NATIVE_SIM))) in the main .c file. I am uncertain about the subsequent steps required to avoid this error and successfully connect to AWS.

I appreciate your efforts to streamline the support process and ensure efficient resolution. Please let me know if you require any additional information or clarification from my end.

[dejans]

Hi,

Thank you for additional information and clarification.

dejans said:

Have you checked that you built the sample for _ns target as specified in the AWS IoT sample requirements?

To have the ability to access the modem, the sample must be built for non-secure (_ns) build target. Can you check if you have done so?

Best regards,
Dejan

[purushothaman]

Hi,
   now if i try to use cellular modem trace now im getting error 

AT command AT+CPINR="SIM PIN" failed: +CME ERROR: 0

AT command AT+CPINR="SIM PIN2" failed: +CME ERROR: 0

AT command AT+CPINR="SIM PUK" failed: +CME ERROR: 0

AT command AT+CPINR="SIM PUK2" failed: +CME ERROR:

 how to resolve this issue?

[dejans]

Hi,

You could try at_client sample and run some AT commands to check if your SIM card is working properly. AT commands are %XSYSTEMMODE, +CFUN, %XSIM, +CEREG, %MDMEV, +CIMI, %XICCID and +CNUM.

Best regards,
Dejan