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

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

dejans — Thu, 18 Apr 2024 09:17:31 GMT

Hi,

It could be useful to see which result you get using snippets. Please try to use snippets when building you application with west to check if you get the same result. Are you able to get modem trace this way or still seeing the same error?

Best regards,
Dejan

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

purushothaman — Wed, 17 Apr 2024 15:13:01 GMT

Hi,

Regarding the modem trace configuration options, I followed the steps outlined in the blog post you provided and ensured that the two config options are added to my project configuration. However, upon flashing the code, I encountered the following error:

07:21:02.703	Error when creating trace: unable to locate db directory plugin path: C:\Users\pmariyappan\.nrfconnect-apps\node_modules\pc-nrfconnect-cellularmonitor\node_modules\@nordicsemiconductor\nrf-monitor-lib-js\Release\win32-x64\nrfml-insight-source.nrfml.

Could you please provide guidance on how to resolve this error and successfully create the modem trace?. Any insights or suggestions you can offer would be greatly appreciated.

Additionally, in second ticket response, you mentioned providing additional input about modem trace with snippets using the west build. I will also give this approach a try concurrently to see if it resolves the issue.

Furthermore, regarding the issue with AWS IoT connectivity, I understand that modem trace may provide valuable insights. Once the modem trace is successfully configured, I would appreciate any guidance or suggestions on why AWS IoT is not connecting.

If there are any alternative or simpler code examples or way available for connecting to AWS IoT, I would find it immensely helpful if you could share them.

Thank you once again for your assistance and support.

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

dejans — Wed, 17 Apr 2024 11:30:48 GMT

Hi,

Thank you for providing the output of mentioned AT commands (in your second ticket). We will look into it.

Regarding modem trace, could you verify that 2 config options shown below are added to your project configuration?

CONFIG_NRF_MODEM_LIB_TRACE=y
CONFIG_AT_HOST_LIBRARY=y

You can read through this blog post and check that you have not skipped some steps.

Best regards,
Dejan

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

dejans — Tue, 16 Apr 2024 11:59:02 GMT

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

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

purushothaman — Mon, 15 Apr 2024 11:31:54 GMT

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?

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

dejans — Fri, 12 Apr 2024 08:19:28 GMT

Hi,

Thank you for additional information and clarification.

[quote user="dejans"]Have you checked that you built the sample for _ns target as specified in the AWS IoT sample requirements?[/quote]

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

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

purushothaman — Thu, 11 Apr 2024 13:56:50 GMT

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.

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

dejans — Thu, 11 Apr 2024 12:32:17 GMT

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