west update v1.3.1 fails

K2AAE

I installed v1.3.1 and added the sections needed to west.yml
I watched it update:
=== updating nfed (nfed):
— nfed: fetching, need revision v1.4.x
From https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers

branch v1.4.x -> FETCH_HEAD

but when I run the build it fails, can’t find the board, looking in boards it isn’t there.
– Board: circuitdojo_feather_nrf9160ns
No board named ‘circuitdojo_feather_nrf9160ns’ found

Looking in ncs/v1.3.1/nrf/boards/arm it is not there
Looking in ncs/v1.3.1/zephyr/boards/arm it is not there
I did find the board in v1.4.1/zephyr/boards/arm

Can not show the west.yml text, it goes crazy…

jaredwolff

K2AAE yea the boards didn’t get merged until 1.4.x. You can copy the boards folder in zephyr/boards/arm/ when you check it out. There were some breaking changes from 1.2 to 1.3 you can checkout this repo and download the appropriate set.

K2AAE

jaredwolff I woke up with the idea I should just look what others have posted and found a post about blinky: I fired up nRF Connect and opened the Tool Manager, select new Nordic project, v1.4.1 since others seems to be using that version and the firmware and I have is mfwv1.2.1, selected blinky and your board and clicked build. when it was done I couldn’t find anything. I opened a command prompt and did the west thing from v1.4.1\zephyr\basic\blinky and ended up with v1.4.1\zephyr\basic\blinky\build\zephyr\app_update.bin 64K file. But at the time I was looking at the file the nRF IDE told me, merged.hex which was 295K, I figured no way to load that, something not right. I reread the post about blinky and he had used nfed blinky, that source does not show in the nRF IDE.
Using west I built nfed blinky and DFU’ed it to the feather, it works!

Correction: at the end of the SEGGER nRF Connect Option Project drop box is three dots, select the directory where the source is then open the Project drop box.

Your source is not showing in the current nRF tools IDE

I have not ''read" everything at nRF about driving west but it would be a good thing for those of us with the attention span of a gnat to have a simple walk through of command line/IDE build with where the results end up and what the results are. I’ve looked around the web for a 101 on nRF but most are dated, Mac, Linux.
(I’ll take the time to do the current Windows 10 101 now that I have an idea where thing are)

Yes, breaking changes would be a polite description, I’ll look where you suggest but I doubt I have the knowledge to make fwv1.1.2 and 1.2.1 SDK work with your board. But for now Blinky is a blinking!

jaredwolff

K2AAE I recommend building from nfed rather than the SDK since I add other values in the prj.conf (like the boatloader). It saves some headaches.

Workflow is something like this:

cd project-folder/
west build -b circuitdojo_feather_nrf9160ns

This builds and puts the output into build/zephyr

app_update.bin is used by the bootloader
merged.hex should be used for programming via SWD

Programming via bootloader:

newtmgr -c serial image upload  build/zephyr/app_update.bin

Where you need to set up the serial port beforehand.

Otherwise you can run

nrfjprog --program build/zephyr/merged.hex --chiperase

west flash

That will program whatever you just compiled to your board.

In either case you need to reset your board before your code starts running.

nrjfprog -r

or if you’re using the bootloader

newtmgr -c serial reset

Make sure that you’re not connected to debug serial when using newtmgr or else transfers will fail.

Hope that helps.

K2AAE

The nfed samples are great but I need an AT interface - I can’t setup a SIM card unless I know the IMEI, if there was one in the box I can’t find it now. I’ve been waiting on the V people but I’ll try another vendor.
I’ve found I can erase the feather, program the bootloader then add the serial_lte_modem from ncs/v1.4.1/nrf/applications/serial_lte_modem here is the modified prj.conf:

#
# Copyright (c) 2019 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-BSD-5-Clause-Nordic
#
# General config
CONFIG_LOG=y
CONFIG_LOG_DEFAULT_LEVEL=3
CONFIG_STACK_SENTINEL=y
CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
CONFIG_RING_BUFFER=y

# Segger RTT
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_BACKEND_UART=n

# Network
CONFIG_NETWORKING=y
CONFIG_NET_SOCKETS=y
CONFIG_NET_NATIVE=n

