This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Simple AT doesn't seem to boot

Hi!,

I'm trying to use simple_at program from https://github.com/Rallare/fw-nrfconnect-nrf2/tree/nrf9160_samples/samples/nrf9160/simple_at.

I erase all, then program secure_boot, then simple_at and reset, but it stops when showing "***** Booting Zephyr OS v1.13.99-ncs2 *****", and it doesn't show the first printk from app_socket_start nor accept AT commands (it always throws "timed out")

Any help?

Thanks!

Parents
  • Some tests I've done:

    1. Erase memory
    2. Flash secureboot
    3. Flash functional firmware from the sdk (for example, asset tracker from sdk)
    4. Flash simple_at firmware 

    Result==>it continues showing the output prints of the previous firmware.

    1. Erase memory
    2. Flash secure-boot

    Result==>it continuously reboots

    1. Erase memory
    2. Flash secureboot
    3. Flash simple_at firmware

    Result==>it continuously reboots

Reply
  • Some tests I've done:

    1. Erase memory
    2. Flash secureboot
    3. Flash functional firmware from the sdk (for example, asset tracker from sdk)
    4. Flash simple_at firmware 

    Result==>it continues showing the output prints of the previous firmware.

    1. Erase memory
    2. Flash secure-boot

    Result==>it continuously reboots

    1. Erase memory
    2. Flash secureboot
    3. Flash simple_at firmware

    Result==>it continuously reboots

Children
  • Update.

    I've changed printk in simple_at to printf and now it works.

  • I cloned the latest repos today and noticed similar problems.  However, I can't get it to work.  I noticed that the areas being programmed by the sample applications do not line up with the non-secure flash memory regions:

    asset_tracker with latest cloned repo:

    Downloading ?zephyr.elf? to J-Link
    Programming 140.2 KB of addresses 00000000 ? 00023103
    Programming 2.9 KB of addresses 00023104 ? 00023caf
    J-Link: Flash download: Bank 0 @ 0x00000000: 1 range affected (86016 bytes)
    J-Link: Flash download: Total time needed: 2.598s (Prepare: 0.026s, Compare: 0.042s, Erase: 1.832s, Program: 0.688s, Verify: 0.001s, Restore: 0.007s)
    Download successful

    Is there a missing configuration?
  • Hi Juan, 

    Recent changes to the master branch has introduced breaking changes for using with Segger, where the board named for non-secure applications has changed to "nrf9160_pca10090ns". We are working on finding a solution for this issue.

    At this time, you should use the command line in order to successfully compile.

    Here's a quick method to use the command line for programming.

    Linux/MacOS:

    export ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb
    export GNUARMEMB_TOOLCHAIN_PATH="/path/to/gcc-arm-none-eabi-Qx-2018/"
    source /path/to/ncs/zephyr/zephyr-env.sh
    cd /path/to/ncs/nrf/samples/nrf9160/myproject/
    mkdir build && cd build
    cmake .. -DBOARD=nrf9160_pca10090ns -GNinja
    ninja flash
    

    Windows:

    set ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb
    set GNUARMEMB_TOOLCHAIN_PATH="c:\path\to\gcc-arm-none-eabi-Qx-2018"
    c:\path\to\ncs\zephyr\zephyr-env.cmd
    cd c:\path\to\ncs\nrf\samples\nrf9160\my_project\
    mkdir build && cd build
    cmake .. -DBOARD=nrf9160_pca10090ns -GNinja
    ninja flash
    

     

    Could you try this and see if that works better?

     

    Kind regards,

    Håkon

Related