1. devel@lists.zephyrproject.org
   Date   
powerpc port of Zephyr

Michael Neuling
 

Hi all,

Below is a basic port of Zephyr to powerpc:

https://github.com/mikey/zephyr/commits/powerpc

It runs on both qemu and and microwatt [1]. It runs the basic tests and samples
in the repository and supports both cooperative and pre-emptive multitasking.

The patch still contains a few FIXMEs but reviews are welcome. When we are
comfortable with the patch, we'd like to create a PR so it can be considered for
inclusion in the upstream project.

The port was done by Anton Blanchard and myself.

Regards,
Mikey

1. https://github.com/antonblanchard/microwatt
Problem with sending longer HCI messages with DLE enabled NRF52840 #ble #hci #nrf52480

kristian.kajak@...
 

Hi,

I am having some problems with getting two NRF52840 USB dongles to communicate with each other with extended data ACL data lengths. I have flashed both the dongles with the Zephyr HCI-USB samples (slightly modified configurations to enable Data Length Extension).

Problem:
Without the DLE configurations, I was able to send 27B of data (including L2CAP length + CID headers) within one transmission so that I can actually receive the "Number of completed packets" event and see that the remote device receives this data. With the DLE enabled, I can only send up to 68B of data (again, headers included), whereas I was expecting to be able to send up to 251B. If the data length is 69 or more, I will not receive the "Number of completed packets" event and the data is not seen on the remote device.

What I have tried:
Different CTRL & HOST config modifications (including CONFIG_BT_HCI_ACL_FLOW_CONTROL=y/n, CONFIG_BT_L2CAP_TX/RX_MTU=247, CONFIG_BT_RX_BUF_LEN=258, and more...) and validated that all of them get set properly with menuconfig.
Also tried using the HCI_Host_Buffer_Size command to set the buffer size to 251 of both of the systems.
Tried increasing the Connection interval to 30ms.
Tried increasing the TX times to 17040 with HCI_LE_Set_Data_length.

Setup:
Host #1: Linux Mint Tina 19.2
Host #1: Linux Mint Tina 19.2, running on VM
Controllers #1 & #2: Zephyr HCI-USB with the following config modifications:

    CONFIG_BT_HCI_ACL_FLOW_CONTROL=y

    CONFIG_BT_RX_BUF_LEN=258

    CONFIG_BT_CTLR_PHY=y

    CONFIG_BT_CTLR_PHY_2M=y

    CONFIG_BT_CTLR_RX_BUFFERS=10

    CONFIG_BT_CTLR_TX_BUFFERS=10

    CONFIG_BT_CTLR_TX_BUFFER_SIZE=251

    CONFIG_BT_CTLR_DATA_LENGTH_MAX=251

 

    CONFIG_BT_CTLR_ADVANCED_FEATURES=y


I can of course provide additional information if requested. Hope someone can provide some ideas!

With regards,
Kristian
Re: Require Help NRF52840 PCA 10059

Bolivar, Marti
 

Hi,

"Muhammad Muh via Lists.Zephyrproject.Org"
<muhammad.muh83=outlook.com@lists.zephyrproject.org> writes:

Dear All,

It has been quite long that i emailed to this group. Hope everybody is fine and in good health. Coming towards the issue i am using nrf52840_PCA10059 Dongle. I am trying to do the example available in
Zephyr----> Sample------->Boards------>nrf52---------->onoff-app and
onoff_level_lighting_vnd_app.
I get what you mean, but we usually identify files using their paths.

Example: zephyr/samples/boards/nrf52/mesh/onoff-app

When i use the WEST command by using board PCA 10056 they run fine and give no error. Moreover, when i run the following command with PCA 10059 i get the following error with both the examples.

