Date   

Re: Segger RTT / Help or ? command

Carles Cufi
 

Hi there,

 

I believe RTT only currently supports output of characters, and not input.

There’s an issue logging this in case you want to follow it, or contribute code to improve this:

https://github.com/zephyrproject-rtos/zephyr/issues/8394

 

Carles

 

From: devel@... <devel@...> On Behalf Of muzammil.patel@...
Sent: 10 October 2018 06:32
To: devel@...
Subject: [Zephyr-devel] Segger RTT / Help or ? command

 

[Edited Message Follows]

 

Hi,

I have configured zephyr console to use the RTT viewer. I am able to receiving log data over RTT but not able to receive anything when sending commands (like 'help'). I have enabled RTT in the prj.conf file as below.

CONFIG_HAS_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n

Is there anything else that I am missing out?

I simply want the RTT viewer to get a response to 'help' command.

Thank you, 

 

Muzammil

 

 

 

 


Email from setec.com.au does not necessarily represent the official policy of SETEC Pty Ltd.
See Email Disclaimer 20060629 for details.


Re: [Zephyr-users] assertion fail in nordic nrf5 i2c driver

Marco Tozzini <lists@...>
 

Hi Manu,
I think I had the same problem and solved using the process showed here.
https://youtu.be/vioi4OsmB_U

Cheers,
Marco


On October 9, 2018 12:03:01 PM PDT, Manu R <manu@...> wrote:
Carles, I am trying to use 1.13 and am having some issues. I can build hello_world, but when i tried to build anything with i2c, I have issues. ( drivers__i2c was created without source files)
Thanks
Manu

build (master) $ ninja

[0/1] Re-running CMake...

CMake Warning at /Users/manurao/temp/zephyr/cmake/app/boilerplate.cmake:167 (message):

  The build directory must be cleaned pristinely when changing boards

Call Stack (most recent call first):

  CMakeLists.txt:3 (include)



-- Selected BOARD nrf52_pca10040

Zephyr version: 1.13.99

Parsing Kconfig tree in /Users/manurao/temp/zephyr/Kconfig

Loading /Users/manurao/temp/zephyr/samples/hello_world/build/zephyr/.config as base

CMake Warning at /Users/manurao/temp/zephyr/cmake/toolchain.cmake:48 (message):

  gccarmemb is deprecated, please use gnuarmemb instead

Call Stack (most recent call first):

  /Users/manurao/temp/zephyr/cmake/app/boilerplate.cmake:269 (include)

  CMakeLists.txt:3 (include)



-- Generating zephyr/include/generated/generated_dts_board.h

-- Cache files will be written to: /Users/manurao/Library/Caches/zephyr

CMake Error at ../../CMakeLists.txt:544 (message):

  The Zephyr library 'drivers__i2c' was created without source files.  Empty

  (non-imported) libraries are not supported.  Either make sure that the

  library has the sources it should have, or make sure it is not created when

  it has no source files.



-- Configuring incomplete, errors occurred!

See also "/Users/manurao/temp/zephyr/samples/hello_world/build/CMakeFiles/CMakeOutput.log".

See also "/Users/manurao/temp/zephyr/samples/hello_world/build/CMakeFiles/CMakeError.log".

FAILED: build.ninja 

/usr/local/Cellar/cmake/3.11.0/bin/cmake -H/Users/manurao/temp/zephyr/samples/hello_world -B/Users/manurao/temp/zephyr/samples/hello_world/build

ninja: error: rebuilding 'build.ninja': subcommand failed

build (master) $ 


On Tue, Oct 9, 2018 at 12:58 AM Cufi, Carles <Carles.Cufi@...> wrote:

Hi Manu,

 

The I2C driver has since been completely rewritten to use nrfx, our common driver codebase.

Would it be possible for you to try with current master (or at least 1.13) to see if you still face the issues you mention?

 

Carles

 

