|
Re: set a pin as out
Erwan Gouriou
Hi Sarvg, To configure a pin in a gpio mode, please have a look to the gpio API (you'll find exemples under tests/drivers/gpio) Chevets Erwan
Le mar. 3 nov. 2020 à 18:49, <sarvg@...> a écrit :
|
|
|
|
Bolivar, Marti
In general, that's left as an exercise for the user, as far as I know.
toggle quoted messageShow quoted text
"Nikos Karamolegkos via lists.zephyrproject.org" <nkaram=ics.forth.gr@...> writes:
Hello, I am studying this ( https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.zephyrproject.org%2Fmcuboot-security-part-1%2F&;data=04%7C01%7Cmarti.bolivar%40nordicsemi.no%7C5786fbc8d5064bb910c308d87f42f246%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C637399274195312166%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=kj5gkT%2BTyB7To%2BLmZE%2FvKojeHKTTTW3Sqd%2FL%2F91Wx50%3D&reserved=0 ) which mentions that the MCUboot is placed to immutable section of flash. How is this implemented? I can not see anywhere information about immutable MCUboot partition.
|
|
|
|
set a pin as out
sarvg@...
Hello,
How can i set an gpio pin as output? Is there any examples or tutorials for this?
For example
PIN: PB_12 in St nucleo H743zi2
Thanks for your help
sarvg
|
|
|
|
Re: zephyr API to read the nRF5340 die temperature
#nrf5340
Martin Kozusky
Hi Mohamed,
i think #include <drivers/sensor.h> with standard #include <zephyr.h> etc should work.
Martin
Dne 02.11.2020 v 9:37 Mohamed
Belaroussi napsal(a):
|
|
|
|
API meeting: agenda
Carles Cufi
Hi all,
Agenda for tomorrow. Note: the API and component naming conventions (https://github.com/zephyrproject-rtos/zephyr/issues/29569) discussion has been postponed until next week since tomorrow the availability of US-based engineers is restricted. - devicetree-based device definitions and dependency representations - PR: https://github.com/zephyrproject-rtos/zephyr/pull/29644 - Reminder and questions about: API to correlate system time with external time sources and translate uptime to wall-clock time - PR https://github.com/zephyrproject-rtos/zephyr/pull/28977 - Introduction of a new work queue - PR https://github.com/zephyrproject-rtos/zephyr/pull/29618 and then, time permitting we'd like to follow-up on pinctrl: - Pinmux and pinctrl API: Decide what the priorities for this are, and how to get to LTS with it - Issue: https://github.com/zephyrproject-rtos/zephyr/issues/22748 Teams link: https://teams.microsoft.com/l/meetup-join/19%3ameeting_NWU2MjZlYWEtZDcwMi00MWQzLTgwMjEtNDdkYjQwMjBjMmFj%40thread.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-5e334e88f6d8%22%7d https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings#zephyr-api-discussion https://github.com/zephyrproject-rtos/zephyr/projects/18 https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit Regards, Carles
|
|
|
|
Network forum agenda
Jukka Rissanen
Hi all,
There is a network forum meeting tomorrow Tue 3 Nov at 8AM PST / 17.00 CET. Current agenda: - WiFi L2 API for non-offloaded devices. See related issue at https://github.com/zephyrproject-rtos/zephyr/issues/29394 - Network testing using docker. If you have anything else you want to discuss, please let me know. Live Agenda/Minutes: https://docs.google.com/document/d/1qFsOpvbyLzhflJbbv4Vl__497pKHDoUCy9hjAveyCX0/edit?usp=sharing Shared Folder: https://drive.google.com/drive/folders/1j6d0FLeOjiMil1Ellb59AsfHdzuWdAAc?usp=sharing ___________________________________________________________ Join Microsoft Teams Meeting ( https://teams.microsoft.com/l/meetup-join/19%3ameeting_NDU5ODRkNzktZDBmNC00MDg5LWI2OWEtNzM0MGZjMDU0Yjgw%40thread.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-5e334e88f6d8%22%7d ) +1 321-558-6518 ( tel:+1 321-558-6518,,458216365# ) United States, Orlando (Toll) Conference ID: 458 216 365# Local numbers ( https://dialin.teams.microsoft.com/325d775d-c910-441e-90d0-353ebaa56cdd?id=458216365 ) | Reset PIN ( https://mysettings.lync.com/pstnconferencing ) | Learn more about Teams ( https://aka.ms/JoinTeamsMeeting ) | Meeting options ( https://teams.microsoft.com/meetingOptions/?organizerId=841a7c92-7816-4faf-9887-5e334e88f6d8&tenantId=af0096d9-700c-411a-b795-b3dd7122bad2&threadId=19_meeting_NDU5ODRkNzktZDBmNC00MDg5LWI2OWEtNzM0MGZjMDU0Yjgw@thread.v2&messageId=0&language=en-US ) Cheers, Jukka
|
|
|
|
Nikos Karamolegkos
Hello, I am studying this which mentions that the MCUboot is placed to immutable section of flash. How is this implemented? I can not see anywhere information about immutable MCUboot partition.
|
|
|
|
Re: zephyr API to read the nRF5340 die temperature
#nrf5340
Martin Kozusky
Hi,
try this, I hope it will work #define TEMP_SENSOR_NAME "TEMP_0"
int valid = 0;
const struct device *tempSensor
device_get_binding(TEMP_SENSOR_NAME);
sensor_value sensor_val;
int rc =
sensor_sample_fetch(tempSensor);
if (rc == 0) {
rc = sensor_channel_get(tempSensor, SENSOR_CHAN_DIE_TEMP,&sensor_val); }else{ valid=0; } if (rc == 0) { double temp = sensor_val.val1 + sensor_val.val2/1000000.0; //printk("Temp: %d.%d\n", sensor_val.val1, sensor_val.val2/10000); valid=1; }else{ valid=0; } you also need to enable
CONFIG_SENSOR=y
CONFIG_TEMP_NRF5=y in prj.conf
Martin
Dne 30.10.2020 v 9:16 Mohamed
Belaroussi napsal(a):
|
|
|
|
Re: zephyr API to read the nRF5340 die temperature
#nrf5340
Martin Kozusky
Hi,
I would recommend looking at samples\bluetooth\peripheral_ht\src I managed to create my code for
nrf52832 based on that sample. If you have problems with that
sample, I can paste some code here.
Martin
Dne 29.10.2020 v 15:45
mohamed.belaroussi@... napsal(a):
|
|
|
|
zephyr API to read the nRF5340 die temperature
#nrf5340
Mohamed Belaroussi
Hello, I am looking for some some nRF5340 example code that reads the nRF5340 die temperature using zephyr APIs. I've looked at previous posts but I could only find this one https://devzone.nordicsemi.com/f/nordic-q-a/56171/how-to-get-die-temperature-on-nrf52832-using-zephyr from 10 months ago that stated none existed. Thank you. Kind regards
|
|
|
|
How to Use the generic Zephyr SPI driver API without creating a full-blown zephyr-based driver
#driver
Mohamed Belaroussi
Hello, I need to communicate with an SPI device (Semtech LR1110) connected to the nordic SoC nRF5340 via its SPI peripheral. I have the driver source code but I am not sure about the steps I need to take to integrate the driver code into zephyr. I know that I have to create a device tree overlay file that defines the compatibilty compatible="nordic,nrf-spim" and specifies the MISO, MOSI, SCK and CS pins etc... &spi1 { I am not sure whether I need the following section because I do not want to create a full-blown driver in the zephyr device tree. What else do you suggest instead? adxl362@0 { }; I've read in one of the posts the following: Drivers-wise, you essentially have two options (zephyr choice is divided into two options): 1. Use the generic Zephyr driver API a. Hard way: Create a full-blown zephyr based driver - this is normally not done unless you plan to do a pull-request to the zephyr-rtos project. b. Easier way: Setup the SPI instance in your application, then add the communication protocol on-top. 2. Use the nordic specific nrfx driver directly You can use the Zephyr API to create your own driver. This includes creating Kconfig menu, device tree, and developing the sensor src and porting to use the spi.h API. This would then be a portable driver, which can theoretically run on any of the supported SPI "backends" (ie: x86, arm, xtensa, etc), but its not a straight forward process. You also have the option to use the nrfx_spim driver directly in your application, by adding CONFIG_NRFX_SPIM=y, then adding for instance CONFIG_NRFX_SPIM1=y. It looks like option 1b is the best way but I need more details, a step-by-step guide if possible would be greatly appreciated. Thank you. Kind regards Mohamed
|
|
|
|
Re: Adding an out of tree driver
Bolivar, Marti
Hi,
toggle quoted messageShow quoted text
You should just need to add it to the build system's Kconfig and CMakeLists.txt hierarchy like any other file in your module. There are worked examples in https://github.com/nrfconnect/sdk-nrf/tree/master/drivers. HTH, Martí "Lawrence King via lists.zephyrproject.org" <lawrence.king=irdeto.com@...> writes:
Adding an out of tree board is easy, I just set the variable BOARD_ROOT and the build system happily finds my_custom_board. This is nicely described by following the links from here: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.zephyrproject.org%2Flatest%2Fapplication%2Findex.html%23boards&;data=04%7C01%7Cmarti.bolivar%40nordicsemi.no%7C8f5afeb9e53b4b11f9b808d87b63fcf5%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C637395016659844236%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=HLSJWOCIo1bmNd7toN8PiWy4yPKgDoKUSgwu4dc6HMY%3D&reserved=0
|
|
|
|
Adding an out of tree driver
Adding an out of tree board is easy, I just set the variable BOARD_ROOT and the build system happily finds my_custom_board. This is nicely described by following the links from here: https://docs.zephyrproject.org/latest/application/index.html#boards
Now I want to do the same for my_custom_sensor_driver. Is there a variable I can set (like SENSOR_ROOT) that will find my out of tree sensor driver? Unfortunately the documentation at https://docs.zephyrproject.org/2.3.0/samples/application_development/out_of_tree_driver/README.html is a little sparse.
How do I include an out of tree sensor driver?
Lawrence King Principal Developer Connected Transport Market Unit +1(416)627-7302
CONFIDENTIAL: This e-mail and any attachments are confidential and intended solely for the use of the individual(s) to whom it is addressed. It can contain proprietary confidential information and be subject to legal privilege and/or subject to a non-disclosure Agreement. Unauthorized use, disclosure or copying is strictly prohibited. If you are not the/an addressee and are in possession of this e-mail, please delete the message and notify us immediately. Please consider the environment before printing this e-mail. Thank you.
|
|
|
|
Re: Heap usage monitoring
Becker Markus
There's a GitHub issue around that: https://github.com/zephyrproject-rtos/zephyr/issues/23076
toggle quoted messageShow quoted text
-----Original Message-----
From: users@... <users@...> On Behalf Of Rob Meades via lists.zephyrproject.org Sent: Montag, 26. Oktober 2020 11:01 To: Zephyr-users@... Subject: [Zephyr-users] Heap usage monitoring I have a question about heap usage monitoring. Apologies if this is the wrong place to ask, please feel free to point me elsewhere if that is the case. I'm using Zephyr on a Nordic NRF53 chip and I need to monitor how much heap was ever left available, as a minimum, after I have run my CI test suite. This is the true minimum heap ever remaining, so taking account of calls to malloc() as well as to Zephyr's memory management APIs, i.e. the true underlying heap low water mark. I could do this on NRF52 as I had the implementation of _sbrk() that FreeRTOS called into. What is the equivalent in the nRFConnect/Zephyr world? I've asked Nordic (https://devzone.nordicsemi.com/f/nordic-q-a/67495/finding-the-heap-low-water-mark-when-using-nrfconnect-zephyr) but they didn't know the answer immediately and suggested I might ask here instead. I note that there are heap stress and heap validation functions in sys/sys_heap.c but nothing in there about heap usage. You must have something of this nature to test for memory leaks: can you point me in the right direction please? Rob ________________________________ The contents of this e-mail and any attachments are confidential to the intended recipient. They may not be disclosed to or used by or copied in any way by anyone other than the intended recipient. If this e-mail is received in error, please immediately notify the sender and delete the e-mail and attached documents. Please note that neither the sender nor the sender's company accept any responsibility for viruses and it is your responsibility to scan or otherwise check this e-mail and any attachments.
|
|
|
|
API meeting: agenda
Carles Cufi
Hi all,
Agenda for today. - Kernel headers - PR: https://github.com/zephyrproject-rtos/zephyr/pull/29359#issuecomment-713598116 - API and component naming conventions - Issue: https://github.com/zephyrproject-rtos/zephyr/issues/29569 and then, time permitting we'd like to follow-up on pinctrl: - Pinmux and pinctrl API: Decide what the priorities for this are, and how to get to LTS with it - Issue: https://github.com/zephyrproject-rtos/zephyr/issues/22748 Teams link: https://teams.microsoft.com/l/meetup-join/19%3ameeting_NWU2MjZlYWEtZDcwMi00MWQzLTgwMjEtNDdkYjQwMjBjMmFj%40thread.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-5e334e88f6d8%22%7d https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings#zephyr-api-discussion https://github.com/zephyrproject-rtos/zephyr/projects/18 https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit Regards, Carles
|
|
|
|
Heap usage monitoring
Rob Meades
I have a question about heap usage monitoring. Apologies if this is the wrong place to ask, please feel free to point me elsewhere if that is the case.
I'm using Zephyr on a Nordic NRF53 chip and I need to monitor how much heap was ever left available, as a minimum, after I have run my CI test suite. This is the true minimum heap ever remaining, so taking account of calls to malloc() as well as to Zephyr's memory management APIs, i.e. the true underlying heap low water mark. I could do this on NRF52 as I had the implementation of _sbrk() that FreeRTOS called into. What is the equivalent in the nRFConnect/Zephyr world? I've asked Nordic (https://devzone.nordicsemi.com/f/nordic-q-a/67495/finding-the-heap-low-water-mark-when-using-nrfconnect-zephyr) but they didn't know the answer immediately and suggested I might ask here instead. I note that there are heap stress and heap validation functions in sys/sys_heap.c but nothing in there about heap usage. You must have something of this nature to test for memory leaks: can you point me in the right direction please? Rob
|
|
|
|
Nikos Karamolegkos
I solved the issue. The size should be multiple of 4096 (sector
size). An other problem that I am facing is that when I run the
lwm2m-client over openthread and the last address of the program
is 0x591f3 (the first address is 0x0) if I erase a random sector
(after the last address) of the memory using pyocd i.e pyocd
erase -t nrf52840 --sector 0x64000, I observe that the
client loses the connection with the server. Is there any bug or I
am missing something? Are any credentials stored somewhere in
flash? Thank you On 10/16/20 2:20 PM, Nikos Karamolegkos
wrote:
Hello, I have made a device DTS overlay file to create my partitions in flash, so I have 3 different partitions (banks) lets say A, B, C respectively. It seems to work. However, each time I am trying to use flash_area_erase to erase the entire bank (for example delete C bank when running the A bank) I am getting error -22 (EINVAL). I tries to use the function flash_erase but I have the same errors. Also, I tried to erase some bytes (e.g 64) but the error remains. I printed the fa->fa_size and fa->fa_off variables and are correct. Any suggestions? -- Nikos Karamolegkos R & D engineer at ICS-FORTH Telecommunications and Networks Lab (TNL)
|
|
|
|
Nikos Karamolegkos
Does zephyr only supports PSK for the DTLS (e.g echo client,
lwm2m client). I haven't seen anything about RPK using ECC. On 7/20/20 5:48 PM, Stefan Hristozov
wrote:
Hi all, -- Nikos Karamolegkos R & D engineer at ICS-FORTH Telecommunications and Networks Lab (TNL)
|
|
|
|
Zephyr SDK 0.12.0-beta-1 available for testing
Kumar Gala
Hi,
Latest version of the SDK can be found here: https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.12.0-beta-1 Please download and try things out and report any issues. Please report issues here: https://github.com/zephyrproject-rtos/sdk-ng/issues Known issues (these are on the Zephyr side): * some xtensa platforms may need updating w/regards to Zephyr & Xtensa HAL [ https://github.com/zephyrproject-rtos/zephyr/pull/23142 ] * known issue with arm64 and linking C++ & newlib: [ https://github.com/zephyrproject-rtos/zephyr/issues/28650 ] Changes since the last release (alpha-1): • Fix for running SDK on CentOS • change to install scripts to allow automated install • RiscV PMP fixes backported from upstream qemu • Bossa support for SAM4L - k
|
|
|
|
forum.contas@...
Ok, found the issue:
It was do to pin mapping naming. I was assuming that the pinmaps in Arduino D5, D6, and so on, corresponded to a direct GPIO map, so D5->GPIO_5 and so on... and that's not true. After using the correct pin number on Zephyr, it works as it should.
|
|
|
