|
Re: Use the drivers files from the custom application directory instead of ZEPHYR_BASE
Srinivasan Tamilarasan
Hi Jacob, Thank you for the response.
As you have mentioned, I have tried following items, · Removed the statements set BOARD_ROOT, SOC_ROOT, DTS_ROOT in cmake . · Added env variables, ZEPHYR_BASE=<my_zephyr_directory> and ZEPHYR_EXTRA_MODULES=$PWD. · Take reference to example-application and developed our custom application.
After that I am getting below error. PFA attachment of error log.
I have added CONFIG_CORTEX_M_SYSTICK=y in my board config file.
Can you please help me to resolve this issue?
Regards, Srinivasan
From: devel@... <devel@...>
On Behalf Of Jacob Avraham
Sent: 25 June 2021 06:00 PM To: devel@... Subject: Re: [Zephyr-devel] Use the drivers files from the custom application directory instead of ZEPHYR_BASE
[External Email]: This email arrived from an external source - Please exercise caution when opening any attachments or clicking on links. Srinivasan, I just did that recently. I modeled my application and soc, board, dts and drivers as a standalone Zephyr module, and used example-application as a reference. Note the content of the zephyr/module.yml file, which points to the soc, dts, and boards location. To build my application from the top of my repository, I set 2 environment variables: ZEPHYR_BASE=<my_zephyr_directory> ZEPHYR_EXTRA_MODULES=$PWD
and I run: west -b <my_board> <my_application_path>
No need to set BOARD_ROOT, SOC_ROOT, DTS_ROOT.
Jacob Avraham
|
|
|
|
nrf5340Dk
#bluetooth
Please help. I cannot get a single bluethooth sample project to work. I tried a beacon, central etc. I expected to see the device on my cell phone so i could connect.
|
|
|
|
Re: Use the drivers files from the custom application directory instead of ZEPHYR_BASE
Jacob Avraham
Srinivasan, I just did that recently. I modeled my application and soc, board, dts and drivers as a standalone Zephyr module, and used example-application as a reference. Note the content of the zephyr/module.yml file, which points to the soc, dts, and boards location. To build my application from the top of my repository, I set 2 environment variables: ZEPHYR_BASE=<my_zephyr_directory> ZEPHYR_EXTRA_MODULES=$PWD and I run: west -b <my_board> <my_application_path> No need to set BOARD_ROOT, SOC_ROOT, DTS_ROOT. Jacob Avraham
|
|
|
|
Use the drivers files from the custom application directory instead of ZEPHYR_BASE
Srinivasan Tamilarasan
Hi, I am creating the standalone Zephyr application build.
I have moved the custom dts, soc and board files to the application directory by adding below below lines in application cmake file, set(BOARD_ROOT ${CMAKE_CURRENT_LIST_DIR}) set(SOC_ROOT ${CMAKE_CURRENT_LIST_DIR}) set(DTS_ROOT ${CMAKE_CURRENT_LIST_DIR})
How to tell the zephyr to use the driver file from the my application directory instead of default location from ZEPHYR_BASE location?
Kindly help me to resolve this issue.
Regards, Srinivasan
|
|
|
|
Re: Failed to register advertisement: org.bluez.Error.NotPermitted
#nrf52
lairdjm
Hi, Did you configure the Bluetooth stack in zephyr to enable the additional options/features? Hciconfig was deprecated 3 years ago now, use the latest version of blueZ and the latest utilities, not utilities that were dropped years ago. Thanks, Jamie
From: devel@... <devel@...>
On Behalf Of akshaykulkarniak via lists.zephyrproject.org
Sent: 25 June 2021 07:01 To: devel@... Subject: [Zephyr-devel] Failed to register advertisement: org.bluez.Error.NotPermitted #nrf52
Hi there , [bluetooth]# scan on Discovery started [CHG] Controller AB:89:67:45:23:01 Discovering: yes [NEW] Device FE:9B:39:0D:92:DA Nordic_UART [NEW] Device EB:2E:27:65:B2:50 Nordic_UART [NEW] Device 5B:38:AE:01:DA:1A 5B-38-AE-01-DA-1A [NEW] Device 4C:5C:1F:26:C5:E6 4C-5C-1F-26-C5-E6 [NEW] Device DE:B1:4E:96:12:A3 TS101C_860906040263136 [NEW] Device F4:0A:E3:37:E7:95 TS101C_869857038077916 [NEW] Device EB:93:06:F2:57:91 FMC125_0597405_LE [CHG] Device 5B:38:AE:01:DA:1A RSSI: -62 [NEW] Device 49:5B:9B:25:3B:48 49-5B-9B-25-3B-48 [NEW] Device E5:56:26:5A:B0:2E TS101C_358250330000216 [CHG] Device 5B:38:AE:01:DA:1A RSSI: -77 [CHG] Device 5B:38:AE:01:DA:1A RSSI: -64 [bluetooth]# scan off Discovery stopped [CHG] Controller AB:89:67:45:23:01 Discovering: no [CHG] Device E5:56:26:5A:B0:2E RSSI is nil [CHG] Device 49:5B:9B:25:3B:48 TxPower is nil [CHG] Device 49:5B:9B:25:3B:48 RSSI is nil [CHG] Device EB:93:06:F2:57:91 TxPower is nil [CHG] Device EB:93:06:F2:57:91 RSSI is nil [CHG] Device F4:0A:E3:37:E7:95 RSSI is nil [CHG] Device DE:B1:4E:96:12:A3 RSSI is nil [CHG] Device 4C:5C:1F:26:C5:E6 TxPower is nil [CHG] Device 4C:5C:1F:26:C5:E6 RSSI is nil [CHG] Device 5B:38:AE:01:DA:1A TxPower is nil [CHG] Device 5B:38:AE:01:DA:1A RSSI is nil [CHG] Device EB:2E:27:65:B2:50 RSSI is nil [CHG] Device FE:9B:39:0D:92:DA RSSI is nil [bluetooth]# discoverable on Changing discoverable on succeeded [CHG] Controller AB:89:67:45:23:01 Discoverable: yes [bluetooth]# advertise on Failed to register advertisement: org.bluez.Error.NotPermitted
Also observed that there is no link policy . And link mode is Master by default and when i tried changing it i have below error . root@swi-mdm9x28-wp:~# hciconfig -a hci0 lm SLAVE,ACCEPT Can't set default link mode on hci0: Operation not supported (95) root@swi-mdm9x28-wp:~# hciconfig -a hci0: Type: Primary Bus: UART BD Address: AB:89:67:45:23:01 ACL MTU: 27:7 SCO MTU: 0:0 UP RUNNING RX bytes:417 acl:0 sco:0 events:29 errors:0 TX bytes:228 acl:0 sco:0 commands:29 errors:0 Features: 0x00 0x00 0x00 0x00 0x60 0x00 0x00 0x00 Packet type: DM1 DH1 HV1 Link policy: Link mode: MASTER Can't read local name on hci0: Input/output error (5)
|
|
|
|
Failed to register advertisement: org.bluez.Error.NotPermitted
#nrf52
Hi there ,
I am trying to turn on advertise and I have below errors [bluetooth]# scan on
Discovery started
[CHG] Controller AB:89:67:45:23:01 Discovering: yes
[NEW] Device FE:9B:39:0D:92:DA Nordic_UART
[NEW] Device EB:2E:27:65:B2:50 Nordic_UART
[NEW] Device 5B:38:AE:01:DA:1A 5B-38-AE-01-DA-1A
[NEW] Device 4C:5C:1F:26:C5:E6 4C-5C-1F-26-C5-E6
[NEW] Device DE:B1:4E:96:12:A3 TS101C_860906040263136
[NEW] Device F4:0A:E3:37:E7:95 TS101C_869857038077916
[NEW] Device EB:93:06:F2:57:91 FMC125_0597405_LE
[CHG] Device 5B:38:AE:01:DA:1A RSSI: -62
[NEW] Device 49:5B:9B:25:3B:48 49-5B-9B-25-3B-48
[NEW] Device E5:56:26:5A:B0:2E TS101C_358250330000216
[CHG] Device 5B:38:AE:01:DA:1A RSSI: -77
[CHG] Device 5B:38:AE:01:DA:1A RSSI: -64
[bluetooth]# scan off
Discovery stopped
[CHG] Controller AB:89:67:45:23:01 Discovering: no
[CHG] Device E5:56:26:5A:B0:2E RSSI is nil
[CHG] Device 49:5B:9B:25:3B:48 TxPower is nil
[CHG] Device 49:5B:9B:25:3B:48 RSSI is nil
[CHG] Device EB:93:06:F2:57:91 TxPower is nil
[CHG] Device EB:93:06:F2:57:91 RSSI is nil
[CHG] Device F4:0A:E3:37:E7:95 RSSI is nil
[CHG] Device DE:B1:4E:96:12:A3 RSSI is nil
[CHG] Device 4C:5C:1F:26:C5:E6 TxPower is nil
[CHG] Device 4C:5C:1F:26:C5:E6 RSSI is nil
[CHG] Device 5B:38:AE:01:DA:1A TxPower is nil
[CHG] Device 5B:38:AE:01:DA:1A RSSI is nil
[CHG] Device EB:2E:27:65:B2:50 RSSI is nil
[CHG] Device FE:9B:39:0D:92:DA RSSI is nil
[bluetooth]# discoverable on
Changing discoverable on succeeded
[CHG] Controller AB:89:67:45:23:01 Discoverable: yes
[bluetooth]# advertise on
Failed to register advertisement: org.bluez.Error.NotPermitted
root@swi-mdm9x28-wp:~# hciconfig -a hci0 lm SLAVE,ACCEPT
Can't set default link mode on hci0: Operation not supported (95) root@swi-mdm9x28-wp:~# hciconfig -a
hci0: Type: Primary Bus: UART
BD Address: AB:89:67:45:23:01 ACL MTU: 27:7 SCO MTU: 0:0
UP RUNNING
RX bytes:417 acl:0 sco:0 events:29 errors:0
TX bytes:228 acl:0 sco:0 commands:29 errors:0
Features: 0x00 0x00 0x00 0x00 0x60 0x00 0x00 0x00
Packet type: DM1 DH1 HV1
Link policy:
Link mode: MASTER
Can't read local name on hci0: Input/output error (5)
BlueZ Version Information root@swi-mdm9x28-wp:/usr/libexec# ./bluetooth/bluetoothd -v 5.50 root@swi-mdm9x28-wp:~# bluetoothctl --v bluetoothctl: 5.50 Please Let me know what could be the reason and a probable solution to overcome this issue .
|
|
|
|
Event: Zephyr Project: Dev Meeting - 06/24/2021
#cal-reminder
devel@lists.zephyrproject.org Calendar <noreply@...>
Reminder: Zephyr Project: Dev Meeting When: Where: Organizer: devel@... An RSVP is requested. Click here to RSVP Description: ________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 483 314 739#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
________________________________________________________________________________
|
|
|
|
Using two UART-based protocols on the same UART link
Vincent Guenat <vincent.guenat@...>
Hello there!
I have a Zephyr-based module connected to a host via a UART connection and I would like to use two different protocols, namely Bluetooth HCI (as shown in zephyr/samples/bluetooth/hci_uart/src/main.c) and MCUmgr's SMP (as shown in zephyr/subsys/mgmt/mcumgr/smp_uart.c). From the source code I understand that each of them is registering a callback to the UART subsystem with uart_irq_callback_set and uart_irq_callback_user_data_set to be notified when new data is available, but, obviously, only one gets the data. Is there a way to make the HCI and SMP UART drivers collaborate? I thought maybe having a different ISR that would forward the data to one or the other subsystem depending on the received bytes could be a solution. Best regards, Vincent Guenat ________________________________ Safran Passenger Innovations Germany GmbH, Registergericht: München HRB 141647, Vat.: DE 813396184 Geschäftsführerin: Núria Riera Díaz ________________________________ This email and any files transmitted with it are confidential & proprietary to Safran Passenger Innovations. This information is intended solely for the use of the individual or entity to which it is addressed. Access or transmittal of the information contained in this e-mail, in full or in part, to any other organization or persons is not authorized.
|
|
|
|
Dev-Review Meeting Agenda June 24th
Kumar Gala
This week’s agenda is a continuation of last week:
RFC: API Change: Flash map: - https://github.com/zephyrproject-rtos/zephyr/issues/34706 RFC: Flash area changes: - https://github.com/zephyrproject-rtos/zephyr/pull/34530 storage: flash partition API: - https://github.com/zephyrproject-rtos/zephyr/pull/34494 Plus anything anyone else has. - k
|
|
|
|
RFC: API Change: Flash map: Partition ID generation #36517
Ermel, Dominik
Hello,
I have proposed change in generating IDs for flash partitions, to include only partitions that are enabled. RFC here: https://github.com/zephyrproject-rtos/zephyr/issues/36517
The change should allow to detect, at compile time, situations where by accident not enabled partition is referenced, something that currently will be detected only at run-time. It will also give more ordered IDs, if somebody cares to disable unused partitions, and may allow easier way to index objects representing partitions in memory.
The PR that implements the change is here: https://github.com/zephyrproject-rtos/zephyr/pull/36394
Regards, Dominik Ermel
|
|
|
|
Re: Can't init device hci0: Cannot assign requested address (99)
#nrf52
lairdjm
Hi Akshay, 00:00:00:00:00:00 is not a valid Bluetooth address, set a valid Bluetooth address and try again Thanks, Jamie
From: devel@... <devel@...>
On Behalf Of akshaykulkarniak via lists.zephyrproject.org
Sent: 23 June 2021 10:45 To: devel@... Subject: [Zephyr-devel] Can't init device hci0: Cannot assign requested address (99) #nrf52 #nrf52 #nrf52
Hi there , I am trying to bring up a BT (HCI interface) module connected to a qualcomm chipset Trying to bring up the interface using hciconfig but it fails with error no.99 .
Note : ttyUSB here is a cp210x (USB-UART bridge) connected via HSIC
Below are the logs
root@swi-mdm9x28-wp:~# hciattach -s 115200 /dev/ttyUSB2 any 115200 noflow nosleep Device setup complete
root@swi-mdm9x28-wp:~# hciconfig -a hci0: Type: Primary Bus: UART BD Address: 00:00:00:00:00:00 ACL MTU: 27:7 SCO MTU: 0:0 DOWN RX bytes:205 acl:0 sco:0 events:14 errors:0 TX bytes:80 acl:0 sco:0 commands:14 errors:0 Features: 0x00 0x00 0x00 0x00 0x60 0x00 0x00 0x00 Packet type: DM1 DH1 HV1 Link policy: Link mode: MASTER
root@swi-mdm9x28-wp:~# hciconfig hci0 up Can’t init device hci0: Cannot assign requested address (99) root@swi-mdm9x28-wp:~# hciconfig hci0 up Can’t init device hci0: Cannot assign requested address (99) root@swi-mdm9x28-wp:~# hciconfig hci0 up Can’t init device hci0: Cannot assign requested address (99) root@swi-mdm9x28-wp:~# hciconfig hci0 up Can’t init device hci0: Cannot assign requested address (99) root@swi-mdm9x28-wp:~# hciconfig hci0 up Can’t init device hci0: Cannot assign requested address (99)
Below are the Details of the Chipset
Module : Sierra Wireless WP7608 (Chipset : QC MDM9x28) Linux Kernel version : 3.18.140 Yocto Project : 2.5
Please Let me know a possible solution to overcome this .
Thanks & Regards - Akshay
|
|
|
|
RFC: API Change: Flash #36485
Ermel, Dominik
Hello,
Within the RFC: https://github.com/zephyrproject-rtos/zephyr/issues/36485 I would like to propose a change, to the flash API, regarding how the flash page information and size is obtained. For that purpose I propose definition of following API calls: int flash_get_page_info(const struct device *dev, off_t offset, struct flash_page_info *fpi); ssize_t flash_get_page_count(const struct device *dev); ssize_t flash_get_size(const struct device *dev);
and addition of following fields to flash_parameters structure, to store flags and size of the largest page on a device (max_page_size). I am also adding first flag, FPF_NON_UNIFORM_LAYOUT, that allows to quickly check whether the flash device offers uniform layout.
In contrary to the flash_api_pages_layout call, enabled with CONFIG_FLASH_PAGE_LAYOUT, the new additions to the API are always present.
These additions allow quicker access to the flash size and the page count, while obtaining page information will depend on whether layout is uniform or not and on how the driver implements the function. The change simplifies access to flash information and allows to easily override the calls in “virtual” devices that could be stacked over the other.
The proposed change, to the code, is available here: https://github.com/zephyrproject-rtos/zephyr/pull/36484
Here is PR that uses the changes to implement flash partition device, which is “virtual” device, and may be used in any functions that call flash API, the same way a real device would be used: https://github.com/zephyrproject-rtos/zephyr/pull/36487
Best regards, Dominik Ermel
Dominik ERMEL | Senior Software Engineer
|
|
|
|
Can't init device hci0: Cannot assign requested address (99)
#nrf52
akshaykulkarniak@...
Hi there ,
I am trying to bring up a BT (HCI interface) module connected to a qualcomm chipset
Trying to bring up the interface using hciconfig but it fails with error no.99 .
Note : ttyUSB here is a cp210x (USB-UART bridge) connected via HSIC
Below are the logs
root@swi-mdm9x28-wp:~# hciattach -s 115200 /dev/ttyUSB2 any 115200 noflow nosleep
Device setup complete
root@swi-mdm9x28-wp:~# hciconfig -a
hci0: Type: Primary Bus: UART
BD Address: 00:00:00:00:00:00 ACL MTU: 27:7 SCO MTU: 0:0
DOWN
RX bytes:205 acl:0 sco:0 events:14 errors:0
TX bytes:80 acl:0 sco:0 commands:14 errors:0
Features: 0x00 0x00 0x00 0x00 0x60 0x00 0x00 0x00
Packet type: DM1 DH1 HV1
Link policy:
Link mode: MASTER
root@swi-mdm9x28-wp:~# hciconfig hci0 up
Can’t init device hci0: Cannot assign requested address (99)
root@swi-mdm9x28-wp:~# hciconfig hci0 up
Can’t init device hci0: Cannot assign requested address (99)
root@swi-mdm9x28-wp:~# hciconfig hci0 up
Can’t init device hci0: Cannot assign requested address (99)
root@swi-mdm9x28-wp:~# hciconfig hci0 up
Can’t init device hci0: Cannot assign requested address (99)
root@swi-mdm9x28-wp:~# hciconfig hci0 up
Can’t init device hci0: Cannot assign requested address (99)
Below are the Details of the Chipset
Module : Sierra Wireless WP7608 (Chipset : QC MDM9x28)
Linux Kernel version : 3.18.140
Yocto Project : 2.5
Please Let me know a possible solution to overcome this .
Thanks & Regards
- Akshay
|
|
|
|
Can't init device hci0: Cannot assign requested address (99)
#nrf52
akshaykulkarniak@...
Hi there , Note : ttyUSB here is a cp210x (USB-UART bridge) connected via HSIC Below are the logs root@swi-mdm9x28-wp:~# hciattach -s 115200 /dev/ttyUSB2 any 115200 noflow nosleep root@swi-mdm9x28-wp:~# hciconfig -a root@swi-mdm9x28-wp:~# hciconfig hci0 up
|
|
|
|
Event: Zephyr Project: APIs - 06/22/2021
#cal-reminder
devel@lists.zephyrproject.org Calendar <noreply@...>
Reminder: Zephyr Project: APIs When: Where: Organizer: devel@... An RSVP is requested. Click here to RSVP Description: Meeting decisions/discussions in their respective PRs, tracked here: https://github.com/zephyrproject-rtos/zephyr/projects/18 ________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 317 990 129#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
________________________________________________________________________________
|
|
|
|
Re: stm32 quadrature decoder general purpose timer functionality
Piotr Mienkowski
Hi Matias,
On 21.06.21 20:42, Matias N. wrote: I need to access STM32's general purpose timer's quadrature decoding functionality. I'm trying to understand what exactly is needed to expose this, either write a custom driver accessing arch-dependant interface directly or if there's at least some support exposed via counter API for example.So far support for quadrature decoding functionality of a general purpose timer/counter module has been implemented as a dedicated sensor driver. You can check * drivers/sensor/qdec_nrfx * drivers/sensor/qdec_sam They use a different binding than a regular counter driver. It's the compatible property of the timer/counter DT node that decides which driver will 'own' it. There is also a basic sample app to demo the driver: samples/sensor/qdec. Regards, Piotr
|
|
|
|
Testing sdmmc_stm32 disk driver
#driver
Nick Stoughton
I am working through a pull-request to add a new eMMC driver for the STM32 family, and much of it is based on the sdmmc_stm32 driver for SD cards. EMMC chips use a different protocol over the SDIO bus, though it is electrically identical. A suggested approach is to pull all of the common code out of the existing sdmmc_stm32 driver, and have 3 files: sdmmc_stm32_common.c, sdmmc_stm32.c, and emmc_stm32.c, with all the code that is common in one place and not copied.
I agree that this approach would be best, but it will mean significant refactoring to the existing driver that I do not have the hardware to test. Anyone willing to help? -- Nick
|
|
|
|
stm32 quadrature decoder general purpose timer functionality
Matias N.
Hi, I need to access STM32's general purpose timer's quadrature decoding functionality. I'm trying to understand what exactly is needed to expose this, either write a custom driver accessing arch-dependant interface directly or if there's at least some support exposed via counter API for example. I see there's specific driver for STM32 PWM functionality so I would guess a similar driver is needed. There's also STM32 counter driver but this would be a different kind of counter (requires special setup of timer). I also see bindings for other platforms which have dedicated QDEC peripherals, so I'm guessing that a similar DTS binding should also be added. What would be the proper way to do this? Best, Matias
|
|
|
|
Event: Zephyr Memory Footprint - biweekly discussion - 06/21/2021
#cal-reminder
devel@lists.zephyrproject.org Calendar <noreply@...>
Reminder: Zephyr Memory Footprint - biweekly discussion When: Where: Organizer: devel@... An RSVP is requested. Click here to RSVP Description: ______________________________
Microsoft Teams meeting
Join on your computer or mobile app
Click here to join the meetingOr call in (audio only)
+1 321-558-6518,,546018126# United States, Orlando
______________________________
|
|
|
|
Re: How to change IP for MQTT Publisher sample for online kapua server
Lubos, Robert
Hi Brenton
You can either use “west build -t menuconfig” command to open a configuration window, or modify the `prj.conf` file directly. I rather suggest the latter, as it’s clear then what exactly you’ve changed.
> 2. I am currently compiling with "-- -DOVERLAY_CONFIG=overlay-e1000.conf". Do I need to change this? I’m assuming you’re using https://docs.zephyrproject.org/latest/guides/networking/qemu_eth_setup.html , in that case you need that overlay to enable appropriate Ethernet driver. There’s also an alternative way to enable networking in Qemu (https://docs.zephyrproject.org/latest/guides/networking/qemu_setup.html), in that case SLIP driver is used and you don’t need any extra overlay. This approach is considered slower though.
Genereally, I suggest to try and run the `net/sockets/http_get` sample, which should connect to the web server on the internet out-of-the-box. This should help you to verify that you network configuration is correct to reach the internet from Qemu.
Regards, Robert
From: devel@... <devel@...>
On Behalf Of Brenton Chetty via lists.zephyrproject.org
Sent: poniedziałek, 21 czerwca 2021 15:20 To: devel@... Subject: [Zephyr-devel] How to change IP for MQTT Publisher sample for online kapua server
Hi, I am trying to connect the MQTT_Publisher via qemu to an online Kapua server.
I managed to connect mqtt_pub to a localhost kapua server using the "zeth" interface "./net-setup.sh"
I assume I need to change these 2 lines in prj.conf " " If the kapua server is on "http://146.34.8.67:8080/" (altered ip) 1. How do I change my IP values? 2. I am currently compiling with "-- -DOVERLAY_CONFIG=overlay-e1000.conf". Do I need to change this?
With thanks Brenton
|
|
|