From: users@... <users@...> On Behalf Of Manu R
Sent: 08 October 2018 18:56
To: devel@...; users@...
Subject: [Zephyr-users] assertion fail in nordic nrf5 i2c driver

 

Hi all, 

I am using a lis2dh12 with a nrf52840, and am on occasion seeing an assertion. 

It happens in the i2c_nrf5_read

 

err=0 txd=0 rxd=0 stopped=0 errsrc=0x0

ASSERTION FAIL [data->stopped] @ <snip>/zephyr_new/drivers/i2c/i2c_nrf5.c:142:

 

We are based off of 5890004ea72066fb4b1e8100bb289fb5a00646a5 ( r 1.12)

 

Can someone shed light on whats happening? It looks like I am waiting for the EVENTS_STOPPED to hit in the isr, but seeing the data->stopped is not set, perhaps its not?

Are there any remedies? It looks like this condition should be benign, am I mistaken?

 

Thanks

Manu


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Re: [Zephyr-users] assertion fail in nordic nrf5 i2c driver

Giuliano Franchetto <giuliano.franchetto@...>
 

Hi Manu,

Please try with the following configs:

CONFIG_I2C=y
CONFIG_I2C_0_NRF_TWI=y
CONFIG_I2C_0=y
CONFIG_I2C_NRFX=y
CONFIG_I2C_0_NRF_TWI=y
CONFIG_NRFX_TWI=y

Some of these configurations may not be mandatory, but it should work.

Best regards
Giuliano FRANCHETTO
_______________________________________________________
Giuliano FRANCHETTO
CTO
https://intellinium.io

Office : +33 9 82 59 33 01
Mobile : +33 6 73 14 95 12
Email : giuliano.franchetto@intellinium.com

Société INTELLINIUM
Technopôle Arbois-Méditerranée,
Av. Louis Philibert, Bât. Laennec Hall A,
13857 Aix en Provence Cedex 3 (France)
________________________________________________________

-----Message d'origine-----
De : users@lists.zephyrproject.org <users@lists.zephyrproject.org> De la part de Himanshu Jha
Envoyé : mercredi 10 octobre 2018 07:01
À : Manu R <manu@culvertengineering.com>
Cc : Cufi, Carles <Carles.Cufi@nordicsemi.no>; devel@lists.zephyrproject.org; users@lists.zephyrproject.org; Głąbek, Andrzej <Andrzej.Glabek@nordicsemi.no>; Mieruński, Mieszko <Mieszko.Mierunski@nordicsemi.no>
Objet : Re: [Zephyr-devel] [Zephyr-users] assertion fail in nordic nrf5 i2c driver

Hi Manu,

On Tue, Oct 09, 2018 at 12:03:01PM -0700, Manu R wrote:
Carles, I am trying to use 1.13 and am having some issues. I can build
hello_world, but when i tried to build anything with i2c, I have
issues. ( drivers__i2c was created without source files)
Try this:

diff --git a/samples/drivers/i2c_fujitsu_fram/prj.conf b/samples/drivers/i2c_fujitsu_fram/prj.conf
index f9659582c..484e813e7 100644
--- a/samples/drivers/i2c_fujitsu_fram/prj.conf
+++ b/samples/drivers/i2c_fujitsu_fram/prj.conf
@@ -1,4 +1,4 @@
CONFIG_STDOUT_CONSOLE=y
CONFIG_PRINTK=y

-CONFIG_I2C=y
+#CONFIG_I2C=y


After this you can select whatever CONFIG you want to select in the `ninja menuconfig`.

Also, just to test that your board and environment, I would first suggest trying sample programs:
https://docs.zephyrproject.org/latest/boards/arm/nrf52840_pca10056/doc/nrf52840_pca10056.html#testing-the-leds-and-buttons-in-the-nrf52840-pdk

Flash these samples and test to see everything is fine.

HTH,
Thanks
--
Himanshu Jha
Undergraduate Student
Department of Electronics & Communication Guru Tegh Bahadur Institute of Technology


