Attachments (2) Download All
Nordic Case Info
  • Case ID: 227553
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF9160 at_client sample project

CWallach

After much work I can build the nRF9160 at_client sample project and flash it into the development kit. Using nRF Connect, the at_client sample project  only prints the line "The AT host sample started" as per the source code (shouldn't this be "AT client sample started"?).  AT commands entered into nRF Connect timeout with no response.  Inspecting the file main.c of at_client and there is no code to read the UART and no code to parse AT commands.  I have flashed an at_client.hex file supplied by Nordic and that firmware does respond to AT commands.

Is something missing from the at_client sample project?  I would need to modify the firmware so that it can switch the UART to a data mode upon registration with the LTE data network. In order to do this I need access to the UART and AT command handlers. How do I get this and the source for the working at_client.hex file?

I'm evaluating the nRF9160 for a project and need confirmation that it can work.

Thanks

Parents
  • 0

    Due to Easter Holiday, our support team has not been fully staffed. We apologize for the late answer, and any inconvenience this may have caused.

    Hello, 

    What version of the nRF Connect SDK are you using? When was the last time you updated the nRF Connect SDK (NCS) code? Please ensure you are using the latest version of NCS. How old is the at_client.hex file you received?

    For convenience, please update your modem FW to the latest version. Click here to go to the nRF9160 download page, and scroll to nRF9160 Modem Firmware and Modem DFU Tool.


    Thanks!

    Kind regards,
    Øyvind

  • 0 in reply to Øyvind

    I'm using nRF Connect v2.6.2 and cloned the SDK on 4/11 and again on 4/18 with no different results. Is there a file with the installed version?

    On the repository at_client main.c tagged v0.3.0 has references to functions at_host_init() and at_host_process() which were removed from the latest SDK. This looks like the reason the latest at_client is broken.

  • 0 in reply to Øyvind

    There are no errors when compiling. I am using the latest SDK. I The mention of v0.3.0 was a comment. The main() function contain one line, a printk() statement, there is no code in main.c that references AT command handling. I slightly modified the printk statement to verify that I was flashing and running the code. How can it handle AT commands when there is no software do so?

    SDK IMEI #: 3526561000477995

    My local copy of the code was created with 

    west init -m https://github.com/NordicPlayground/fw-nrfconnect-nrf 

    I just did
    git pull
    and
    west update

    and rebuilt, flashed, and ran.

    The terminal screen: 

    ***** Booting Zephyr OS v1.14.99-ncs1-rc1-2-g33c06133c197 *****
    

    

    !! The AT host sample started
    

    

    

    AT_CFUN?
    

     
    

    The log screen:
    

    

    

    12:16:51.247
    

    Modem port is opened
    

    

    

    12:17:43.763
    

    Error: 'AT+CFUN? ' timed out
    

    

    

    

    

    All AT commands are ignored. Either entered by myself or by the LTE monitor when selecting one of the serial ports.
    

    

    
			
    

		
		
		
		
	
    
	
    
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
	
    

    

    • 

	

  • 
	
    



	
		
	
	



    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
												
						in reply to CWallach
					
									
    
	
    

		
		
    
					
    Hello,

    The nRF9160 is an advanced device that uses the Zephyr OS to handle events, communications etc. 
    

    CWallach said:
    The main() function contain one line, a printk() statement, there is no code in main.c that references AT command handling.
    

    Zephyr OS will configure the device according to prj.conf (Read more here):
    

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    # General config
    CONFIG_ASSERT=y
    CONFIG_TEST_RANDOM_GENERATOR=y
    # Network
    CONFIG_NETWORKING=y
    CONFIG_NET_SOCKETS=y
    CONFIG_NET_SOCKETS_OFFLOAD=y
    # BSD library
    CONFIG_BSD_LIBRARY=y
    # AT host library
    CONFIG_AT_HOST_LIBRARY=y
    CONFIG_UART_INTERRUPT_DRIVEN=y
    # Stacks and heaps
    CONFIG_MAIN_STACK_SIZE=4096
    CONFIG_HEAP_MEM_POOL_SIZE=1024
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
     
    

    Upon boot, Zephyr OS uses System Drivers that run misc. functions configured in our libraries. With this in mind, one can have a completely empty main file.
    

    

    Back to the original problem. 
    

    I downloaded the latest version (into a new folder) following the same instructions as you above, and it is working fine: 
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    ***** Booting Zephyr OS v1.14.99-ncs1-rc1-2-g33c06133c197 *****
    Flash region        Domain      Permissions
    00 0x00000 0x02000  Secure      rwxl
    01 0x02000 0x04000  Non-Secure  rwxl
    02 0x04000 0x06000  Non-Secure  rwxl
    03 0x06000 0x08000  Non-Secure  rwxl
    04 0x08000 0x0a000  Non-Secure  rwxl
    05 0x0a000 0x0c000  Non-Secure  rwxl
    06 0x0c000 0x0e000  Non-Secure  rwxl
    07 0x0e000 0x10000  Non-Secure  rwxl
    08 0x10000 0x12000  Non-Secure  rwxl
    09 0x12000 0x14000  Non-Secure  rwxl
    10 0x14000 0x16000  Non-Secure  rwxl
    11 0x16000 0x18000  Non-Secure  rwxl
    12 0x18000 0x1a000  Non-Secure  rwxl
    13 0x1a000 0x1c000  Non-Secure  rwxl
    14 0x1c000 0x1e000  Non-Secure  rwxl
    15 0x1e000 0x20000  Non-Secure  rwxl
    16 0x20000 0x22000  Non-Secure  rwxl
    17 0x22000 0x24000  Non-Secure  rwxl
    18 0x24000 0x26000  Non-Secure  rwxl
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    

    Not that I think it will do anything of difference, but have you inserted the SIM card?

    How are you compiling the project? Using Segger Embedded Studio or command line?

    Kind regards,
    Øyvind
    
			
    

		
		
		
		
	
    
	
    
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
	
    

    

    • 

	

  • 
	
    



	
		
	
	



    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
												
						in reply to Øyvind
					
									
    
	
    

		
		
    
					
    Can you please try to run the attached file?
    uicr_tcxo.hex
    

    Fullscreen
    1
    nrfjprog.exe --program uicr_tcxo.hex -f nrf91 --sectorerase --verify
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    

    Discussing the issue with my colleague, he mentioned that it could be an issue with the 32 MHz temperature compensated crystal oscillator (TCXO) register.
    
			
    

		
		
		
		
	
    
	
    
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
	
    

    

    • 

	

  • 
	
    



	
		
	
	



    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
												
						in reply to Øyvind
					
									
    
	
    

		
		
    
					
    A sim card had been inserted and it worked with s Nordic supplied file at_client.hex.
    

    I erased flash then flashed file uicr_txco.hex, ran it, then flashed the built code. No AT commands.
    

    File prj.conf has the line CONFIG_AT_HOST_LIBRARY=y plus several other AT related lines. After a Clean Solution followed by Build Solution no AT* files are built.  See the attached build log.
    

    What is the search path for  modules referenced in prj.conf ?
    

    

    



    
    
    
        Fullscreen
        build_log.txt
        Download
    
    
    
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    Building �zephyr/include/generated/driver-validation.h� from solution �build� in configuration �Common�
    1> Combining �zephyr/include/generated/driver-validation.h�
    Building �zephyr/CMakeFiles/driver_validation_h_target� from solution �build� in configuration �Common�
    Building �zephyr/driver_validation_h_target� from solution �build� in configuration �Common�
    Building �zephyr/include/generated/kobj-types-enum.h� from solution �build� in configuration �Common�
    1> Combining �zephyr/include/generated/kobj-types-enum.h�
    Building �zephyr/include/generated/otype-to-str.h� from solution �build� in configuration �Common�
    Building �zephyr/CMakeFiles/kobj_types_h_target� from solution �build� in configuration �Common�
    Building �zephyr/kobj_types_h_target� from solution �build� in configuration �Common�
    Building �zephyr/misc/generated/syscalls.json� from solution �build� in configuration �Common�
    1> Combining �zephyr/misc/generated/syscalls.json�
    Building �zephyr/include/generated/syscall_list.h� from solution �build� in configuration �Common�
    1> Combining �zephyr/include/generated/syscall_list.h�
    Building �zephyr/CMakeFiles/syscall_list_h_target� from solution �build� in configuration �Common�
    Building �zephyr/include/generated/syscall_dispatch.c� from solution �build� in configuration �Common�
    Building �zephyr/syscall_list_h_target� from solution �build� in configuration �Common�
    Building �zephyr/include/generated/syscall_macros.h� from solution �build� in configuration �Common�
    1> Combining �zephyr/include/generated/syscall_macros.h�
    Building �zephyr/CMakeFiles/syscall_macros_h_target� from solution �build� in configuration �Common�
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    

    


    
			
    

		
		
		
		
	
    
	
    
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
	
    

    

    • 

	

  • 
	
    



	
		
	
	



    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
												
						in reply to CWallach
					
									
    
	
    

		
		
    
					
    Hello,
    

    CWallach said:
    A sim card had been inserted and it worked with s Nordic supplied file at_client.hex.
    

    Ok, that means that your board is working correctly and everything is as it should be. 
    

    CWallach said:
    I erased flash then flashed file uicr_txco.hex, ran it, then flashed the built code. No AT commands.
    

    Then we have excluded that issue. 
    

    CWallach said:
    File prj.conf has the line CONFIG_AT_HOST_LIBRARY=y plus several other AT related lines. After a Clean Solution followed by Build Solution no AT* files are built.  See the attached build log.
    

    I assume you are using Segger Embedded Studio due to "Clean Solution command", Therefore, I think we should move from using Segger Embedded Studio to building using command line instead, as there have been some issues with Segger Embedded Studio (that we are aware of) and the SDK. 
    


    Please follow this tutorial. Make sure to change the folder to \nrf\samples\nrf9160\at_client\ and delete the build folder.
    

    CWallach said:
    What is the search path for  modules referenced in prj.conf ?
    

    Have a look at this guide.
    
			
    

		
		
		
		
	
    
	
    
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
	
    

    

    • 

	




Reply

    


  • 
	
    



	
		
	
	



    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
												
						in reply to CWallach
					
									
    
	
    

		
		
    
					
    Hello,
    

    CWallach said:
    A sim card had been inserted and it worked with s Nordic supplied file at_client.hex.
    

    Ok, that means that your board is working correctly and everything is as it should be. 
    

    CWallach said:
    I erased flash then flashed file uicr_txco.hex, ran it, then flashed the built code. No AT commands.
    

    Then we have excluded that issue. 
    

    CWallach said:
    File prj.conf has the line CONFIG_AT_HOST_LIBRARY=y plus several other AT related lines. After a Clean Solution followed by Build Solution no AT* files are built.  See the attached build log.
    

    I assume you are using Segger Embedded Studio due to "Clean Solution command", Therefore, I think we should move from using Segger Embedded Studio to building using command line instead, as there have been some issues with Segger Embedded Studio (that we are aware of) and the SDK. 
    


    Please follow this tutorial. Make sure to change the folder to \nrf\samples\nrf9160\at_client\ and delete the build folder.
    

    CWallach said:
    What is the search path for  modules referenced in prj.conf ?
    

    Have a look at this guide.
    
			
    

		
		
		
		
	
    
	
    
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
	
    

    

    • 





Children
	
    
	

  • 
	
    



	
		
	
	



    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
												
						in reply to Øyvind
					
									
    
	
    

		
		
    
					
    If  Segger Embedded Studio is not working correctly then it should be documented and corrected. When will it be corrected? Is much easier to debug code with the IDE.
    

    Can you provide step by step instructions for building for target nRD9160-DK via Window 10 command line?
    

    

    There is an error message on attempting to build:
    

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    C:\Users\cwallach\Projects\Heart_Hero\LTE\ncs\nrf\samples\nrf9160\at_client\build>cmake -GNinja -DBOARD=nrf9160_pca10090 ..
    -- Using application from 'C:/Users/cwallach/Projects/Heart_Hero/LTE/ncs/nrf/samples/nrf9160/at_client'
    Zephyr version: 1.14.99
    -- Found PythonInterp: C:/Users/cwallach/AppData/Local/Programs/Python/Python37/python.exe (found suitable version "3.7.3", minimum required is "3.4")
    -- Selected BOARD nrf9160_pca10090
    -- Found west: C:/Users/cwallach/AppData/Local/Programs/Python/Python37/Scripts/west.exe (found suitable version "0.5.8", minimum required is "0.5.6")
    -- Cache files will be written to: C:\Users\cwallach\AppData\Local/.cache/zephyr
    CMake Error at C:/Users/cwallach/Projects/Heart_Hero/LTE/ncs/zephyr/cmake/generic_toolchain.cmake:57 (include):
      include could not find load file:
        C:/Users/cwallach/Projects/Heart_Hero/LTE/ncs/zephyr/cmake/toolchain/cgnuarmemb/generic.cmake
    Call Stack (most recent call first):
      C:/Users/cwallach/Projects/Heart_Hero/LTE/ncs/zephyr/cmake/app/boilerplate.cmake:446 (include)
      CMakeLists.txt:9 (include)
    -- Loading C:/Users/cwallach/Projects/Heart_Hero/LTE/ncs/zephyr/boards/arm/nrf9160_pca10090/nrf9160_pca10090.dts as base
    -- Overlaying C:/Users/cwallach/Projects/Heart_Hero/LTE/ncs/zephyr/dts/common/common.dts
    CMake Error at C:/Users/cwallach/Projects/Heart_Hero/LTE/ncs/zephyr/cmake/dts.cmake:131 (message):
      command failed with return code: The system cannot find the file specified
    Call Stack (most recent call first):
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    

    

    File LTE/ncs/zephyr/cmake/toolchain/cgnuarmemb/generic.cmake exists.
    

    

    Thanks
    
			
    

		
		
		
		
	
    
	
    
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
	
    

    

    • 

	

  • 
	
    



	
		
	
	



    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
												
						in reply to CWallach
					
									
    
	
    

		
		
    
					
    Hello,
    

    We are constantly working with SES and the master branch, some have it working, others have not. Do you have the latest Segger Embedded Studio (SES)?
    

    

    My colleague has SES working on Windows 10 here, please try this solution first and see if you can get that working.
    

    If the above does not work, we'll continue with command line. From the output you attached it seems that you have not configured the build environment correctly, see this link. 

    Kind regards,
    Øyvind
    
			
    

		
		
		
		
	
    
	
    
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
	
    

    

    • 

	

  • 
	
    



	
		
	
	



    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
												
						in reply to Øyvind
					
									
    
	
    

		
		
    
					
    I am using SEGGER Embedded Studio for ARM Release 4.16  Build 2019032803.38728 Windows x64
    

    I had previously reinstalled the SDK with no change. On attempting a 3rd reinstall, as suggested in a message thread, an error resulted
    

    Fullscreen
    1
    2
    west init -m https://github.com/NordicPlayground/fw-nrfconnect-nrf
    West already initialized. Aborting.
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    

    

    There is a thread suggesting removing ZEPHYR_BASE,  tried this and still got the error.
    

    This is ridiculous.  Why not edit ALL the steps into one document along with the exact versions of all software? Then verify it works.
    

    

    Clearly the nRF9160 was released prematurely and cannot be recommended.
    

    

    

    

    

    

    

    
			
    

		
		
		
		
	
    
	
    
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
	
    

    

    • 

	

  • 
	
    



	
		
	
	



    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
												
						in reply to CWallach
					
									
    
	
    

		
		
    
					
    Clearly the nRF9160 was released prematurely and cannot be recommended.
    

    It's unfortunate that you feel it this way, and we are sorry that you feel that it is not recommended. We are aware of the issues and are constantly working with improvements. Given that the device is so complex and more advanced than previous devices, we are working to find a good solution for customers on how to use the device. Both internally and externally. Our technical support team is not working directly with the SDK and meet the same issues as the customer meet.
    

    


    Why not edit ALL the steps into one document along with the exact versions of all software? Then verify it works.
    

    

    With the answer from above in mind, this gives us some challenges when writing tutorials. The first tutorial was written right after product announcement and has unfortunately not been updated since. This has to do with our SDK team working to find a better solution on how to reduce the complexity, and that the device is still in the public sampling stage. You can follow the status on the device here.
    


    This is also why we have customers register a support case with issues they are seeing with the nRF9160, so we can give feedback to the SDK team on what is working and what is not.
    When the device reaches the production state, we will have a more stable SDK and be able to write more complete tutorials. But there will be more tutorials before then.
    

    


    I had previously reinstalled the SDK with no change. On attempting a 3rd reinstall, as suggested in a message thread, an error resulted
    

    

    Great, you have initialized west presumably with the ncs folder referred to in your previous comment. 
    In the command prompt, standing in the ncs folder, do the following:
    

    Fullscreen
    1
    2
    3
    4
    5
    cd nrf
    git pull
    west update
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    

    

    This should update to the latest. 
    

    To build a project using the command prompt in Windows 10, please do the following. 
    

      

    1. Move back to ncs folder
      2. 

    2. Navigate to the zephyr folder
      3. 

    3. In the zephyr folder, run zephyr-env.cmd

        

      1. This should set the correct path to your zephyr folder which is needed to build projects.
        2. 

      2. Run echo %zephyr_base% to ensure the path. It should print the whole path of the zephyr folder e.g. C:\ncs\zephyr
        3. 

      

      4. 

    4. Navigate to the at_clint sample project folder: nrf\samples\nrf9160\at_client

        

      1. If you have any build folders in the at_client folder, please delete these.
        2. 

      2. Make an empty build folder and navigate to this.
        3. 

      

      5. 

    5. Standing in the build folder, run the following
      Fullscreen
      1
      2
      3
      4
      5
      cmake -DBOARD=nrf9160_pca10090ns -GNinja ..
      ninja
      ninja flash
      XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

      

        

      1. This will build and flash the at_client sample along with the SPM to your nRF9160.
        2. 

      

      6. 

    



    There is a thread suggesting removing ZEPHYR_BASE,  tried this and still got the error.
    

    I am not aware of this thread/suggestion, can you please provide me a link?
    
			
    

		
		
		
		
	
    
	
    
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
	
    

    

    • 

	

  • 
	
    



	
		
	
	



    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
												
						in reply to Øyvind
					
									
    
	
    

		
		
    
					
    I should have been clearer. After
    

    Fullscreen
    1
    2
    3
    4
    5
    mkdir ncs
    cd ncs
    west init -m https://github.com/NordicPlayground/fw-nrfconnect-nrf
    West already initialized. Aborting.
    dir
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    

    No directories or files are present in the ncs directory. Nothing. A cd nrf command fails.
    

    Seriously, there has to be complete, tested, and verified guide with each of the steps along with exact software versions.  Fully debug the procedure. Verify it. Then compile it all into a  batch file. Verify it again. This 
    

    I am a software engineer with decades of experience in multiple development environments. The nrf9160 is not ready for production use.
    

    
			
    

		
		
		
		
	
    
	
    
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
	
    

    

    • 

	


		
			






































	

		



	












                    
        
                                	

        		

        	

                    

















	

		

    Terms of service