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

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

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

  • I should have been clearer. After

    mkdir ncs
    cd ncs
    west init -m https://github.com/NordicPlayground/fw-nrfconnect-nrf
    West already initialized. Aborting.
    dir
    

    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.

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

    I'm really sorry you feel this way, sir. I can understand the frustration, given the experience. 

    I am here to help you get this running, and will do what I can from here in Norway. Would you like me to put you in contact with our sales team? They have several experienced FAE's who can assist you with the issue. 

    CWallach said:
    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 

     There are several tested and verified guides available in DevZone, and have helped several people.

    As mentioned we are working on getting more tutorials out to our customers, but have not been able to gather all guides into one yet. Please be patient and use DevZone as much as possible.

    CWallach said:
    The nrf9160 is not ready for production use.

     Yes, you are correct. The device is still not in production but available for public sampling, so you can test and verify your design before production devices are available. Given that the nRF9160 is completely new for Nordic Semiconductor, we are using this time to learn and get an overview of what customer needs. This is why you are seeing so many issues as we using this as a way to remove all bugs in code and silicon.

    Nordic Semiconductor did have the same issues when moving from legacy 8-bit devices to 32-bit nRF51 and nRF52.


    Back your issue

    Since you are getting "West already initialized. Aborting." this means that the folder has been initialized somehow. I suggest that you make a new folder, this time call it NCS2. Following these commands:

    mkdir NCS2 && cd NCS2
    
    west init -m https://github.com/NordicPlayground/fw-nrfconnect-nrf
    
    cd nrf
    
    west update

    There really should not be any issues with this as I am using the command prompt in Windows 10 to do the same. 


    Kind regards,
    Øyvind

  • One major problem is that the modem firmware shipped in the 0.8.2 and 0.8.5 nRF9160 development boards is broken and has to to be replaced.

  • Not sure what you mean with broken. Can you please elaborate? If the board needs to be replaced, then I urge you to do this. Where did you get the board from? Your local RSM will be able to provide you with a new board if needed.


    The newest modem FW fixes known issues that we have seen and received from customers.

    If you have never updated the modem FW, you can download the latest modem FW from the nRF9160 download page:

    Once downloaded, please extract the file (current file is mfwnrf916007029alpha.zip) to a known location.

    1. Read the README.txt.
    2. Inside the mfwnrf916007029alpha folder, there is a new .zip file (nrf9160_mdm_dfu.zip) which includes the DFU tool to update the modem. Please unzip this as well, and follow the instructions found in  README.rst in the nrf9160_mdm_dfu.
    3. Once installed you should be able to run the command 
      nrf9160_mdm_dfu --update

    Please let me know how this works with your board!

    Kind regards,
    Øyvind

  • I had the exact same problem, renaming the folder did not work. The solution that worked for me was to uninstall west, delete the .west folder and install west again and running the commands suggested in the getting started guide. So if anyone have the same problem you can try this.

    /Samuel

Reply Children
Related