Regarding the fxos8700 (accelerometer) program

Hossain, Md Kowsar <mdkowsar-hossain@...>
 

Hello,


I was trying to understand how and when interrupts occur in accelerometer program, how and when the thread switching happens.


Could you please help me regarding this issue?


Thanks

Kowsar


Re: [Zephyr-users] assertion fail in nordic nrf5 i2c driver

Himanshu Jha <himanshujha199640@...>
 

Hi Manu,

On Tue, Oct 09, 2018 at 12:03:01PM -0700, Manu R wrote:
Carles, I am trying to use 1.13 and am having some issues. I can build
hello_world, but when i tried to build anything with i2c, I have issues. (
drivers__i2c was created without source files)
Try this:

diff --git a/samples/drivers/i2c_fujitsu_fram/prj.conf b/samples/drivers/i2c_fujitsu_fram/prj.conf
index f9659582c..484e813e7 100644
--- a/samples/drivers/i2c_fujitsu_fram/prj.conf
+++ b/samples/drivers/i2c_fujitsu_fram/prj.conf
@@ -1,4 +1,4 @@
CONFIG_STDOUT_CONSOLE=y
CONFIG_PRINTK=y

-CONFIG_I2C=y
+#CONFIG_I2C=y


After this you can select whatever CONFIG you want to select
in the `ninja menuconfig`.

Also, just to test that your board and environment, I would first
suggest trying sample programs:
https://docs.zephyrproject.org/latest/boards/arm/nrf52840_pca10056/doc/nrf52840_pca10056.html#testing-the-leds-and-buttons-in-the-nrf52840-pdk

Flash these samples and test to see everything is fine.

HTH,
Thanks
--
Himanshu Jha
Undergraduate Student
Department of Electronics & Communication
Guru Tegh Bahadur Institute of Technology


Segger RTT / Help or ? command

Muzammil Patel
 
Edited



Hi,
I have configured zephyr console to use the RTT viewer. I am able to receiving log data over RTT but not able to receive anything when sending commands (like 'help'). I have enabled RTT in the prj.conf file as below.
CONFIG_HAS_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n
Is there anything else that I am missing out?
I simply want the RTT viewer to get a response to 'help' command.

Thank you, 
 
Muzammil
 
 
 


Email from setec.com.au does not necessarily represent the official policy of SETEC Pty Ltd.
See Email Disclaimer 20060629 for details.


Re: [Zephyr-users] assertion fail in nordic nrf5 i2c driver

Manu R
 

Carles, I am trying to use 1.13 and am having some issues. I can build hello_world, but when i tried to build anything with i2c, I have issues. ( drivers__i2c was created without source files)
Thanks
Manu

build (master) $ ninja

[0/1] Re-running CMake...

CMake Warning at /Users/manurao/temp/zephyr/cmake/app/boilerplate.cmake:167 (message):

  The build directory must be cleaned pristinely when changing boards

Call Stack (most recent call first):

  CMakeLists.txt:3 (include)



-- Selected BOARD nrf52_pca10040

Zephyr version: 1.13.99

Parsing Kconfig tree in /Users/manurao/temp/zephyr/Kconfig

Loading /Users/manurao/temp/zephyr/samples/hello_world/build/zephyr/.config as base

CMake Warning at /Users/manurao/temp/zephyr/cmake/toolchain.cmake:48 (message):

  gccarmemb is deprecated, please use gnuarmemb instead

Call Stack (most recent call first):

  /Users/manurao/temp/zephyr/cmake/app/boilerplate.cmake:269 (include)

  CMakeLists.txt:3 (include)



-- Generating zephyr/include/generated/generated_dts_board.h

-- Cache files will be written to: /Users/manurao/Library/Caches/zephyr

CMake Error at ../../CMakeLists.txt:544 (message):

  The Zephyr library 'drivers__i2c' was created without source files.  Empty

  (non-imported) libraries are not supported.  Either make sure that the

  library has the sources it should have, or make sure it is not created when

  it has no source files.