# BSD library
CONFIG_BSD_LIBRARY=y
# Align the max FD entry to BSD_MAX_SOCKET_COUNT(8)
CONFIG_POSIX_MAX_FDS=8
# Enable below for modem trace
#CONFIG_BSD_LIBRARY_TRACE_ENABLED=y

# Use GPIO
CONFIG_GPIO=y
CONFIG_GPIO_NRFX=y
CONFIG_GPIO_NRF_P0=y

# UART interface
CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y
CONFIG_NRFX_TIMER2=y

# LTE link control
CONFIG_LTE_LINK_CONTROL=y
CONFIG_LTE_AUTO_INIT_AND_CONNECT=n

# Stacks and heaps
CONFIG_MAIN_STACK_SIZE=4096
CONFIG_HEAP_MEM_POOL_SIZE=16384
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=8192

# AT_CMD
# Enable AT_CMD debug for details
#CONFIG_AT_CMD_LOG_LEVEL_DBG=y

# Device power management
CONFIG_DEVICE_POWER_MANAGEMENT=y

# Enable SUPL client support
#CONFIG_SUPL_CLIENT_LIB=y

# FOTA
CONFIG_HTTP_PARSER_URL=y
CONFIG_FOTA_DOWNLOAD=y
CONFIG_FOTA_DOWNLOAD_PROGRESS_EVT=y
CONFIG_DFU_TARGET=y
CONFIG_DOWNLOAD_CLIENT=y
CONFIG_DOWNLOAD_CLIENT_STACK_SIZE=4096
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_IMG_MANAGER=y
CONFIG_FLASH=y
CONFIG_IMG_ERASE_PROGRESSIVELY=y

# Application-specific
CONFIG_SLM_LOG_LEVEL_INF=y
# Enable GPIO wakeup if sleep is expected
#CONFIG_SLM_GPIO_WAKEUP=y
# Use UART_0 (when working with PC terminal)
CONFIG_UART_0_NRF_HW_ASYNC_TIMER=2
# Use UART_2 (when working with external MCU)
#CONFIG_SLM_CONNECT_UART_2=y
#CONFIG_UART_2_NRF_HW_ASYNC_TIMER=2
# Use optional TCP/TLS Proxy
#CONFIG_SLM_TCP_PROXY=y
# Use optional UDP/DTLS Proxy
#CONFIG_SLM_UDP_PROXY=y

# Enable Zephyr application to be booted by MCUboot
CONFIG_BOOTLOADER_MCUBOOT=y

When it is done I use the bootloader to install it. I’ve done this a few times now, the last time I removed the TC2030 from the feather before loading the SLM bin.
Question, how do you ‘clean’ the build files? cmake and west do not seem to have a ‘–clean ’

K2AAE

I put the prj.conf inside of </> code but it hits the # and changes the font size I guess

I built all the samples but the sms and ran them. Reading (me reading) the SLM docs it talks about configuring uart 0 to talk to the PC as default, there is a nrf9160dk_nrf9160ns.overlay file shows 10,11,12,13 for uart 2, and in prj.conf I commented out uart 0 and un-commented uart 2 then watched the build blow up… The feather is using p0.5 & p0.6 without RTS/CTS

Is this why I can not see any AT or is the command line west build -b circuitdojo_feather_nrf9160ns making it ignore the nrf9160dk_nrf9160ns.overlay file?

K2AAE

K2AAE
I found: https://community.jaredwolff.com/d/60-serial-lte-modem-example-compilation-problem
which had https://docs.jaredwolff.com/nrf9160-serial-lte-modem-sample.html
and discovered the bin file for serial_lte_modem but I had already tried that version.
It appears that was SDK v1.3.2 because v1.4.1 has different files in the directory but I tried it anyway, nope.
I tried to figure out the fw version and SDK magic but gave up, it shows fw 1.1.4 using sdk 1.4.2 and fw 1.2.1 (feather v2) sdk 1.3.1 for fw 1.2.2 sdk 1.4.0 and 1.4.1 so how does fw 1.1.4 rank sdk 1.4.2?
If my SIM was working on the nrf9160-dk I’d try 1.1.4+1.4.2 to see if it works.
oh ya, -p = –clean

