Difference between revisions of "Devzone posts"

From Wiki at Neela Nurseries
Jump to: navigation, search
m (→‎Posts To Follow - not yet sorted: fds error on FLASH, error no pages.)
m (→‎^ UARTs and Multiple UARTs: - add brief description of post.)
 
(154 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
<b>Keywords:</b>  Nordic Segger python script :: [[#nn-anchor--create-nordic-project-dot-py|create_nordic_project.py]] :: create Nordic project dot py
+
<b>Keywords:</b>  Nordic Segger python script :: [[#nn-anchor--create-nordic-project-dot-py|create_nordic_project.py]] :: create Nordic project dot py :: index.asp
  
 
&nbsp;<br />
 
&nbsp;<br />
 +
&nbsp;<br />
 +
 +
--- Overview ---
  
 
This page a starting point for references (links) to Nordic Devzone posts and additional notes on their respective issues.  This page also contains posts from [https://community.jaredwolff.com/ Jared Wolff Community forum], an excellent technical resource for design matters IoT related, and also Zephyr RTOS related.
 
This page a starting point for references (links) to Nordic Devzone posts and additional notes on their respective issues.  This page also contains posts from [https://community.jaredwolff.com/ Jared Wolff Community forum], an excellent technical resource for design matters IoT related, and also Zephyr RTOS related.
 +
 +
== 2021 Overview notes to review ==
  
 
On this page indentation of URLs highlights when one post refers or links to another.
 
On this page indentation of URLs highlights when one post refers or links to another.
  
 +
Worth noting, Nordic Semi web site is organized into three domains:
 +
 +
&nbsp;
 +
<center>
 +
[https://nordicsemi.com primary Nordic Semi website] &nbsp; &nbsp; :: &nbsp; &nbsp; [https://devzone.nordicsemi.com Nordic Devzone] &nbsp; &nbsp; :: &nbsp; &nbsp; [https://infocenter.nordicsemi.com Nordic Semi Documentation]
 +
</center>
 +
&nbsp;
 +
 +
Searching for articles, tutorials and other materials in one domain does not in general appear to find or capture search results in the other two Nordic Semi site domains.  An on-line power profiling tool can be found indirectly at [https://devzone.nordicsemi.com Nordic Devzone] by entering search pattern "online power profiler".  The link to the profiler for nRF91xx family parts is:
 +
 +
<ul>
 +
*  https://devzone.nordicsemi.com/power/w/opp/3/online-power-profiler-for-lte Nordic Semi Online Power Profiler for nRF9160
 +
</ul>
 +
 +
Some related links to Nordic on-line power profiler:
 +
<ul>
 +
*  https://devzone.nordicsemi.com/power/w/opp Nordic power profilers for nRF91xx and nRF52 and 53 family SoCs and SiPs
 +
*  https://devzone.nordicsemi.com/power/w/opp/4/user-guide-lte Online power profiler user guide
 +
</ul>
 +
 +
A local wiki page is in progress as well relating to LTE modem commands, both universal ones and some of Nordic Semi's custom AT commands:
 +
 +
<ul>
 +
*  [[Lte_at_command_notes|LTE modem AT command notes]]
 +
</ul>
 +
 +
 +
A helpful summary of all firmware development tools offered by Nordic Semi:
 +
<ul>
 +
*  https://infocenter.nordicsemi.com/topic/ug_gsg_ses/UG/gsg/nrf_tools.html
 +
</ul>
 +
Nordic link to Segger and Segger Embedded Studio downloads:
 +
<ul>
 +
*  https://infocenter.nordicsemi.com/topic/ug_gsg_ses/UG/gsg/install_segger_tools.html
 +
</ul>
 +
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] Nordic Semi Guides ==
 +
 +
*  https://devzone.nordicsemi.com/guides/cellular-iot-guides/b/hardware-design/posts/getting-started-with-current-measurements-on-the-nrf9160?CommentId=b6127988-c126-4d90-a566-86596e84a0f0
 +
 +
<!-- comentario -->
 +
 +
 +
 +
== [[#top|^]] ncs Changes in Newer than 1.6.1 Release ==
 +
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/87493/at-command-interface-library-removed-in-ncs-1-9-1
 +
 +
<!-- comentario -->
 +
 +
 +
 +
== [[#top|^]] - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; ==
 +
 +
<!-- comentario -->
 +
 +
 +
 +
== [[#top|^]] Low Current Related ==
 +
2022
 +
<ul>
 +
0615
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/89013/nrf52840dk-high-current-consumption-when-using-lipo-as-power-source
 +
0607
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/88693/power-optimisation-help  nRF52840 and Zephyr power optimization
 +
 +
0415
 +
<ul>
 +
Edge triggered interrupts require GPIO IN feature enabled, draws ~30uA:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/70130/nrf9160-low-power-edge-interrupt
 +
 +
Developer request for hex file which puts nRF9160 "module" into ~7uA current use:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/49661/nrf9160-low-power
 +
<ul><!-- nRF9160 low power guides BEGIN -->
 +
Original linked low power guide:
 +
*  https://devzone.nordicsemi.com/guides/cellular-iot-guides/b/hardware-design/posts/measuring-psm-idle-current-on-the-nrf91-dk
 +
Newer guide:
 +
*  https://devzone.nordicsemi.com/guides/cellular-iot-guides/b/hardware-design/posts/getting-started-with-current-measurements-on-the-nrf9160
 +
</ul><!-- nRF9160 low power guides END -->
 +
 +
Developer working to achieve microamp current draw on custom nRF9160 based board:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/86989/nrf9160-low-power
 +
 +
Developer Parveen Palaparthi and Cortex-M33 task registers, TASKS_CONSTLAT and TASKS_LOWPWR registers.  Also Devzone engineer mentions to use 3v3 rail for VDD_GPIO over 1v8 to avoid unintended current leak in nRF9160:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/59812/m33-core-in-nrf9160-low-power-mode---constant-latency-mode
 +
 +
Post made prior to Devzone engineers recommending to create `[project_dir]/child_image/spm.conf` containing CONFIG_SERIAL=n to disable UARTs in Secure Partition Manager binary element of given Zephyr app:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/57413/nrf9160-achieving-low-power-consumption
 +
</ul>
 +
 +
<!-- espacio -->
 +
 +
0414 Thursday . . .
 +
<ul>
 +
<pre>
 +
1011  # https://infocenter.nordicsemi.com/topic/ug_ppk2/UG/ppk/measure_current_source_meter.html
 +
1012  # https://devzone.nordicsemi.com/power/w/opp/3/online-power-profiler-for-lte
 +
1013  #
 +
1015  # https://devzone.nordicsemi.com/guides/cellular-iot-guides/b/hardware-design/posts/measuring-psm-idle-current-on-the-nrf91-dk
 +
</pre>
 +
</ul>
 +
 +
<!-- espacio -->
 +
 +
0408
 +
<ul>
 +
At Nordic Devzone issuing search string "nRF9160 configure PSM and eDRX" . . .
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/63075/nrf9160-psm-and-edrx-modes
 +
Developers Shital, Hoang, Erik posting about modem PSM and eDRX modes, mention of asset_tracker nRF9160 sample app:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/52282/how-to-programing-in-nrf9160-dk-for-psm-mode-and-edrx-mode/210357#210357
 +
Need to asure Secure Partition Manager not using UART for any logging or other purpose:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/64417/nrf9160-psm-and-edrx-mode-power-consumption-test/263413#263413
 +
AT modem commands to set power saving mode parameters and eDRX params:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/52441/how-to-use-psm-and-edrx-mode-in-custom-code/211688#211688
 +
Cerca 2019 Q2, as of ncs v1.3.1 the enabling of PSM and eDRX does not leave a way for application firmware to be notified when modem wakes from power savings mode:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/57053/abiding-by-the-negotiated-psm-edrx-timing-intervals
 +
Cerca 2021 Q2, GPS use where PSM and eDRX are not available.  Plus AT commands to return whether eDRX can be used, whether PSM can be used:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/73431/latest-gps-lte-with-no-psm-or-edrx/303438#303438
 +
Mention in third or fourth reply about SIM card minimum interval needed to deactivate, with respect to eDRX setting:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/59610/psm-floor-value-double-8ua-instead-of-4ua-and-edrx-values-bigger-24ua-instead-of-19ua-compared-to-product-specifications-using-fw-1-1-1
 +
To set the CONFIG_MQTT_KEEPALIVE equal to your polling interval . . .
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/68307/enabling-edrx-or-psm-mode-with-iot-1nce-net-sim
 +
nRF9160 maximum device sleep period and maximum device reachable period:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/48027/edrx-mode-psm-mode-sleep-mode-standby-mode-active-mode-power-consumption
 +
Only necessary to set PSM and eDRX values once, LTE modem retains them, honors what values it can given mobile network provider:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/42433/edrx-psm-mode-always-on/165548#165548
 +
</ul>
 +
 +
 +
0407
 +
<ul>
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/73794/gpio-in-high-impedance---low-power/303981#303981
 +
</ul>
 +
 +
0405
 +
<ul>
 +
*  https://docs.jaredwolff.com/nrf9160-low-power-operation.html . . . "disconnect-sdo-sa0-pull-up;"
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/79303/zephyr-power-management-issues/329571#329571
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/86634/nrf52840dk-ppk-and-battery-life-estimation
 +
 +
An interesting code excerpt stumbled upon during exam of Jared Wolff's nfed v1.7.1 `active_sleep` sample app:
 +
 +
<pre>
 +
770 int lte_lc_normal(void)
 +
771 {
 +
772        return lte_lc_func_mode_set(LTE_LC_FUNC_MODE_NORMAL);
 +
773 }
 +
774
 +
775 int lte_lc_offline(void)
 +
776 {
 +
777        return lte_lc_func_mode_set(LTE_LC_FUNC_MODE_OFFLINE);
 +
778 }
 +
779
 +
780 int lte_lc_power_off(void)
 +
781 {
 +
782        return lte_lc_func_mode_set(LTE_LC_FUNC_MODE_POWER_OFF);
 +
783 }
 +
784
 +
785 int lte_lc_psm_param_set(const char *rptau, const char *rat)
 +
786 {
 +
787        if ((rptau != NULL && strlen(rptau) != 8) ||
 +
788            (rat != NULL && strlen(rat) != 8)) {
 +
789                return -EINVAL;
 +
790        }
 +
791
 +
792        if (rptau != NULL) {
 +
793                strcpy(psm_param_rptau, rptau);
 +
794                LOG_DBG("RPTAU set to %s", log_strdup(psm_param_rptau));
 +
795        } else {
 +
796                *psm_param_rptau = '\0';
 +
797                LOG_DBG("RPTAU use default");
 +
798        }
 +
799
 +
800        if (rat != NULL) {
 +
</pre>
 +
</ul>
 +
 +
 +
0404 - To reduce GPIO current draw (~270uA) on nRF5340:
 +
<ul>
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/86598/reduce-gpio-current-draw
 +
</ul>
 +
 +
 +
0315
 +
<ul>
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/69557/periodic-current-spikes-on-sleep
 +
</ul>
 +
</ul><!-- end indent for year 2022 -->
 +
 +
<!--
 +
03xx
 +
<ul>
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/69557/periodic-current-spikes-on-sleep
 +
</ul> -->
 +
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] DTS ==
 +
 +
2022
 +
<ul>
 +
1027
 +
*  https://github.com/zephyrproject-rtos/zephyr/discussions/51733 - Zephyr discussions post on iis2dh driver and I2C instance ok discovery process
 +
 +
0503
 +
<ul>
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/87540/creation-of-custom-dts-file-for-describing-custom-device-connections
 +
</ul>
 +
0623
 +
Example call to device_get_binding(), part of several lines of supporting code:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/76226/device_get_binding-keep-returning-null
 +
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/74315/how-to-use-device_get_binding
 +
</ul>
 +
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] To Configure Pins ==
 +
 +
2022
 +
<ul>
 +
0628
 +
<ul>
 +
*  [open]  https://devzone.nordicsemi.com/f/nordic-q-a/89425/how-exactly-do-you-enable-i2c0-i2c1-or-i2c3-on-the-nrf9160-dk
 +
</ul>
 +
 +
0503 <i>( <- note these dates reflect time of finding here at nn, not original post date of Devzone ticket )</i>
 +
<ul>
 +
Does nRF9160 have internal pull up resistors for i2c twim?
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/52455/does-nrf9160-have-internal-pull-up-resistors-for-i2c-twim
 +
 +
Post greater than four years old, discusses internal clocking diffs between nRF51 and nRF52 family parts:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/36881/best-practice---delay-between-setting-pin-as-input-with-pull-up-pull-down-and-reading-the-pin
 +
</ul>
 +
 +
xx-xx
 +
<ul>
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/14272/using-gpio-10-nfc-pin-to-drive-spi-sclk
 +
</ul>
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] Display Devices ==
 +
 +
GPIO and display related posts:
 +
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/89208/zephyr-ws2812-driver-undefined-reference-to-__device_dts_ord_68
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] SPI and I2C ==
 +
 +
2022
 +
<ul>
 +
1024
 +
<ul>
 +
*  [unsolved]  https://devzone.nordicsemi.com/f/nordic-q-a/79080/including-specific-sensor-header-files  . . . post related to DT_ANY_INST_ON_BUS_STATUS_OKAY issue
 +
</ul>
 +
0628
 +
<ul>
 +
*  [open]  https://devzone.nordicsemi.com/f/nordic-q-a/89429/zephyr-sdmmc_spi-c-driver-is-very-disappointing-is-there-an-alternative-choice
 +
 +
*  [open]  https://devzone.nordicsemi.com/f/nordic-q-a/89434/nrfx-spim-and-zephyr-spi
 +
</ul>
 +
</ul>
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] To Configure Pins as Analog Inputs ==
 +
 +
0331
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/73594/nrf9160-analog-input-pins/303576#303576
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] Debugging ==
 +
 +
2022
 +
<ul>
 +
1027
 +
* [] https://github.com/zephyrproject-rtos/zephyr/issues/41677#issuecomment-1011605859 . . . undefined reference to `__device_dts_ord_xx' #41677
 +
 +
1025
 +
* [open] https://devzone.nordicsemi.com/f/nordic-q-a/93239/debugging-out-of-tree-device-driver-in-nrf-connect
 +
0620
 +
* [open] https://devzone.nordicsemi.com/f/nordic-q-a/89101/debug-uart  How to send Zephyr log messages to custom UART?
 +
* [open] https://devzone.nordicsemi.com/f/nordic-q-a/87240/nrf9160-using-uart-with-printf-without-all-the-debugging-outputs-from-zephyr
 +
</ul>
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] RTT Real Time Terminal Related ==
  
−
== [[#top|^]] nRF Radio Related ==
+
2022
 +
<ul>
 +
0322
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/86100/not-able-to-use-nordic-proprietary-at-commands-on-nrf9160
 +
 
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/76957/zephyr-read-in-keys-from-the-rtt-terminal
 +
</ul>
 +
 
 +
<!-- comentario -->
 +
 
 +
== [[#top|^]] UARTs and Multiple UARTs ==
 +
 
 +
Question with dev board nRF5340DK regarding use of multiple UARTs and Bluetooth together:
 +
 
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/103034/using-uart0-and-uart1-in-the-app-cpu-with-bt-enabled-on-the-nrf5340dk
 +
 
 +
2024-03-20 WED
 +
 
 +
Devzone member Mataer asks about run time baud rate changes:
 +
 
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/109489/dynamically-change-devicetree-configuration-for-uart-in-firmware
 +
 
 +
<!-- comentario -->
 +
 
 +
== - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - - - - - - - - - - ==
 +
 
 +
<!-- comentario -->
 +
 
 +
== [[#top|^]] External Services ==
 +
 
 +
Zephyr Timing With Epoch
 +
<ul>
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/103032/zephyr-timing-with-epoch
 +
</ul>
 +
 
 +
<!-- comentario -->
 +
 
 +
== - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - - - - - - - - - - ==
 +
 
 +
<!-- comentario -->
 +
 
 +
== [[#top|^]] nRF LTE Modem and PSM Modes ==
 +
 
 +
Posts to Nordic Devzone relating to LTE modem Power Savings Mode:
 +
 
 +
0516
 +
About three years ago Norway developers discover iBasis SIM cards force Active Time period to zero, effectively disabling PSM:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/48641/psm-tau-and-at
 +
 
 +
 
 +
How to interpret bit wise encodings of PSM parameters periodic-TAU, active time, periodic-TAU extended:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/87451/role-of-active-time-in-psm-requests-granted-values
 +
 
 +
Others' posts:
 +
 
 +
2022
 +
<ul>
 +
0426
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/87330/nrf9160-not-setting-requested-active-time
 +
 
 +
0418
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/86952/different-definitions-of-parameter-periodic-tau-in-at-instruction-cpsms-and-xmonitor
 +
 
 +
0412 TUE
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/86893/weirdest-thing-i-ve-ever-experienced-in-my-life
 +
</ul>
 +
 
 +
2021
 +
<ul>
 +
1217 FRI
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/63439/nrf-cloud---two-client-certs-mqtt_evt_connack-result--111
 +
 
 +
2021-12-05 SUN
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/82416/thread-secure-dfu
  
 
2021-11-09 TUE
 
2021-11-09 TUE
Line 15: Line 391:
 
*  https://community.jaredwolff.com/d/187-getting-started-nrf9160-a-bunch-of-questions/4
 
*  https://community.jaredwolff.com/d/187-getting-started-nrf9160-a-bunch-of-questions/4
  
−
2021-10-23 SAT
+
2021-10-23 SAT (SOLVED)
 
*  https://devzone.nordicsemi.com/f/nordic-q-a/80988/thingy-91-agps-sample-tracks-satellites-but-does-not-get-fix  Thingy91 sample tracks but does not fix on satellites
 
*  https://devzone.nordicsemi.com/f/nordic-q-a/80988/thingy-91-agps-sample-tracks-satellites-but-does-not-get-fix  Thingy91 sample tracks but does not fix on satellites
 +
</ul>
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] nRF9160 Modem Libraries ==
 +
 +
2022
 +
<ul>
 +
0707
 +
 +
*  [open]  https://devzone.nordicsemi.com/f/nordic-q-a/89775/can-the-modem-library-back-end-be-directed-to-an-external-modem
 +
</ul>
 +
 +
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] AT commands ==
 +
 +
0408
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/86787/nrf9160-slm-documentation-seems-to-be-inconsistent
 +
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/63267/getting-cereg-5-fffe-ffffffff-while-disconnected-from-the-network
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] MQTT Related ==
 +
2022
 +
<ul>
 +
0509<br />
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/87728/mqtt-subscribe-and-unsolicited-messages  ticket 87728 - MQTT subscribe and unsolicited messages
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/76415/merging-application-mqtt_simple-and-gps/315628#315628 ticket 76415 - merging application mqtt_simple and gps
 +
 +
2021-12-31 FRI
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/81617/cjson-mqtt_publish-on-nrf9160
 +
 +
2021-12-22 WED
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/83058/mqtt-client---calling-nrf_getaddrinfo-couse-reset
 +
</ul>
 +
 +
2021-12-17 FRI
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/56991/aws-fota-sample-and-psm
 +
 +
https://devzone.nordicsemi.com/f/nordic-q-a/69077/nrf9160-aws_iot-sample-mqtt-topic-add-does-not-work/288602#288602
 +
<pre>
 +
zephyr-based/nrf$ grep -nr CONFIG_MQTT_CLEAN_SESSION ./*
 +
./applications/asset_tracker_v2/prj.conf:106:CONFIG_MQTT_CLEAN_SESSION=y
 +
./applications/asset_tracker/prj.conf:54:CONFIG_MQTT_CLEAN_SESSION=n
 +
./applications/asset_tracker/src/main.c:1638:#if !IS_ENABLED(CONFIG_MQTT_CLEAN_SESSION)
 +
./applications/asset_tracker/prj_qemu_x86.conf:28:CONFIG_MQTT_CLEAN_SESSION=n
 +
./applications/asset_tracker/prj_thingy91_nrf9160ns.conf:58:CONFIG_MQTT_CLEAN_SESSION=n
 +
./doc/nrf/releases/release-notes-1.4.0.rst:181:    * Replaced ``CONFIG_CLOUD_PERSISTENT_SESSIONS`` usage with Zephyr's :option:`CONFIG_MQTT_CLEAN_SESSION`.
 +
./samples/nrf9160/mqtt_simple/prj.conf:28:CONFIG_MQTT_CLEAN_SESSION=y
 +
./subsys/net/lib/nrf_cloud/src/nrf_cloud_transport.c:577:#if !defined(CONFIG_MQTT_CLEAN_SESSION)
 +
./subsys/net/lib/nrf_cloud/src/nrf_cloud_transport.c:591:#if !defined(CONFIG_MQTT_CLEAN_SESSION)
 +
./subsys/net/lib/nrf_cloud/src/nrf_cloud_transport.c:604:#if !defined(CONFIG_MQTT_CLEAN_SESSION) || defined(CONFIG_NRF_CLOUD_FOTA)
 +
./subsys/net/lib/nrf_cloud/src/nrf_cloud_transport.c:610:#if !defined(CONFIG_MQTT_CLEAN_SESSION)
 +
./subsys/net/lib/aws_iot/src/aws_iot.c:684:                                !IS_ENABLED(CONFIG_MQTT_CLEAN_SESSION) &&
 +
./subsys/net/lib/aws_iot/src/aws_iot.c:690:                IS_ENABLED(CONFIG_MQTT_CLEAN_SESSION)) {
 +
</pre>
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] FOTA Firmware Over The Air Updates ==
 +
 +
<ul>
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/101606/device-becomes-un-updatable-forever-if-wrong-s0-s1-update-image-is-transferred-in-a-two-stage-bootloader-setup
 +
</ul>
 +
 +
<!-- comentario -->
 +
 +
== - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - - - - - - - - - - ==
 +
 +
<!-- comentario -->
 +
 +
 +
== [[#top|^]] Zephyr starting function ==
 +
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/59838/why-there-is-no-main-in-zephyr-thread-sample-codes
 +
 +
<!-- comentario -->
 +
''
 +
== [[#top|^]] Zephyr and External Flash ==
 +
 +
*  https://community.jaredwolff.com/d/262-external-flash-not-playing-nice-with-networking/5
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] Zephyr kernel issues ==
 +
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/87830/k_work_submit-schedules-in-atomic-context
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] Battery Related Questions ==
 +
 +
2022
 +
<ul>
 +
0601
 +
<ul>
 +
To monitor a coin cell battery CR2032 and example schematic:
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/65417/nrf52840-coin-cell-battery-percentage-monitor
 +
</ul>
 +
</ul>
 +
 +
<!-- comentario -->
 +
 +
UICR and related issues:
 +
 +
2022
 +
<ul>
 +
0621
 +
<ul>
 +
*  [open] https://devzone.nordicsemi.com/f/nordic-q-a/89195/uicr-write-example-with-nrf9160-and-zephyr
 +
</ul>
 +
</ul>
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] Zephyr DMA and EasyDMA ==
 +
 +
Zephyr DMA and EasyDMA . . .
 +
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/90219/using-qspi-with-dma-on-nrf5340dk
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] DPPI Distributed Programmable Peripheral Interrupts ==
 +
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/79179/simple-blinky-example-with-dppi-for-nrf9160
 +
 +
A reference to DPPI driver code:
 +
*  https://github.com/nrfconnect/sdk-nrf/blob/v1.6.1/subsys/esb/esb.c#L563
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; ==
 +
 +
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] Code Test Coverage and Coverage Reports ==
 +
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/90166/enabling-coverage-reports-for-device-testing-with-nrf-connect-sdk
 +
 +
<!-- comentario -->
 +
 +
== - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - - - - - - - - - - ==
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] Zephyr Project Configuration ==
 +
 +
Section started 2023-08-16.
 +
 +
*  (open) https://devzone.nordicsemi.com/f/nordic-q-a/102918/nrf5340-zephyr-child-image-image-build-issue
 +
 +
Forum post on configuring CLion first time of use:
 +
<ul>
 +
*  https://stackoverflow.com/questions/33267305/how-do-i-set-up-clion-to-compile-and-run
 +
</ul>
 +
 +
 +
<!-- comentario -->
 +
 +
== - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - - - - - - - - - -  - - - - - - - - - - - - - - - - - - - - ==
 +
 +
<!-- comentario -->
 +
 +
== [[#top|^]] Toolchain Related ==
 +
 +
<!-- comentario -->
 +
 +
=== [[#top|^]] To Set cmake Options In SES ===
 +
 +
As of 2021-09-24, using Segger version xxx Nordic's version, this Segger IDE offers an extra menu item to open, build, flash and debug nRF SDK sample apps.  The initial dialog box which appears for this option is titled "nRF Connect Options".  Just left of the title there is a Nordic colored icon showing two links of chain, white on blue.
 +
 +
There are five input boxes, a mix of text inputs and drop down menus, and two sets of radio buttons.  The free form text input box titled "Extra CMake Build Options" is a key place to express custom configuration settings to `cmake`.  To use, for example, Zephyr's latest stable arm cross compiling toolchain in place of Nordic's close but not quite as recent chosen release of GNU ARM cross compiler toolchain, the following `cmake` option needs be entered here:
 +
 +
-DZEPHYR_TOOLCHAIN_VARIANT=zephyr
 +
 +
The default value for 'ZEPHYR_TOOLCHAIN_VARIANT' with Nordic's SDK v1.6.1 is 'gnuarmemb'.  It is not sufficient to set a variable by this name in the shell environment of Linux systems, nor is it sufficient to set a Segger global or project macro by this name equal to the string "zephyr".  This change in toolchain name or branding must be passed to `cmake` on its command line.  In Segger, we build with a button press, so the command line option is only accessible to us from certain limited place or places.  This text input box is our place to express needed custom command line options to `cmake` when working within SES.
 +
 +
 +
<!-- comment -->
 +
 +
<span id="nn-anchor--create-nordic-project-dot-py"></span>
 +
 +
=== [[#top|^]] create_nordic_project.py ===
 +
 +
<pre>
 +
ted@localhost:~/projects/zephyr-based/z4-sandbox-kionix-work/nrf/samples/nrf9160/at_client$ python3 /opt/ses-nordic/arm_segger_embedded_studio_v560_linux_x64_nordic/html/create_nordic_project.py
 +
Usage: create_nordic_project.py [-h] [--cmake-executable cmakeExecutable] [--cmake-option cmakeOption]
 +
                                [--python-executable pythonExecutable] [--ninja-executable ninjaExecutable]
 +
                                [--dtc-executable dtcExecutable]
 +
                                zephyrBaseDir toolchainDir studioDir buildDir boardDir boardName sourceDir
 +
 +
Arguments:
 +
  zephyrBaseDir      Zephyr base directory
 +
  toolchainDir      GCC toolchain directory
 +
  studioDir          Embedded Studio directory
 +
  buildDir          Build directory
 +
  boardDir          Board directory
 +
  boardName          Board name
 +
  sourceDir          Source directory
 +
 +
Optional arguments:
 +
  --help                                  Show this help message and exit
 +
  --ncs-toolchain-version versionNCS Toolchain version to use
 +
  --cmake-executable cmakeExecutable      CMake executable to use
 +
  --cmake-option cmakeOption              Add additional CMake option
 +
  --python-executable pythonExecutable    Python executable to use
 +
  --ninja-executable ninjaExecutable      Ninja executable to use
 +
  --dtc-executable dtcExecutable          DTC executable to use
 +
  --cmake-rerunRerun CMake in build folder
 +
ted@localhost:~/projects/zephyr-based/z4-sandbox-kionix-work/nrf/samples/nrf9160/at_client$
 +
</pre>
 +
 +
<!-- comment -->
 +
 +
== [[#top|^]] How to flash how to program ==
 +
 +
*  [some answers] https://devzone.nordicsemi.com/f/nordic-q-a/51740/how-can-we-flash-the-original-factory-out-of-the-box-fw-for-the-nrf9160
 +
 +
 +
<!-- comment -->
 +
 +
== [[#top|^]] Zephyr and Docker ==
 +
 +
2022
 +
<ul>
 +
0629
 +
<ul>
 +
*  [open]  https://devzone.nordicsemi.com/f/nordic-q-a/89477/project-cannot-be-built-in-a-docker-container
 +
</ul>
 +
</ul>
  
 
<!-- comment -->
 
<!-- comment -->
  
−
== Posts To Follow - not yet sorted ==
+
== [[#top|^]] - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; - - - - - &nbsp; ==
 +
 
 +
<!-- comentario -->
 +
 
 +
 
 +
 
 +
== [[#top|^]] Posts To Follow - not yet sorted ==
 +
 
 +
As a note here which will also be mentioned near the beginning of this NN wiki page, it is as of 2022-05-09 Monday possible to access any Nordic Devzone post by its number, by entering a URL of the form <b>[https://devzone.nordicsemi.com/f/nordic-q-a/1/index.asp https://devzone.nordicsemi.com/f/nordic-q-a/nnnnn/index.asp]</b>.  This works for posts all the way down to Nordic Devzone's first post, post number 1, which was posted cerca 2013.
 +
 
 +
The following posts cover interesting and in many cases likely useful topics relating to low power, edge sensing devices.  These posts however are not yet sorted by NN wiki users.  They are here for further review, possibly on a rainy day, but in either case to fulfill future technical needs:
 +
 
 +
2023
 +
<ul>
 +
0418
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/98868/ncs-mcuboot-and-nvs
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/98871/arduino_header-usage
 +
 
 +
0412
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/98672/twim-drivers-don-t-work-with-power-management-runtime-enabled
 +
 
 +
0322
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/98006/how-to-create-a-custom-yaml-file
 +
 
 +
0221
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/96915/force-network-re-registration
 +
</ul>
 +
 
 +
2022
 +
<ul>
 +
 
 +
1002 Monday
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/92559/zephyr-custom-driver-out-of-tree-i2c
 +
 
 +
0927 Tuesday
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/92383/spi-interface-for-microsd-card
 +
 
 +
0715 Friday post to Nordic Devzone regarding micro ecc . . .
 +
*  [open] &nbsp;https://devzone.nordicsemi.com/f/nordic-q-a/90050/prebuilt-micro-ecc-library
 +
 
 +
0706
 +
*  [open] &nbsp;https://devzone.nordicsemi.com/f/nordic-q-a/89725/watchdog-timer-issues-and-pullup-on-nreset  . . . nRF9160 watchdog timer issue and 10k pull up on reset line.
 +
 
 +
0630
 +
*  [reply] &nbsp;https://devzone.nordicsemi.com/f/nordic-q-a/89523/does-mdk-8-15-0-include-workaround-for-errata-136
 +
 
 +
0614
 +
*  [replies] &nbsp;https://devzone.nordicsemi.com/f/nordic-q-a/88970/nrf9160-help-needed-to-find-reset-reboot-cause  . . . Thingy91, ncs 1.6.1 adds Memfault module for RAM based logging facility
 +
 
 +
0607
 +
*  [open] &nbsp;https://devzone.nordicsemi.com/f/nordic-q-a/88696/high-drive  High current drive question for infra-red LEDs
 +
 
 +
0520
 +
*  [open] &nbsp;https://infocenter.nordicsemi.com/topic/ref_at_commands/REF/at_commands/nw_service/cpsms_set.html
 +
</ul>
 +
 
 +
 
 +
0509
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/100/how-to-determine-nrf51822-laser-mark  ". . . mark answer as accepted to make clearer for other users . . ."
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/20181/nrf52-throughput-demo-blog-post  nRF52xx data throughput
 +
 
 +
0329
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/86381/communication-between-nrf52-and-nrf91-on-the-nrf91dk
 +
 
 +
0315
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/85861/twis-stops-working-during-long-k_msleep
 +
 
 +
 
 +
2021-12-13 Monday
 +
( OPEN )<br />
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/82734/softdevice-on-custom-board
 +
 
 +
 
 +
2021-11-30
 +
( OPEN )<br />
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/82254/data-queues-crashing-zephyr-code
 +
 
 +
2021-11-22
 +
 
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/81986/littlefs-on-large-qspi-nor
 +
*  https://github.com/zephyrproject-rtos/zephyr/issues/40453
 +
 
 +
2021-11-19
 +
 
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/79660/kconfig-and-prj-conf-question
  
 
2021-11-18
 
2021-11-18
Line 98: Line 795:
  
  
 +
<!-- comment -->
 +
 +
== [[#top|^]] Posts to Follow - Offered help ==
 +
 +
2022 . . .
 +
<ul>
 +
0601
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/88510/system-off-power-consumption-is-high
 +
<ul>
 +
Not able to find 'NARODIC' in searches, but here are some nRF5 SDK references at Nordic Semi site:
 +
(1)  https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.3.0%2Findex.html
 +
(2)  https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/pwr_mgmt_example.html
 +
(3)  https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/lib_pwr_mgmt.html
 +
</ul>
 +
 +
0512
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/87883/first-i2c-code-on-nrf-connect-i-think-i-m-close
 +
*  ...
 +
 +
0510
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/87784/adding-to-the-device-tree-with-overlays---zephyr  Developer SmallerPond "adding to the device tree with overlays" question
 +
 +
0415
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/86996/on-setting-up-linux-vs-code-showing-error-in-running-command-make-gcc-gcc-multilib-g--multilib-libsdl2-dev
 +
 +
0311
 +
*  https://devzone.nordicsemi.com/f/nordic-q-a/85636/can-i-run-python-scripts-on-the-nrf52840-dk
 +
</ul>
  
 
<!-- comment -->
 
<!-- comment -->
  
−
== [[#top|^]] To Set cmake Options In SES ==
+
== [[#top|^]] Posts Underway ==
  
−
As of 2021-09-24, using Segger version xxx Nordic's version, this Segger IDE offers an extra menu item to open, build, flash and debug nRF SDK sample apps.  The initial dialog box which appears for this option is titled "nRF Connect Options".  Just left of the title there is a Nordic colored icon showing two links of chain, white on blue.
+
<!--
 +
 
 +
Read Differential adc and print the value serially using uart
 +
2 hours ago
 +
Nagaraj JP
 +
Offline
 +
Nagaraj JP
 +
0 pts.
 +
 
 +
Hi all iam trying to read the differential analog voltage between AIN0 and AIN1 which is pin0.02 and pin0.03 and print the voltage which will be in micro volts from 400 micorvolt, and since the examples in sdk uses log_flush i could not get the data or not acess any data from that, i need to acess the data and print the data using uart, can anybody help me out in this, thankyou.
 +
 
 +
 
 +
 
 +
Reply to post on 2021-11-24:
 +
 
 +
Hello Nagaraj JP,
 +
 
 +
Not sure if I can assist you, but a few details about your starting point in terms of software libraries and targeted hardware will be useful for the community here to know.  Are you working with Nordic Semi's nRF Connect SDK, such as found at https://github.com/nrfconnect/sdk-nrf/tags?  This was my starting point a few months back.  I am using Nordic's sdk-nrf release version 1.6.1.
 +
 
 +
If yes to this question you are most likely then working with a Zephyr RTOS based app.  I've seen some posts here, however, in which developers are working with a non-Zephyr code base or project.
 +
 
 +
If your application is Nordic SDK plus Zephyr based, then you may be able to get your targeted board's UART functioning quickly via the "hello world" sample app in downloaded SDK.  For myself there were several steps to download and configure the various tools and SDK software pieces, but in the end I have a `west` workspace (where `west` is, you may already know, a Python based project manager at the command line).  In that `west` workspace the `west` utility has eased the git cloning of Nordic's SDK, an associated fork of the Zephyr project, and some nice sample apps both from Nordic and from Zephyr.
 +
 
 +
In about a day's time I was able to enable any of three on-chip UARTs in my development board's microcontroller.  The "hello world" sample in [west_workspace]/zephyr/samples/hello_world contains almost no code, and its prj.conf file is effectively empty.  But as the sample app builds part of the build toolchain goes out and reads a DTS (device tree source) board file for my particular targeted board.  Capturing and reviewing the build messages, I could then study that board.dts file, and see how the UART is assigned to pins, given a default BAUD rate, and enabled in the context of Zephyr RTOS.  Those things allowed me to correctly configure my terminal emulator, and later to move between UART instances and change BAUD rate settings as needed.
 +
 
 +
The minimal source file from "hello_world" provided me an include statement which I have used many times since in development versions of code:
 +
 
 +
`#include <sys/printk.h>`
 +
 
 +
In Zephyr based apps (Zephyr 2.6.0 in my case) this include permits me to call `printk()` family functions.  Printk() seems to behave just like `printf()`.
 +
 
 +
If I have shared things you already know my apologies.  If you are just getting started in a Zephyr based project, you will likely want to study some about Device Tree Source, and the .dts and .overlay files you will and can use in Zephyr RTOS based projects.
 +
 
 +
Once you can build and see correct "hello world" output, you can start to add your own custom routines and code to that project.  To pull the sample app out of Nordic's larger SDK will require some additional project configuration steps.  Those lay outside the scope of your question, and are better answered by a couple of good tutorials and likely some further interaction with the forum community.
 +
 
 +
Hope this helps.
 +
 
 +
- Ted
 +
 
 +
 
 +
-->
  
−
There are five input boxes, a mix of text inputs and drop down menus, and two sets of radio buttons.  The free form text input box titled "Extra CMake Build Options" is a key place to express custom configuration settings to `cmake`.  To use, for example, Zephyr's latest stable arm cross compiling toolchain in place of Nordic's close but not quite as recent chosen release of GNU ARM cross compiler toolchain, the following `cmake` option needs be entered here:
+
2022-03-02 Wed
  
−
-DZEPHYR_TOOLCHAIN_VARIANT=zephyr
+
Hello CircuitDojo Community,
  
−
The default value for 'ZEPHYR_TOOLCHAIN_VARIANT' with Nordic's SDK v1.6.1 is 'gnuarmemb'.  It is not sufficient to set a variable by this name in the shell environment of Linux systems, nor is it sufficient to set a Segger global or project macro by this name equal to the string "zephyr".  This change in toolchain name or branding must be passed to `cmake` on its command line.  In Segger, we build with a button press, so the command line option is only accessible to us from certain limited place or places.  This text input box is our place to express needed custom command line options to `cmake` when working within SES.
+
In a [recent post](https://community.jaredwolff.com/d/222-nrf9160-sleep-and-low-power-control-areas/2) I inquired about low power configurations for the nRF9160 and boards based on this SiP.  Jared Wolff shared code which dynamically turns off a given UART of the SiP's application processor.  In his code there's a call to a routine named `uart_rx_disable().` I'd initially overlooked this.  Today as I try to build my application I'm blocked on a link time error "undefined reference to `'".
  
 +
Per Jared's code excerpt I have added `CONFIG_PM_DEVICE=y` to my prj.conf.  My project is based on Nordic's aws_iot sample app.  I am using the ncs SDK version 1.6.1.  Nordic's fork of Zephyr in this SDK is Zephyr release 2.6.0.
  
−
<!-- comment -->
+
Where should `uart_rx_disable()` be defined?  Am I using a too old version of ncs or Zephyr RTOS?
−
<span id="nn-anchor--create-nordic-project-dot-py"></span>
 
−
== [[#top|^]] create_nordic_project.py ==
 
  
−
<pre>
+
<!-- comentario -->
−
ted@localhost:~/projects/zephyr-based/z4-sandbox-kionix-work/nrf/samples/nrf9160/at_client$ python3 /opt/ses-nordic/arm_segger_embedded_studio_v560_linux_x64_nordic/html/create_nordic_project.py
 
−
Usage: create_nordic_project.py [-h] [--cmake-executable cmakeExecutable] [--cmake-option cmakeOption]
 
−
                                [--python-executable pythonExecutable] [--ninja-executable ninjaExecutable]
 
−
                                [--dtc-executable dtcExecutable]
 
−
                                zephyrBaseDir toolchainDir studioDir buildDir boardDir boardName sourceDir
 
  
−
Arguments:
+
== [[#top|^]] Posts To Close ==
−
  zephyrBaseDir      Zephyr base directory
 
−
  toolchainDir      GCC toolchain directory
 
−
  studioDir          Embedded Studio directory
 
−
  buildDir          Build directory
 
−
  boardDir          Board directory
 
−
  boardName          Board name
 
−
  sourceDir          Source directory
 
  
−
Optional arguments:
+
Must request Nordic Devzone engineers to close following tickets, issues answered:
−
  --help                                  Show this help message and exit
 
−
  --ncs-toolchain-version versionNCS Toolchain version to use
 
−
  --cmake-executable cmakeExecutable      CMake executable to use
 
−
  --cmake-option cmakeOption              Add additional CMake option
 
−
  --python-executable pythonExecutable    Python executable to use
 
−
  --ninja-executable ninjaExecutable      Ninja executable to use
 
−
  --dtc-executable dtcExecutable          DTC executable to use
 
−
  --cmake-rerunRerun CMake in build folder
 
−
ted@localhost:~/projects/zephyr-based/z4-sandbox-kionix-work/nrf/samples/nrf9160/at_client$
 
−
</pre>
 
  
 +
*  [ ] https://devzone.nordicsemi.com/f/nordic-q-a/83753/custom-board-i2c-device_is_ready-failing-with-init_res-5
  
  
−
<!-- comment -->
+
<!-- comentario -->

Latest revision as of 16:05, 20 March 2024

Keywords: Nordic Segger python script :: create_nordic_project.py :: create Nordic project dot py :: index.asp

 
 

--- Overview ---

This page a starting point for references (links) to Nordic Devzone posts and additional notes on their respective issues. This page also contains posts from Jared Wolff Community forum, an excellent technical resource for design matters IoT related, and also Zephyr RTOS related.

Contents

2021 Overview notes to review

On this page indentation of URLs highlights when one post refers or links to another.

Worth noting, Nordic Semi web site is organized into three domains:

 

primary Nordic Semi website     ::     Nordic Devzone     ::     Nordic Semi Documentation

 

Searching for articles, tutorials and other materials in one domain does not in general appear to find or capture search results in the other two Nordic Semi site domains. An on-line power profiling tool can be found indirectly at Nordic Devzone by entering search pattern "online power profiler". The link to the profiler for nRF91xx family parts is:

Some related links to Nordic on-line power profiler:

A local wiki page is in progress as well relating to LTE modem commands, both universal ones and some of Nordic Semi's custom AT commands:


A helpful summary of all firmware development tools offered by Nordic Semi:

Nordic link to Segger and Segger Embedded Studio downloads:


^ Nordic Semi Guides



^ ncs Changes in Newer than 1.6.1 Release



^ - - - - -   - - - - -   - - - - -   - - - - -   - - - - -   - - - - -   - - - - -   - - - - -   - - - - -   - - - - -  

^ Low Current Related

2022



^ DTS

2022


^ To Configure Pins

2022

Retrieved from "https://wiki.neelanurseries.com/index.php?title=Devzone_posts&oldid=7855"