-- Configuring incomplete, errors occurred!

See also "/Users/manurao/temp/zephyr/samples/hello_world/build/CMakeFiles/CMakeOutput.log".

See also "/Users/manurao/temp/zephyr/samples/hello_world/build/CMakeFiles/CMakeError.log".

FAILED: build.ninja 

/usr/local/Cellar/cmake/3.11.0/bin/cmake -H/Users/manurao/temp/zephyr/samples/hello_world -B/Users/manurao/temp/zephyr/samples/hello_world/build

ninja: error: rebuilding 'build.ninja': subcommand failed

build (master) $ 


On Tue, Oct 9, 2018 at 12:58 AM Cufi, Carles <Carles.Cufi@...> wrote:

Hi Manu,

 

The I2C driver has since been completely rewritten to use nrfx, our common driver codebase.

Would it be possible for you to try with current master (or at least 1.13) to see if you still face the issues you mention?

 

Carles

 

From: users@... <users@...> On Behalf Of Manu R
Sent: 08 October 2018 18:56
To: devel@...; users@...
Subject: [Zephyr-users] assertion fail in nordic nrf5 i2c driver

 

Hi all, 

I am using a lis2dh12 with a nrf52840, and am on occasion seeing an assertion. 

It happens in the i2c_nrf5_read

 

err=0 txd=0 rxd=0 stopped=0 errsrc=0x0

ASSERTION FAIL [data->stopped] @ <snip>/zephyr_new/drivers/i2c/i2c_nrf5.c:142:

 

We are based off of 5890004ea72066fb4b1e8100bb289fb5a00646a5 ( r 1.12)

 

Can someone shed light on whats happening? It looks like I am waiting for the EVENTS_STOPPED to hit in the isr, but seeing the data->stopped is not set, perhaps its not?

Are there any remedies? It looks like this condition should be benign, am I mistaken?

 

Thanks

Manu


Re: [Zephyr-users] assertion fail in nordic nrf5 i2c driver

Manu R
 

Carles, appreciate the response. 
That was definitely one of my experiments to try. 
However, we have had a relatively stable base with r1.12 and I am not sure we can change to 1.13 without some regression testing. 

I will certainly try 1.13 and update you. 

(A different issue I see in the driver is related to the power consumption being high(~1ma) for ~1.2s after i2c transactions are done. Any idea what that might be?)
Thanks a lot, I appreciate the help. 
M

On Tue, Oct 9, 2018 at 12:58 AM Cufi, Carles <Carles.Cufi@...> wrote:

Hi Manu,

 

The I2C driver has since been completely rewritten to use nrfx, our common driver codebase.

Would it be possible for you to try with current master (or at least 1.13) to see if you still face the issues you mention?

 

Carles

 

From: users@... <users@...> On Behalf Of Manu R
Sent: 08 October 2018 18:56
To: devel@...; users@...
Subject: [Zephyr-users] assertion fail in nordic nrf5 i2c driver

 

Hi all, 

I am using a lis2dh12 with a nrf52840, and am on occasion seeing an assertion. 

It happens in the i2c_nrf5_read

 

err=0 txd=0 rxd=0 stopped=0 errsrc=0x0

ASSERTION FAIL [data->stopped] @ <snip>/zephyr_new/drivers/i2c/i2c_nrf5.c:142:

 

We are based off of 5890004ea72066fb4b1e8100bb289fb5a00646a5 ( r 1.12)

 

Can someone shed light on whats happening? It looks like I am waiting for the EVENTS_STOPPED to hit in the isr, but seeing the data->stopped is not set, perhaps its not?

Are there any remedies? It looks like this condition should be benign, am I mistaken?

 

Thanks

Manu


Re: [Zephyr-users] assertion fail in nordic nrf5 i2c driver

Carles Cufi
 

Hi Manu,

 

The I2C driver has since been completely rewritten to use nrfx, our common driver codebase.

