|
Re: Using counter (with RTC) on
#nrf52832
Chruściński, Krzysztof
Hi Diogo,
CMake is complaining because even though COUNTER driver is enabled there is no COUNTER instance enabled. In the example there is a Kconfig (samples/drivers/counter/alarm/Kconfig) which enabled COUNTER_RTC0 for Nordic platform and you need to do the same.
Note that for other drivers enabling instances happens in Device Tree. Counter will be aligned to that at some point.
Regards, Krzysztof
From: users@... <users@...>
On Behalf Of Diogo Correia via lists.zephyrproject.org
Sent: Thursday, August 6, 2020 3:23 PM To: users@... Subject: [Zephyr-users] Using counter (with RTC) on #nRF52832
Hi there,
I've started using Zephyr OS last week, so is better to advise that there might be a tiny chance of this question being dumb. I'm trying to use the Nordic's nRF52832 RTC clock, so wrote a small piece of software (based on the samples/counter/alarm/ example). However, when trying to compile I receive the following error:
CMake Error at /home/diogo.correia/zephyrproject/zephyr/cmake/extensions.cmake:372 (add_library):
My .conf file:
#Nordic nRF52 RTT LOGGER
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n
#Counter
CONFIG_COUNTER=y
My .c file:
#include <zephyr.h>
#include <sys/printk.h>
#include <device.h>
#include <drivers/counter.h>
#if defined(CONFIG_COUNTER_RTC0)
#define TIMER DT_LABEL(DT_NODELABEL(rtc0))
#elif defined(CONFIG_COUNTER_RTC1)
#define TIMER DT_LABEL(DT_NODELABEL(rtc1))
#elif defined(CONFIG_COUNTER_RTC2)
#define TIMER DT_LABEL(DT_NODELABEL(rtc2))
#endif
struct device *counter;
struct counter_alarm_cfg alarm_config;
void init();
void counter_callback(struct device *counter_dev, u8_t chan_id, u32_t ticks, void *user_data);
void main(void)
{
init();
while(1) {
k_sleep(K_FOREVER);
}
}
void init(){
// Counter
counter = device_get_binding(TIMER);
if (counter == NULL){
printk("ERROR: %s not found.\n", TIMER);
return;
}
counter_start(counter);
alarm_config.flags = 0;
alarm_config.ticks = counter_us_to_ticks(counter, 1000000);
alarm_config.callback = counter_callback;
counter_set_channel_alarm(counter, 0, &alarm_config);
}
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
Re: #west
#west
ahmed.balata@...
attached my Dockerfile and myscript1.sh
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
Re: #west
#west
ahmed.balata@...
Thank you for your replay.
i have checked the path and it has been fixed, still it only works manually but if I take the script as entrypoint it does not work.
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
Re: #west
#west
Bolivar, Marti
Hello,
Some responses inline. "ahmed.balata via lists.zephyrproject.org" <ahmed.balata=tu-dortmund.de@...> writes: Hello,If these are really copy/pasted from the error output, then the problem seems to be that it should be "west", not "West" -- lowercase "w", that is. The other thing to check is that the west executable installed by pip is in the PATH. Use "pip3 show -f west" to find these. So for example: Location: /foo/lib/python3.8/site-packages Files: ../../../bin/west This means west is in /foo/lib/python3.8/site-packages/../../../bin/west, or /foo/bin/west Martí
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
#west
#west
ahmed.balata@...
Hello,
I want or create a docker image for Zephyr, I have a script that has west init / West Update west zephyr export ..........and the next steps. While the previous steps are in Dockerfile. when i use this script as entrypoint, i get these errors Line 9: West: command not found Line 10: West: command not found Line 11: West: command not found but if I normally execute the container and then manually execute the script in the container, I don't get any errors. How can i use such script as an entrypoint? Thank you
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
Using counter (with RTC) on
#nrf52832
Diogo Correia <diogo.correia@...>
Hi there,
I've started using Zephyr OS last week, so is better to advise that there might be a tiny chance of this question being dumb. I'm trying to use the Nordic's nRF52832 RTC clock, so wrote a small piece of software (based on the samples/counter/alarm/
example). However, when trying to compile I receive the following error:
CMake Error at /home/diogo.correia/zephyrproject/zephyr/cmake/extensions.cmake:372 (add_library):
No SOURCES given to target: drivers__counter Call Stack (most recent call first): /home/diogo.correia/zephyrproject/zephyr/cmake/extensions.cmake:349 (zephyr_library_named) /home/diogo.correia/zephyrproject/zephyr/drivers/counter/CMakeLists.txt:3 (zephyr_library) -- Build files have been written to: /home/diogo.correia/zephyrproject/zephyrLAB/build FAILED: build.ninja /usr/local/bin/cmake -S/home/diogo.correia/zephyrproject/zephyrLAB -B/home/diogo.correia/zephyrproject/zephyrLAB/build ninja: error: rebuilding 'build.ninja': subcommand failed FATAL ERROR: command exited with status 1: /usr/local/bin/cmake --build /home/diogo.correia/zephyrproject/zephyrLAB/build
My .conf file: #Nordic nRF52 RTT LOGGER
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n
#Counter
CONFIG_COUNTER=y
My .c file: #include
<zephyr.h>
#include
<sys/printk.h>
#include
<device.h>
#include
<drivers/counter.h>
#if
defined(CONFIG_COUNTER_RTC0)
#define TIMER
DT_LABEL(DT_NODELABEL(rtc0))
#elif
defined(CONFIG_COUNTER_RTC1)
#define TIMER
DT_LABEL(DT_NODELABEL(rtc1))
#elif
defined(CONFIG_COUNTER_RTC2)
#define TIMER
DT_LABEL(DT_NODELABEL(rtc2))
#endif
struct device *counter;
struct counter_alarm_cfg alarm_config;
void
init();
void
counter_callback(struct device *counter_dev,
u8_t
chan_id,
u32_t ticks,
void *user_data);
void
main(void)
{
init();
while(1) {
k_sleep(K_FOREVER);
}
}
void
init(){
// Counter
counter = device_get_binding(TIMER);
if (counter ==
NULL){
printk("ERROR: %s not found.\n",
TIMER);
return;
}
counter_start(counter);
alarm_config.flags =
0;
alarm_config.ticks =
counter_us_to_ticks(counter,
1000000);
alarm_config.callback = counter_callback;
counter_set_channel_alarm(counter,
0, &alarm_config);
}
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
West v0.7.3 released
Bolivar, Marti
Hello,
I'm announcing the release of west v0.7.3. https://pypi.org/project/west/0.7.3/ https://github.com/zephyrproject-rtos/west/tree/v0.7.3 To upgrade: Ubuntu: pip3 install --user west==0.7.3 Windows/macoS: pip3 install west==0.7.3 This is a bugfix release from v0.7.2. The main bug fixed causes 'west update' to fail in some situations when manifest imports are used. For details about this bug, see: https://github.com/zephyrproject-rtos/west/pull/415 For details about manifest imports, see: https://docs.zephyrproject.org/latest/guides/west/manifest.html#manifest-imports Full commit list since v0.7.2: Martí Bolívar (5): conftest: make it more os.PathLike friendly app: fix import error followed by update app/project: add missing f for f-string lint: flake8 fixes West v0.7.3 Thanks, Martí
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
LWM2M client to nrf582540-DK
#nrf52840
#networking
Nikos Karamolegkos
Hi all,
I have two nrf582540-dk modules and I would like to run the lwm2m client example of the link using the leshan server. How could I implement this using real device? How my 802.15.4 device will communicate with the server running on my PC? Is there any border router? I really need this. Can someone point me in the right direction? Thank you, Nikos
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
RFC: removing eeprom_slave as driver in Zephyr
Peter A. Bigot
The eeprom_slave driver accessed under CONFIG_I2C_EEPROM_SLAVE implements the I2C follower (slave) driver API. This device isn't an actual hardware driver: it's a virtual EEPROM that stores data in an instance-specific RAM buffer, with the data exposed on an I2C bus as a I2C follower device that can be controlled by another device acting as a leader (master) on that same bus.
As such it's a reasonable example of how to write an I2C follower driver, but it's not clear that it has a real use in applications: the sole in-tree reference is in the i2c_slave_api test. Unless this driver has real-world applications I intend to move this from the drivers directory into the source directory for the test that uses it. Consequently CONFIG_I2C_EEPROM_SLAVE and the device it provided will no longer be supported. If you have a use for this driver or other concerns about this please comment at: https://github.com/zephyrproject-rtos/zephyr/issues/27303 Peter
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
API meeting: agenda
Carles Cufi
Hi all,
Sorry for the late agenda. Topics for today: - RFC: downgrade i2c eeprom_slave driver to sample - Issue: https://github.com/zephyrproject-rtos/zephyr/issues/27303 - Add regulator driver infrastructure - PR: https://github.com/zephyrproject-rtos/zephyr/pull/27360 - Triage and cleanup of the in-progress column Additional items in the "Triage" column in the GitHub project may be discussed if time permits. If you want an item included in the meeting, please add it to the GitHub project. 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
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
Re: [solved] Re: SMP Server Sample: Fails to upload over BLE
Hi George:
I had no end of trouble with the built-in bluetooth adapter on my laptop. It was an Intel adapter and would only work if I moved the target Zephyr box about 15ft away from the laptop.
I changed over to using another nrf52840 board with the hci_usb sample loaded, connected to the laptop via USB. With this setup mcumgr targeted at hci1 instead of hci0 works great.
Lawrence King Principal Developer +1(416)627-7302
From: users@... <users@...>
On Behalf Of George Ruinelli
Sent: Tuesday, August 4, 2020 3:09 AM To: users@... Subject: [Zephyr-users] [solved] Re: SMP Server Sample: Fails to upload over BLE
Thanks to the support of Nick, I was able to trace it down to an issue in the MCUmgr on the PC side.
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
[solved] Re: SMP Server Sample: Fails to upload over BLE
George Ruinelli
Thanks to the support of Nick, I was able to trace it down to an issue in the MCUmgr on the PC side.
There is now an open bug report for this: https://github.com/apache/mynewt-mcumgr-cli/issues/15
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
Network forum agenda
Jukka Rissanen
Hi all,
There is a network forum meeting today 4 Aug at 8AM PDT / 17.00 CET. Agenda: - Making the new TCP stack the default. See https://github.com/zephyrproject-rtos/zephyr/pull/27208 for details. - Network stack testing. Maxwell Pro license just expired, any volunteers to start using it. Discussion how to do network testing in the future. If you have anything else you want to discuss, please let me know. Link to the 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 Cheers, Jukka
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
SMP Server Sample: Fails to upload over BLE
George Ruinelli
Hi all
I am trying to get the "SMP Server Sample" (https://docs.zephyrproject.org/latest/samples/subsys/mgmt/mcumgr/smp_svr/README.html) working. I have a nrf52840dongle_nrf52840 and successfully installed MCUboot (option #2) and the "SMP Server Sample" on it. I also have a laptop with a built-in BLE radio. I successfully can test the connection and even list the image: > mcumgr --conntype ble --connstring ctlr_name= peer_name='Zephyr' echo hello hello sudo mcumgr --conntype ble --connstring ctlr_name=peer_name='Zephyr' image listImages: image=0 slot=0 version: 0.0.0 bootable: true flags: active confirmed hash: 37a4a9403fbd0a0336152646947ccce5faf6674e3a29b4220eb2b97a2f613b9d Split status: N/A (0) How ever when I try to upload a new image, I run into n error: sudo mcumgr --conntype ble --connstring peer_name='Zephyr' image upload smp_svr.signed.bin -t 1000 B / 182.61 KiB [--------------------------------------------------------------------------------------------------] 0.00% panic: send on closed channel goroutine 493 [running]: mynewt.apache.org/newtmgr/nmxact/nmp.(*Listener).AfterTimeout.func1() /home/ubuntu/go/src/mynewt.apache.org/newtmgr/nmxact/nmp/dispatch.go:50 +0x64 created by time.goFunc /usr/lib/go-1.13/src/time/sleep.go:168 +0x44 Any Idea how this can get fixed? Sincerely George Confidentiality Notice: This e-mail is privileged and confidential and for the use of the addressee only. Should you have received this e-mail in error please notify us by replying directly to the sender or by sending a message to info@.... Unauthorised dissemination, disclosure or copying of the contents of this e-mail, or any similar action, is prohibited.
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
Re: Getting to blinky with an ESP32 board
Michael Rosen
Did you complete “Step 3: Set up the Tools” on the esp-idf getting started page? If so, you should have run the install script and installed the ESP tools on your system. Depending on where you installed them, there should be a directory at either $HOME/.espressif (or %USERPROFILE%\.espressif on windows) or somewhere else if you installed them elsewhere. Once you find them, you need to set that environment variables for using that espressif toolchain:
export ZEPHYR_TOOLCHAIN_VARIANT="espressif" export ESPRESSIF_TOOLCHAIN_PATH=<<DIRECTORY YOU FOUND EARLIER>>/tools/xtensa-esp32-elf/esp-2020r2-8.2.0/xtensa-esp32-elf/
For flashing, you’ll also need a version of esptool.py which you can get from cloning the ESP IDF then setting the path to it for Zephyr to find:
export ESP_IDF_PATH=<<PATH TO WHEREEVER YOU DOWNLOADED THE IDF TO>>
From: users@... <users@...>
On Behalf Of don.haig@...
Sent: Wednesday, July 29, 2020 3:22 PM To: users@... Subject: [Zephyr-users] Getting to blinky with an ESP32 board
I am trying out Zephyr following the "Getting Started" guide:
https://docs.zephyrproject.org/latest/getting_started/index.html#build-the-blinky-sample export ESPRESSIF_TOOLCHAIN_PATH="/path/to/xtensa-esp32-elf/"
Unfortunately, there is no "xtensa-esp32-elf/" directory that I can find.
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
Getting to blinky with an ESP32 board
don.haig@...
I am trying out Zephyr following the "Getting Started" guide: https://docs.zephyrproject.org/latest/getting_started/index.html#build-the-blinky-sample
I've installed the toolchain and I am trying to get the blinky example running on an ESP32 board. I've installed the latest stable ESP toolchain according to the instructions here: https://docs.espressif.com/projects/esp-idf/en/stable/get-started/ To set up the build environment, I apparently need to set the following environment variable: export ESPRESSIF_TOOLCHAIN_PATH="/path/to/xtensa-esp32-elf/"
Unfortunately, there is no "xtensa-esp32-elf/" directory that I can find.When I try to build the example, I get the following error: zephyr-sdk-0.11.3/xtensa/esp32/xtensa-zephyr-elf/bin/xtensa-zephyr-elf-gcc not found - Please check your toolchain installation It is probably something simple, but I'm stumped. Can someone point me in the right direction?
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
sending data to SD card - CS control inhibited (no GPIO device)
Edyta Bosacka <edyta.bosacka@...>
I want to write some data in .csv file on SD card. Some of data are written , but then I get error :
"CS control inhibited (no GPIO device)"
I added this in config file:
 
I havent got any idea what could cause this problem
🙁
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
API meeting: agenda
Carles Cufi
Hi all,
Today's topics: - Device: Normalize DMA, IPM and UART callbacks signatures including the caller's device pointer (should be quick, PRs are already approved and email sent to the mailing lists) - Issue: https://github.com/zephyrproject-rtos/zephyr/issues/26923 - PR: https://github.com/zephyrproject-rtos/zephyr/pull/26426 - PR: https://github.com/zephyrproject-rtos/zephyr/pull/26780 - PR: https://github.com/zephyrproject-rtos/zephyr/pull/26781 - Device: Const-ify device driver instances - PR: https://github.com/zephyrproject-rtos/zephyr/pull/24873 - Go through the current set of issues in the project and clean up/organize them Additional items in the "Triage" column in the GitHub project may be discussed if time permits. If you want an item included in the meeting, please add it to the GitHub project. 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
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
ODP: Reading data from LSM6DS33 , I2C
Edyta Bosacka <edyta.bosacka@...>
Thank you 🙂
Thanks to your advice I opened this file but I still get error while writing to this file
🙁Do you have any idea why? I will be very grateful for any help😊
Od: Lawrence King <lawrence.king@...>
Wysłane: piątek, 24 lipca 2020 15:41 Do: Edyta Bosacka <edyta.bosacka@...>; users@... <users@...> Temat: RE: Reading data from LSM6DS33 , I2C Did you power up the Accelerometer? You should read the full datasheet, here is what is says about power:
Operating modes The LSM6DS33 has three operating modes available: only accelerometer active and gyroscope in power-down only gyroscope active and accelerometer in power-down both accelerometer and gyroscope sensors active with independent ODR The accelerometer is activated from power down by writing ODR_XL[3:0] in CTRL1_XL (10h) while the gyroscope is activated from power-down by writing ODR_G[3:0] in CTRL2_G (11h). For combo mode the ODRs are totally independent.
There are a lot of registers (about 60) in this chip, you need to setup the chip before you can use it. Did you set the output data rates? The Fifo? The filters?
Lawrence King Principal Developer +1(416)627-7302
From: users@... <users@...>
On Behalf Of Edyta Bosacka
Sent: Friday, July 24, 2020 5:27 AM To: users@... Subject: [Zephyr-users] Reading data from LSM6DS33 , I2C
Hi 🙂 I want to read some data (axis_X) from accelerometer but I constantly get "0" answer.
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
|
Re: Sending data to .csv file
You didn’t check the return code from fs_open(). I am pretty sure the open failed, I think the correct file path is “/SD:/plink.csv”.
You then tried to write to a file with an invalid handle which caused the instruction access violation.
Lawrence King Principal Developer +1(416)627-7302
From: users@... <users@...>
On Behalf Of Edyta Bosacka
Sent: Monday, July 27, 2020 10:13 AM To: users@... Subject: [Zephyr-users] Sending data to .csv file
Hi 🙂 I want to write some data to .csv file.
I took an example : \zephyrproject\zephyr\samples\subsys\fs\fat_fs and I added these to my code:
In main:
Os_x, os_y, os_z - these are variables I wanna have in one row in .csv file.
The code compiles, but in terminal I get:
I also tried fs_opendir (&zfp, "C:/Users/user/Desktop/file.csv") but it also doesnt work 🙁
|
|||||||||||||||||||||
|
|
|||||||||||||||||||||