jaredwolff

K2AAE if you need an AT interface the at_client example is a good start. Also the firmware that comes shipped on the device (I sent you that HEX image earlier) allows you to issue AT commands.

jaredwolff

Actually it wasn’t you but here’s the forum link: https://community.jaredwolff.com/d/76-issue-with-dfu-mode

K2AAE

jaredwolff I get the same, Not allowed to download, I logged out and back in but Not allowed to download.

jaredwolff

K2AAE man this forum does not way to play nice sometimes!

Here’s the direct link: https://community.jaredwolff.com/assets/files/2021-02-09/1612877102-515080-v2-010421-1502-mergedhex.zip

K2AAE If anyone has installed the D:\ncs\v1.4.1\nrf\applications\serial_lte_modem OR D:\ncs\v1.4.1\nrf\samples\nrf9160\at_client
What modem firmware and bootloader and SDK and version of feather ?

What am I missing that I can’t get a bin (bootloader) or hex (jlink) image to work?
I installed bootloader V2 does that make a difference?

I think you’re trying too many things at one time. It’s hard to isolate what the problem is. I would erase the chip and re-flash the bootloader. Put it in bootloader mode and make sure you can talk to it using newtmgr. I’m assuming you’ve already used the newtmgr command successfully at some point?

Once you get the above, then you can move on to the next step which would be to build the at_client firmware and load it with newtmgr. Make sure you hit the reset button on the board after loading or issue the newtmgr -c serial reset command.

I’ll build the at_client .bin and .hex and share it here if you need to compare a working environment to what you have set up on your end.

K2AAE

I installed SDK v1.3.2, added the stuff to west.yml, edit the prj.conf and tried to build, it couldn’t find the board. v1.3.2/zephyr/boards/arm was missing the feather board, copied it from v1.4.1 and built the at software with no errors, installed and no AT response.

If anyone has installed the D:\ncs\v1.4.1\nrf\applications\serial_lte_modem OR D:\ncs\v1.4.1\nrf\samples\nrf9160\at_client
What modem firmware and bootloader and SDK and version of feather ?

What am I missing that I can’t get a bin (bootloader) or hex (jlink) image to work?
I installed bootloader V2 does that make a difference?

jaredwolff

https://community.jaredwolff.com/assets/files/2021-02-09/1612877510-577016-at-client-v141.zip

K2AAE

jaredwolff I couldn’t sleep last night so I plugged the nrf9160-dk in and using v1.4.99 build I built and ran everything that didn’t use LTE, worked great. I had already built everything in nfed but the SMS example with v1.4.1 but I must have screwed up the at and serial_lte_modem source some how in v1.4.1.

I used the pdk with your at merged.hex with nrfjprog –program merged.hex –chiperase
It happened so fast I thought something was wrong and used the nRF Connect programmer to look at the feathers memory, it was good. Shut off the PDK and used putty:
AT
OK
a first…
I guess I’ll figure out how to remove v1.4.1 (v1.3.1, 1.3.2 also) then install a clean version of v1.4.1 and add nfed with the current directions… Thanks for your help on this moving disaster I created!
I have the IMEI now.

jaredwolff

K2AAE Nice! Glad to see you’re making some progress now. 🙂

K2AAE

Using a hologram SIM:

But on the git examples I get:
D:\ncs\v1.4.1\nfed>west init -m https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers –mr main
FATAL ERROR: already initialized in D:\ncs\v1.4.1, aborting.
Note:
In your environment, ZEPHYR_BASE is set to:
D:\ncs\v1.4.1\zephyr

This forces west to search for a workspace there.
Try unsetting ZEPHYR_BASE and re-running this command.

D:\ncs\v1.4.1\nfed>

I did find the modem FW at v1.2.3 now.

jaredwolff

K2AAE you shouldn’t run west init twice. You can add nfed to the west.yml as per the setup instructions.

K2AAE

jaredwolff I found that:
https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers
I have the west.yml modified but forgot that the new way brings the git with west update
While I was trouble shooting a non existent problem I compared the UART in nfr9160-DK to the feather and noticed a CP2105 would mirror the UART setup of the DK for 1mm and 20¢.