Would it be possible for you to try with current master (or at least 1.13) to see if you still face the issues you mention?

 

Carles

 

From: users@... <users@...> On Behalf Of Manu R
Sent: 08 October 2018 18:56
To: devel@...; users@...
Subject: [Zephyr-users] assertion fail in nordic nrf5 i2c driver

 

Hi all, 

I am using a lis2dh12 with a nrf52840, and am on occasion seeing an assertion. 

It happens in the i2c_nrf5_read

 

err=0 txd=0 rxd=0 stopped=0 errsrc=0x0

ASSERTION FAIL [data->stopped] @ <snip>/zephyr_new/drivers/i2c/i2c_nrf5.c:142:

 

We are based off of 5890004ea72066fb4b1e8100bb289fb5a00646a5 ( r 1.12)

 

Can someone shed light on whats happening? It looks like I am waiting for the EVENTS_STOPPED to hit in the isr, but seeing the data->stopped is not set, perhaps its not?

Are there any remedies? It looks like this condition should be benign, am I mistaken?

 

Thanks

Manu


Strange power consumption _after_ I2C transactions on nrf52840

Manu R
 

Hi All,

We have a custom board with a nrf52840 and multiple I2C devices( accel, pressure, etc).

We noticed that anytime we do an I2C transaction ( reads in particular), the current draw is abnormally high ( ~1 mA) for almost 1.2 seconds after the transaction ! After that, it drops to our system normal ( ~55uA).

In the i2c_nrf5_transfer function, the TWI is disabled around line 249. When I add a k_sleep() before this instruction, the current stays high for that much longer. when I do it after this, it doesnt change the 1.2second pulse.
...
twi->ENABLE = TWI_ENABLE_ENABLE_Disabled;

From this, I surmise that there is some delayed mechanism after the disable IN THE TWI PERIPHERAL I hypothesize that its not my i2c device since the same thing happens with other devices on my bus as well.

Can anyone from nordic please shed some light on this? 
Much obliged!
Manu Rao


cant read device using i2c sample code on nrf52

gurpreet+zephy@...
 

I'm trying to run the sample i2c code from samples/drivers/i2c_fujitsu_fram on my board. 
I've tweaked the address to use the i2c address of my device, and am trying to read the who_am_i register, but to no avail. 

My prj.conf is
CONFIG_STDOUT_CONSOLE=y
CONFIG_PRINTK=y
CONFIG_I2C=y
CONFIG_I2C_NRFX=y
CONFIG_I2C_0_NRF_TWIM=y
CONFIG_I2C_INIT_PRIORITY=60
CONFIG_I2C_0=y

Is there something else I need to be doing to get this to work?

-Gurpreet 


assertion fail in nordic nrf5 i2c driver

Manu R
 

Hi all, 
I am using a lis2dh12 with a nrf52840, and am on occasion seeing an assertion. 
It happens in the i2c_nrf5_read

err=0 txd=0 rxd=0 stopped=0 errsrc=0x0
ASSERTION FAIL [data->stopped] @ <snip>/zephyr_new/drivers/i2c/i2c_nrf5.c:142:

We are based off of 5890004ea72066fb4b1e8100bb289fb5a00646a5 ( r 1.12)

Can someone shed light on whats happening? It looks like I am waiting for the EVENTS_STOPPED to hit in the isr, but seeing the data->stopped is not set, perhaps its not?
Are there any remedies? It looks like this condition should be benign, am I mistaken?

Thanks
Manu


Re: HCI_UART

Cale Collins <ccollins@...>
 

Charles,

Thank you very much for the advice, I figured out that I built the .hex file with the incorrect parameters: 

cmake -DBOARD=nrf52840_pca10059 ../..

When I needed:

cmake -DBOARD=nrf52840_pca10056 ../..

HCI_UART is working magnificently now. 


Best regards, 


