Date   

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
M +48 505 071 130 | Kraków, Poland
nordicsemi.com | devzone.nordicsemi.com

Nordic_logo_signature

 


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 ,
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

 


Event: Zephyr Project: APIs - 06/22/2021 #cal-reminder

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Reminder: Zephyr Project: APIs

When:
06/22/2021
4:00pm to 5:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

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:
06/21/2021
3:00pm to 4:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

Organizer: devel@...

An RSVP is requested. Click here to RSVP

Description:
Working doc: https://docs.google.com/document/d/1bnQLJKVhgI3zkk3MsSXun8onEsA8z1Rf5ohdbCHASmU/edit#heading=h.x36xe8bnwr9r

________________________________________________________________________________
Microsoft Teams meeting
Join on your computer or mobile app
Click here to join the meeting
Or call in (audio only)
+1 321-558-6518,,546018126# United States, Orlando
Phone Conference ID: 546 018 126#
 
 
________________________________________________________________________________


Re: How to change IP for MQTT Publisher sample for online kapua server

Lubos, Robert
 

Hi Brenton

> 1. How do I change my IP values?

 

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.
You’d need to modify “CONFIG_NET_CONFIG_PEER_IPV4_ADDR” to the value of the server IP address, and in order to reach external network you’d also need to set the gateway address (“CONFIG_NET_CONFIG_MY_IPV4_GW”).

 

>  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

"
CONFIG_NET_CONFIG_MY_IPV4_ADDR="192.0.2.1"
CONFIG_NET_CONFIG_PEER_IPV4_ADDR="192.0.2.2"

"

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


How to change IP for MQTT Publisher sample for online kapua server

Brenton Chetty
 

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
"
CONFIG_NET_CONFIG_MY_IPV4_ADDR="192.0.2.1"
CONFIG_NET_CONFIG_PEER_IPV4_ADDR="192.0.2.2"
"
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


API meeting: agenda

Carles Cufi
 


Event: Zephyr Project: Dev Meeting - 06/17/2021 #cal-reminder

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Reminder: Zephyr Project: Dev Meeting

When:
06/17/2021
3:00pm to 4:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

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
 
 
________________________________________________________________________________


Dev-Review Meeting Agenda June 17th

Kumar Gala
 

Today’s (Jun 17, 2021) topic will will focus on Flash Map API

- k

On Jun 14, 2021, at 2:43 PM, Kumar Gala <kumar.gala@linaro.org> wrote:

All,

I was hoping to confirm that you’d be able to join this week’s Dev-review meeting as one of the Agenda topic items will be the Flash Map API:

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

I vaguely remember that part of the discussion focused on the implications for MCUboot and how we might cleanup the interface there.

- k


Resolve warning of DT_INST_DMAS_LABEL_BY_NAME deprecated macro in zephyr 2.6.0

Srinivasan Tamilarasan
 

Hi,

In our dma based serial driver code, I am using the DT_INST_DMAS_LABEL_BY_NAME() as given in below code snippet.

 

 

DT_INST_DMAS_LABEL_BY_NAME macro is deprecated in zephyr 2.6.0 release. I am trying to replace the DT_INST_DMAS_LABEL_BY_NAME macro to equal macro.

 

Option 1:  I have tried that DT_INST_DMAS_LABEL_BY_NAME() with DEVICE_DT_GET(DT_DMAS_CTLR_BY_NAME(n,tx)). But it provided below build error,

 

Kindly let me know what is the right way to to avoid this waring.

 

Regards,

Srinivasan


Event: Zephyr Project: APIs - 06/15/2021 #cal-reminder

devel@lists.zephyrproject.org Calendar <noreply@...>
 

Reminder: Zephyr Project: APIs

When:
06/15/2021
4:00pm to 5:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

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: [DEV REVIEW] Topic - Flash Map API

Bolivar, Marti
 

I'll be there.

Kumar Gala <kumar.gala@linaro.org> writes:

All,

I was hoping to confirm that you’d be able to join this week’s Dev-review meeting as one of the Agenda topic items will be the Flash Map API:

RFC: API Change: Flash map:
- https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fzephyrproject-rtos%2Fzephyr%2Fissues%2F34706&;data=04%7C01%7CMarti.Bolivar%40nordicsemi.no%7C3222a72b2481490e6ac108d92f6cac2d%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C637592966065271826%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=wcsrz3CHdJlVCs%2FPS1vwBqHiIm3Usn3ow4kgrQpsCZs%3D&amp;reserved=0

RFC: Flash area changes:
- https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fzephyrproject-rtos%2Fzephyr%2Fpull%2F34530&;data=04%7C01%7CMarti.Bolivar%40nordicsemi.no%7C3222a72b2481490e6ac108d92f6cac2d%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C637592966065281789%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=TU%2BL1LE872WsVa5HZh0w3svP6e9CJ4EiomfO%2FJ4Qnlg%3D&amp;reserved=0

storage: flash partition API:
- https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fzephyrproject-rtos%2Fzephyr%2Fpull%2F34494&;data=04%7C01%7CMarti.Bolivar%40nordicsemi.no%7C3222a72b2481490e6ac108d92f6cac2d%7C28e5afa2bf6f419a8cf6b31c6e9e5e8d%7C0%7C0%7C637592966065281789%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=ohXCWJIMlDWrh8cyrqTDRvlGxvP9dwe63fX1vFRhfwg%3D&amp;reserved=0

I vaguely remember that part of the discussion focused on the implications for MCUboot and how we might cleanup the interface there.

- k


API meeting: agenda

Carles Cufi
 


[DEV REVIEW] Topic - Flash Map API

Kumar Gala
 

All,

I was hoping to confirm that you’d be able to join this week’s Dev-review meeting as one of the Agenda topic items will be the Flash Map API:

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

I vaguely remember that part of the discussion focused on the implications for MCUboot and how we might cleanup the interface there.

- k

221 - 240 of 8050