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

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

    Can you please give me the output with the errors you are seeing when compiling? Please add the log file from the LTE Link Monitor.

    The examples following our SDK should work out of the box without any need to edit the code. How old is your board? Can you please add the IMEI number on the back of your DK?

    I tested the at_client here without any issues.

    To ensure that the SDK is installed correctly, please follow the instructions in this link. The SDK v0.3.0 is old and outdated.

    Let me know how that works for you!

    Kind regards,
    Øyvind

  • 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):
    

     
    

    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: 
    

    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
    
			
    

		
		
		
		
	
    
	
    
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
	
    

    

    • 

	



       	          
  	  
                  1                        2                        3                        4                      
    
        	       


	
			






































	

		



	












                    
        
                                	

        		

        	

                    

















	

		

    Terms of service