Cale Collins
Field Application Engineer
Gateworks Corporation
3026 S. Higuera, SLO, CA 93401
T: (805)781-2000 x37

On Wed, Oct 3, 2018 at 2:38 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Cale,

 

The controller doesn´t seem to be responding to the Reset command, as if perhaps the serial (UART) connection was not working.

Can you try building and flashing the “hello_world” sample and visualize the output using minicom or similar, to make sure the serial link is working?

 

Carles

 

From: Cale Collins <ccollins@...>
Date: Wednesday, 3 October 2018 at 20:48
To: "Cufi, Carles" <Carles.Cufi@...>
Cc: "devel@..." <devel@...>, Luiz Augusto von Dentz <luiz.dentz@...>
Subject: Re: [Zephyr-devel] HCI_UART

 

Charles, 

 

Thank you very much for the reply.  

 

Here is a paste-bin of the logs you requested.  Please let me know if there's any further information you would like me to provide.  

 

 

Best regards, 


Cale Collins
Field Application Engineer
Gateworks Corporation

3026 S. Higuera, SLO, CA 93401
T: (805)781-2000 x37

 

On Wed, Oct 3, 2018 at 8:56 AM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi there,

 

Could you please attach a btmon log of the attach procedure?

 

On one shell run “sudo btmon”

On another shell then run: “sudo btattach -B /dev/ttyACM0 -S 1000000”

 

And then attach the log output from btmon in an email or paste service.

 

Also, have you tried “sudo btmgmt --index 0”? i.e. specifying the index when invoking btmgmt?

 

Carles

 

From: devel@... <devel@...> On Behalf Of Cale Collins
Sent: 03 October 2018 17:43
To: devel@...
Subject: [Zephyr-devel] HCI_UART

 

Hello,

 

I have built and installed HCI_UART to nRF52840 Nordic Development kit.  When I connect this device it appears with "lsusb", seemingly I can attach it using "btattach -B /dev/ttyACM0 -S 1000000", revealing hci0.  I have made the recommended adaptation to "/lib/systemd/system/bluetooth.service", appending -E to the "ExecStart=/usr/lib/bluetooth/bluetoothd -E" line.

 

When issuing commands with "btmgmt", "btmon" reports "Invalid Index (0x11)".  Normal HCI commands fail such as "hciconfig hci0 up".  

 

Using Bionic-Beaver Ubuntu, 4.15 kernel, Bluez 5.48, also tested with Xenial Ubuntu 4.15 kernel, Bluez 5.50.  Any suggestions would be greatly appreciated. 

 

Best regards, 

 

Cale Collins
Field Application Engineer
Gateworks Corporation

3026 S. Higuera, SLO, CA 93401
T: (805)781-2000 x37

 



Re: Bluetooth: about latest Kernel OOPS

vikrant8051 <vikrant8051@...>
 

Hi Carles,
Oh !! That's Great news !!


On Fri, Oct 5, 2018 at 1:49 PM Cufi, Carles <Carles.Cufi@...> wrote:
Fix is now merged: https://github.com/zephyrproject-rtos/zephyr/pull/10391


> -----Original Message-----
> From: Chettimada, Vinayak Kariappa
> Sent: 05 October 2018 09:54
> To: vikrant8051 <vikrant8051@...>; devel@...;
> Cufi, Carles <Carles.Cufi@...>
> Subject: Re: [Zephyr-devel] Bluetooth: about latest Kernel OOPS
>
> Hi Vikrant,
>
> It appears a recent merged PR has introduced regression.
> https://github.com/zephyrproject-rtos/zephyr/pull/10289
>
> I am analysing the issue, meanwhile you can revert the said commit so as
> to unblock your tasks.
>
> Regards,
> Vinayak
>
> -----Original Message-----
> From: <devel@...> on behalf of vikrant8051
> <vikrant8051@...>
> Date: Friday, 5 October 2018 at 9:37 AM
> To: "devel@..." <devel@...>,
> Carles Cufi <Carles.Cufi@...>
> Subject: [Zephyr-devel] Bluetooth: about latest Kernel OOPS
>
>     Hi,
>     Today I synced my local repo with Zephyr master & while testing with
>
>     Bluetooth Mesh App I got following Kernel OOPS:
>
>
>     ***** Kernel OOPS! *****
>
>     Current thread ID = 0x200018c0
>
>     Faulting instruction address = 0x16d84
>
>     Fatal fault in ISR! Spinning...
>
>
>     I executed following command :
>
>     /opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-
> eabi/arm-zephyr-eabi-addr2line -e zephyr.elf 0x16d84
>
>
>     o/p ->
>     /home/vikrant/zephyr/subsys/bluetooth/controller/ll_sw/ctrl.c:6353
>
>
>     Please suggest me how to overcome this.
>
>
>     Thank You !!
>
>
>
>
>
>
>
> >