Command: west build -b nrf52840_pca10059 .
Error: I am showing the last part of error
../src/mesh/publisher.c: In function 'publish':
../src/mesh/publisher.c:61:43: error: 'DT_ALIAS_SW1_GPIOS_PIN' undeclared (first use in this function); did you mean 'DT_ALIAS_SW0_GPIOS_PIN'?
} else if (button_read(button_device[1], DT_ALIAS_SW1_GPIOS_PIN) == 0U) {
^~~~~~~~~~~~~~~~~~~~~~
DT_ALIAS_SW0_GPIOS_PIN
../src/mesh/publisher.c:61:43: note: each undeclared identifier is reported only once for each function it appears in
../src/mesh/publisher.c:83:43: error: 'DT_ALIAS_SW2_GPIOS_PIN' undeclared (first use in this function); did you mean 'DT_ALIAS_SW0_GPIOS_PIN'?
} else if (button_read(button_device[2], DT_ALIAS_SW2_GPIOS_PIN) == 0U) {
^~~~~~~~~~~~~~~~~~~~~~
DT_ALIAS_SW0_GPIOS_PIN
../src/mesh/publisher.c:153:43: error: 'DT_ALIAS_SW3_GPIOS_PIN' undeclared (first use in this function); did you mean 'DT_ALIAS_SW0_GPIOS_PIN'?
} else if (button_read(button_device[3], DT_ALIAS_SW3_GPIOS_PIN) == 0U) {
^~~~~~~~~~~~~~~~~~~~~~
DT_ALIAS_SW0_GPIOS_PIN
ninja: build stopped: subcommand failed.
ERROR: command exited with status 1: /home/rg/cmake-3.13.1-Linux-x86_64/bin/cmake --build /home/rg/zephyrproject/zephyr/samples/boards/nrf52/mesh/onoff_level_lighting_vnd_app/build

It is requested to kindly advise on the aforementioned.
The PCA10059 board only has one button, so its devicetree (dts file)
only defines a sw0 alias. The on-off sample seems to require additional
buttons since it's using macros generated from the sw1, sw2, and sw3
aliases, so I doubt it will work with that board.

Please see the devicetree documentation for more details:

https://docs.zephyrproject.org/latest/guides/dts/index.html

Thanks,
Marti


Best Regards
Upcoming Event: Zephyr Project: APIs - Tue, 10/22/2019 9:00am-10:00am, Please RSVP #cal-reminder

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

Reminder: Zephyr Project: APIs

When: Tuesday, 22 October 2019, 9:00am to 10:00am, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/177647878

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description: Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/177647878

Or iPhone one-tap :
    US: +16465588656,,177647878# or +16699006833,,177647878# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 177 647 878
    International numbers available: https://zoom.us/zoomconference?m=ioAR9GK1OE5LkN1ojt-heTCl7yPcJrhY

 Live meeting minutes: https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit?usp=sharing
Require Help NRF52840 PCA 10059

Muhammad Muh <muhammad.muh83@...>
 

Dear All,

It has been quite long that i emailed to this group. Hope everybody is fine and in good health. Coming towards the issue i am using nrf52840_PCA10059 Dongle. I am trying to do the example available in
Zephyr----> Sample------->Boards------>nrf52---------->onoff-app and onoff_level_lighting_vnd_app. When i use the WEST command by using board PCA 10056 they run fine and give no error. Moreover, when i run the following command with PCA 10059 i get the following error with both the examples. 

Command:  west build -b nrf52840_pca10059 .
Error: I am showing the last part of error
../src/mesh/publisher.c: In function 'publish':
../src/mesh/publisher.c:61:43: error: 'DT_ALIAS_SW1_GPIOS_PIN' undeclared (first use in this function); did you mean 'DT_ALIAS_SW0_GPIOS_PIN'?
  } else if (button_read(button_device[1], DT_ALIAS_SW1_GPIOS_PIN) == 0U) {
                                           ^~~~~~~~~~~~~~~~~~~~~~
                                           DT_ALIAS_SW0_GPIOS_PIN
../src/mesh/publisher.c:61:43: note: each undeclared identifier is reported only once for each function it appears in
../src/mesh/publisher.c:83:43: error: 'DT_ALIAS_SW2_GPIOS_PIN' undeclared (first use in this function); did you mean 'DT_ALIAS_SW0_GPIOS_PIN'?
  } else if (button_read(button_device[2], DT_ALIAS_SW2_GPIOS_PIN) == 0U) {
                                           ^~~~~~~~~~~~~~~~~~~~~~
                                           DT_ALIAS_SW0_GPIOS_PIN
../src/mesh/publisher.c:153:43: error: 'DT_ALIAS_SW3_GPIOS_PIN' undeclared (first use in this function); did you mean 'DT_ALIAS_SW0_GPIOS_PIN'?
  } else if (button_read(button_device[3], DT_ALIAS_SW3_GPIOS_PIN) == 0U) {
                                           ^~~~~~~~~~~~~~~~~~~~~~
                                           DT_ALIAS_SW0_GPIOS_PIN
ninja: build stopped: subcommand failed.
ERROR: command exited with status 1: /home/rg/cmake-3.13.1-Linux-x86_64/bin/cmake --build /home/rg/zephyrproject/zephyr/samples/boards/nrf52/mesh/onoff_level_lighting_vnd_app/build

It is requested to kindly advise on the aforementioned.

Best Regards
API meeting: Agenda

Carles Cufi
 

Hi all,

This week we will look at:

- V4Z: Update on comments, merge if there is no objections
- https://github.com/zephyrproject-rtos/zephyr/pull/17194

- EEPROM API proposal
- https://github.com/zephyrproject-rtos/zephyr/pull/19972

- GPIO: Update on progress
- Look at the PRs with driver conversion (https://github.com/zephyrproject-rtos/zephyr/issues/18530)
- Check users of GPIO APIs: https://github.com/zephyrproject-rtos/zephyr/issues/20017
- Any additional outstanding PRs to topic-gpio

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.

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: Supported devices

Maureen Helm
 

Hi Robert,

There is a pull request for RT1010. We’re still working on getting it into a mergeable state.

https://github.com/zephyrproject-rtos/zephyr/pull/19335

 

Maureen

 

From: devel@... <devel@...> On Behalf Of Robert Lewicki via Lists.Zephyrproject.Org
Sent: Sunday, October 20, 2019 11:27 AM
To: devel@...
Cc: devel@...
Subject: [Zephyr-devel] Supported devices

 

I sent an email previously and after going into the project and looking at the list of supported products, it seems as if the NXP i.MX RT1010 is not yet supported although the 1020 and others are.
Any ide when the 1010 would be supported, and how can I help? Can I try the 1020?
Thanks

Robert
EEPROMs as first-class devices in Zephyr

Henrik Brix Andersen
 

Hi all,

I have submitted and RFC for adding an EEPROM API to Zephyr RTOS here:
https://github.com/zephyrproject-rtos/zephyr/pull/19972

The idea behind this is a simple, byte-oriented API for EEPROM devices.

I have been implementing drivers for generic SPI EEPROMs (AT25xxx compatible) and I2C EEPROMs (AT24xxx compatible) under the Zephyr flash API, but it just doesn't feel right.

The EEPROM drivers need to implement the full flash API (What to do on erase? NO-OP? Write 0xFF to "erased" bytes thus affecting lifetime negatively? Something else?) and this type of devices generally aren't fit as backends for the various subsystems in Zephyr currently supporting the flash API as backend (e.g. the settings subsystem) due to assumptions about page layout and erase.

I would like to hear any comments and/or suggestions on how to approach integrating EEPROM devices in as first-class devices in Zephyr.

Comments and ideas are most welcome. Please submit them as comments to the Github issue in order to keep the conversation there.

Best regards,
Brix
--
Henrik Brix Andersen
Supported devices

Robert Lewicki <rlewicki@...>
 

I sent an email previously and after going into the project and looking at the list of supported products, it seems as if the NXP i.MX RT1010 is not yet supported although the 1020 and others are.
Any ide when the 1010 would be supported, and how can I help? Can I try the 1020?
Thanks
Robert
Usage of optional 'erase-block-size' flash nodes property

Erwan Gouriou
 

Hi all,

Optional property 'erase-block-size' is used to describe the minimum size of flash sector on which an erase operation could be applied. It is generated as a device tree generic define DT_FLASH_ERASE_BLOCK_SIZE (made generic through the use of chosen 'zephyr,flash').
It is optional since, on some parts (stm32f4, for instance), flash layout is made of several sectors of variable size and hence it cannot be provided.

So here is the issue since, on one side, we have a zephyr generic define, and on the other side, we have parts on which it does not exist. Problem is that it could happen that people use it in generic zephyr components, while it is not a generic property (cf last example: [1]).

Another issue with this define is that it appears to be simple and handy to use, but it is actually misleading since it is only available on embedded flash. So any flash based application, if trying to use it will fail on external flash.
Flash API actually provides an alternate, robust and generic 'flash_area_get_sectors' that will provide the same information with few more computations. And this is the solution to be used.

Unfortunately, there is no automatic way to prevent people using misleading DT_FLASH_ERASE_BLOCK_SIZE.

So the question I'm raising to you is how to avoid facing this issue every 3 months.
Once idea would be to remove it, but it is actually used in device specific embedded flash drivers where it does make sense.

If you're interested, don't hesitate to answer this mail, comment in related issue [1] or join dev_meeting next week.

Thanks
Erwan
Upcoming Event: Zephyr Project: Dev Meeting - Thu, 10/17/2019 8:00am-9:00am, Please RSVP #cal-reminder

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

Reminder: Zephyr Project: Dev Meeting

When: Thursday, 17 October 2019, 8:00am to 9:00am, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/993312203

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description: Join Zoom Meeting
https://zoom.us/j/993312203

One tap mobile
+16699006833,,993312203# US (San Jose)
+16465588656,,993312203# US (New York)

Dial by your location
        +1 669 900 6833 US (San Jose)
        +1 646 558 8656 US (New York)
        +1 877 369 0926 US Toll-free
        +1 855 880 1246 US Toll-free
Meeting ID: 993 312 203
Find your local number: https://zoom.us/u/ankEMRagf
Simultaneous BLE and ShockBurst #shockburst #ble #nrf52840

Mike DiClaudio
 

In my application, I need to use the nrf52840 for both BLE (as the controller) and ShockBurst. Specifically, it's the nrf52840 on the nrf9160 if it matters. I'm using the zephyr BLE stack and things are working well, but now I need to add the capability for the device to send occasional SB transmissions (send only, not receive). Do I need to manage the protocols sharing the radio, or is that handled by zephyr/nordic drivers?
following up on GPIO API - GH18530

Jennifer M Williams
 

 

@Cufi, Carles and @topic-gpio folks

 

Here’s some feedback I got for the drivers we discussed this morning for https://github.com/zephyrproject-rtos/zephyr/issues/18530

 

  1. altera_nios2 – suggest to drop from this list, no owner at this time for this convert driver effort.
  2. Pcal9535a – it’s on our radar, but unassigned at this time.

 

Thanks,

Jen
Calculating Log() in Zpehyr

William Fish
 

Help please,
Does Zephyr have a logarithm function?

Thanks;
Billy..
Upcoming Event: Zephyr Project: APIs - Tue, 10/15/2019 9:00am-10:00am, Please RSVP #cal-reminder

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

Reminder: Zephyr Project: APIs

When: Tuesday, 15 October 2019, 9:00am to 10:00am, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/177647878

An RSVP is requested. Click here to RSVP

Organizer: devel@...

Description: Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/177647878

Or iPhone one-tap :
    US: +16465588656,,177647878# or +16699006833,,177647878# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 177 647 878
    International numbers available: https://zoom.us/zoomconference?m=ioAR9GK1OE5LkN1ojt-heTCl7yPcJrhY

 Live meeting minutes: https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit?usp=sharing
API meeting: agenda

Carles Cufi
 

Hi all,

This week we will look at:

- V4Z: Update on the state of the Pull Request, should we merge it?
- https://github.com/zephyrproject-rtos/zephyr/pull/17194

- GPIO: Update on progress
- Look at the PRs with driver conversion (https://github.com/zephyrproject-rtos/zephyr/issues/18530)
- Check the timeline
- Any additional outstanding PRs to topic-gpio

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.

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: #nrf52 #custom_board #nrf52 #custom_board

leslieli@2ytech.cn
 

Hi ibraxim,

Try add below line in your prj.conf, it might solve your problem.

CONFIG_BOARD_ENABLE_DCDC=n

leslieli@...

 
From: ibraxim
Date: 2019-10-11 18:20
To: devel
Subject: [Zephyr-devel] #nrf52 #custom_board
Hello everyone,

I have a custom board based on the QIAA layout, when i try to flash the bluetooth beacon example from the zephyr samples directory, the board does not advertise at all(the board also doesn't work with other examples either). testing the same example on a similar board such as the nrf52840_pca10059 dongle, the application works perfectly.

please note that when using examples from the NRF5 SDK to flash this custom board, they work fine with no problem.

I'm flashing this board with the bootloader option set to n as it does not have one.

any help on how to progress from here is really appreciated

Re: #nrf52 #custom_board #nrf52 #custom_board

Tom Burdick
 

One other issue I just recalled was related to the console and not having a UART properly setup and pinned out, for my custom board I ended up using a USB console which worked out well.

Beyond that it would be hard to say without I think having my hands on the board.

Cheers,

Tom


On Fri, Oct 11, 2019 at 6:19 AM <ibraxim@...> wrote:
Hello everyone,

I have a custom board based on the QIAA layout, when i try to flash the bluetooth beacon example from the zephyr samples directory, the board does not advertise at all(the board also doesn't work with other examples either). testing the same example on a similar board such as the nrf52840_pca10059 dongle, the application works perfectly.

please note that when using examples from the NRF5 SDK to flash this custom board, they work fine with no problem.

I'm flashing this board with the bootloader option set to n as it does not have one.

any help on how to progress from here is really appreciated

Re: #nrf52 #custom_board #nrf52 #custom_board

Tom Burdick
 

Hi,

A few questions I think will help myself or others answer this easier...

I'm assuming you are able to flash the board

Are you using the same clock setup and crystal freqs as the dev board your basing this on?
Are you using the same dcdc regulator configuration?

Its been awhile since I brought up my own customer nrf52 board, but I recall having to tweak the DCDC option
SOC_DCDC_NRF52X for my first version of it since I ended up opting for external DCDC power management, and I recall
that leading to some issues.

Cheers

Tom


On Fri, Oct 11, 2019 at 6:19 AM <ibraxim@...> wrote:
Hello everyone,

I have a custom board based on the QIAA layout, when i try to flash the bluetooth beacon example from the zephyr samples directory, the board does not advertise at all(the board also doesn't work with other examples either). testing the same example on a similar board such as the nrf52840_pca10059 dongle, the application works perfectly.

please note that when using examples from the NRF5 SDK to flash this custom board, they work fine with no problem.

I'm flashing this board with the bootloader option set to n as it does not have one.

any help on how to progress from here is really appreciated

Re: Call for help: SAM0 GPIO driver

Peter A. Bigot
 

Assuming nobody more qualified speaks up I do have a D21 Xplained Pro and will give a shot at converting the driver this weekend.  People with D20 and R21 variant hardware would be helpful in testing it.

Peter
1201 - 1220 of 7600