Re: Choosing Tx Buffers in BLE stack

Carles Cufi
 

Note that if you do not own a BLE sniffer you can still use a Nordic board to sniff traffic over the air:

https://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF-Sniffer

Carles

-----Original Message-----
From: devel@lists.zephyrproject.org <devel@lists.zephyrproject.org> On
Behalf Of Chettimada, Vinayak Kariappa
Sent: 05 October 2018 10:36
To: dhguja@gmail.com; devel@lists.zephyrproject.org
Subject: Re: [Zephyr-devel] Choosing Tx Buffers in BLE stack

Do you have a sniffer trace you can send to me email?

It appears the peer is not responding to a control procedure.

-Vinayak

-----Original Message-----
From: <devel@lists.zephyrproject.org> on behalf of "dhguja@gmail.com"
<dhguja@gmail.com>
Date: Thursday, 4 October 2018 at 11:19 AM
To: "devel@lists.zephyrproject.org" <devel@lists.zephyrproject.org>
Subject: Re: [Zephyr-devel] Choosing Tx Buffers in BLE stack




Hello All,
I did some more debugging on my problem and i noticed that
whenever the characters are stopped receiving by windows host i get a
disconnection in my device with either
LMP RESPONSE TIMEOUT / LL RESPONSE TIMEOUT (0x22) or CONNECTION
TIMEOUT (0x08)
always.

Is this expected on the zephyr side? Is there anything else i can do
from my device perspective?


I also posted my queries in MS forums and waiting for some solution
there too.

Thanks for the help.
Dhananjay G J





Re: Choosing Tx Buffers in BLE stack

Chettimada, Vinayak Kariappa
 

Do you have a sniffer trace you can send to me email?

It appears the peer is not responding to a control procedure.

-Vinayak

-----Original Message-----
From: <devel@lists.zephyrproject.org> on behalf of "dhguja@gmail.com" <dhguja@gmail.com>
Date: Thursday, 4 October 2018 at 11:19 AM
To: "devel@lists.zephyrproject.org" <devel@lists.zephyrproject.org>
Subject: Re: [Zephyr-devel] Choosing Tx Buffers in BLE stack




Hello All,
I did some more debugging on my problem and i noticed that whenever the characters are stopped receiving by windows host i get a disconnection in my device with either
LMP RESPONSE TIMEOUT / LL RESPONSE TIMEOUT (0x22) or CONNECTION TIMEOUT (0x08)
always.

Is this expected on the zephyr side? Is there anything else i can do from my device perspective?


I also posted my queries in MS forums and waiting for some solution there too.

Thanks for the help.
Dhananjay G J


Re: Bluetooth: about latest Kernel OOPS

Carles Cufi
 

-----Original Message-----
From: Chettimada, Vinayak Kariappa
Sent: 05 October 2018 09:54
To: vikrant8051 <vikrant8051@gmail.com>; devel@lists.zephyrproject.org;
Cufi, Carles <Carles.Cufi@nordicsemi.no>
Subject: Re: [Zephyr-devel] Bluetooth: about latest Kernel OOPS

Hi Vikrant,

It appears a recent merged PR has introduced regression.
https://github.com/zephyrproject-rtos/zephyr/pull/10289

I am analysing the issue, meanwhile you can revert the said commit so as
to unblock your tasks.

Regards,
Vinayak

-----Original Message-----
From: <devel@lists.zephyrproject.org> on behalf of vikrant8051
<vikrant8051@gmail.com>
Date: Friday, 5 October 2018 at 9:37 AM
To: "devel@lists.zephyrproject.org" <devel@lists.zephyrproject.org>,
Carles Cufi <Carles.Cufi@nordicsemi.no>
Subject: [Zephyr-devel] Bluetooth: about latest Kernel OOPS

Hi,
Today I synced my local repo with Zephyr master & while testing with

Bluetooth Mesh App I got following Kernel OOPS:


***** Kernel OOPS! *****

Current thread ID = 0x200018c0

Faulting instruction address = 0x16d84

Fatal fault in ISR! Spinning...


I executed following command :

/opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-
eabi/arm-zephyr-eabi-addr2line -e zephyr.elf 0x16d84


o/p ->
/home/vikrant/zephyr/subsys/bluetooth/controller/ll_sw/ctrl.c:6353


Please suggest me how to overcome this.


Thank You !!










Re: Bluetooth: about latest Kernel OOPS

Chettimada, Vinayak Kariappa
 

Hi Vikrant,

It appears a recent merged PR has introduced regression. https://github.com/zephyrproject-rtos/zephyr/pull/10289

I am analysing the issue, meanwhile you can revert the said commit so as to unblock your tasks.

Regards,
Vinayak

-----Original Message-----
From: <devel@lists.zephyrproject.org> on behalf of vikrant8051 <vikrant8051@gmail.com>
Date: Friday, 5 October 2018 at 9:37 AM
To: "devel@lists.zephyrproject.org" <devel@lists.zephyrproject.org>, Carles Cufi <Carles.Cufi@nordicsemi.no>
Subject: [Zephyr-devel] Bluetooth: about latest Kernel OOPS

Hi,
Today I synced my local repo with Zephyr master & while testing with

Bluetooth Mesh App I got following Kernel OOPS:


***** Kernel OOPS! *****

Current thread ID = 0x200018c0

Faulting instruction address = 0x16d84

Fatal fault in ISR! Spinning...


I executed following command :

/opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e zephyr.elf 0x16d84


o/p ->
/home/vikrant/zephyr/subsys/bluetooth/controller/ll_sw/ctrl.c:6353


Please suggest me how to overcome this.


Thank You !!


Bluetooth: about latest Kernel OOPS

vikrant8051 <vikrant8051@...>
 

Hi,
Today I synced my local repo with Zephyr master & while testing with
Bluetooth Mesh App I got following Kernel OOPS:

***** Kernel OOPS! *****                                                                                                         
Current thread ID = 0x200018c0                                                                                                   
Faulting instruction address = 0x16d84                                                                                           
Fatal fault in ISR! Spinning...

I executed following command :
/opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e zephyr.elf 0x16d84

o/p ->
/home/vikrant/zephyr/subsys/bluetooth/controller/ll_sw/ctrl.c:6353

Please suggest me how to overcome this.

Thank You !!



Type-C PD (TCPC / TCPM)

david <david@...>
 

Hi,

Checking in if anyone has been looking at generic USB Type-C PD support?

There are obviously various ways this is dealt with in products on the market,
some uses more primitive PHY's + a big chunk of driver-code running on cpu,
some are completely standalone (proprietary / less flexible) with it's own little
cpu & binary that can operate autonomously or via a high-level serial-protocol.

Then there are parts supporting TCPC / TCPM, where the 'port-manager' runs
on the host cpu talking to the phy via (I assume) a somewhat standardized
protocol that should be generic between PD IC's supporting it.


Thoughts?


best David

2881 - 2900 of 8113