Date   

Re: flash testing app(soc_flash_nrf5) fails to complete when using segger RTT.

Carles Cufi
 

I actually combined RTT and UART output to be able to debug this better, and it turns out that the program is not hanging, it does reach the end of main(), it's just that the RTT log output is not coming out, for whatever the reason.

Carles

-----Original Message-----
From: devel@... <devel@...> On
Behalf Of Cufi, Carles
Sent: 30 May 2018 17:08
To: Abderrezak Mekkaoui <ab.mekka@...>;
devel@...; Chruściński, Krzysztof
<Krzysztof.Chruscinski@...>; Puzdrowski, Andrzej
<Andrzej.Puzdrowski@...>
Subject: Re: [Zephyr-devel] flash testing app(soc_flash_nrf5) fails to
complete when using segger RTT.

Hi Adberrezak,

I can reproduce the same issue here locally. I am copying Krzysztof and
Andrzej to let them know, it might be that RTT has an issue with flash
writes.

Regards,

Carles

-----Original Message-----
From: devel@... <devel@...> On
Behalf Of Abderrezak Mekkaoui
Sent: 30 May 2018 16:51
To: devel@...
Subject: [Zephyr-devel] flash testing app(soc_flash_nrf5) fails to
complete when using segger RTT.

Hi All,

When running the zephyr supplied flash test sample
(..\zephyr\samples\drivers\soc_flash_nrf5), it produces the correct
output when using the regular UART console.
But when I switch to the segger RTT it hangs before completing.
I would appreciate If you have any input on why this might be
happening.
Is there any special precaution one has to observe when using the
segger RTT?
Thank you

Abderrezak


================================================================

..\zephyr\samples\drivers\soc_flash_nrf5

Output when using the segger RTT:

***** BOOTING ZEPHYR OS v1.11.0 - BUILD: May 29 2018 21:58:25 *****

Nordic nRF5 Flash Testing
=========================

Test 1: Flash erase page at 0x40000
   Flash erase succeeded!

Test 2: Flash write (word array 1)
   Attempted to write 1122 at 0x40000
   Attempted to read 0x40000
   Data read: 1122
   Data read matches data written. Good!
   Attempted to write aabb at 0x40004
   Attempted to read 0x40004
   Data read: aabb
   Data read matches data written. Good!
   Attempted to write abcd at 0x40008
   Attempted to read 0x40008
   Data read: abcd
   Data read matches data written. Good!
   Attempted to write 1234 at 0x4000c
   Attempted to read 0x4000c
   Data read: 1234
   Data read matches data written. Good!

Test 3: Flash erase (4 pages at 0x3e000)
   Flash erase succeeded!

Test 4: Flash write (word array 2)
   Attempted to write 1234 at 0x40000
   Attempted to read 0x40000
   Data read: 1234
   Data read matches data written. Good!
   Attempted to write aabb at 0




Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception #bluetoothmesh

Boie, Andrew P
 

What board is this on? Check for stack overflow, on devices with NXP MPUs these get reported as bus faults.

 

Andrew

 

From: users@... [mailto:users@...] On Behalf Of Cufi, Carles
Sent: Wednesday, May 30, 2018 7:00 AM
To: Vikrant More <vikrant8051@...>
Cc: Von Dentz, Luiz <luiz.von.dentz@...>; Hedberg, Johan <johan.hedberg@...>; devel@...; users@...
Subject: Re: [Zephyr-devel] [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

This is starting to look more and more like a memory corruption or kernel issue at this point.

I cannot reproduce this easily by running our standard Bluetooth samples, so I am a bit at a loss here. I will try to run a mesh sample to see if it fails in the same way.

 

From: Vikrant More <vikrant8051@...>
Sent: 30 May 2018 13:05
To: Cufi, Carles <carles.cufi@...>
Cc: Von Dentz, Luiz <luiz.von.dentz@...>; Johan Hedberg <johan.hedberg@...>; devel@...; users@...
Subject: Re: [Zephyr-devel] [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hi to all,

 

Suddenly get this non-stoppable FAULT

 

***** BUS FAULT *****
  Executing thread ID (thread): 0x20000220
  Faulting instruction address:  0x1c9a4
  Precise data bus error
  Address: 0xe5f7ffbe
Fatal fault in thread 0x20000220! Aborting.

 

Input -->

 

#/opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e /home/vikrant/projects/zephyr/zephyr/samples/bluetooth/mesh2/build/zephyr/zephyr.elf 0x1c9a4

 

Output -->

 

/home/vikrant/projects/zephyr/zephyr/kernel/include/ksched.h:153

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

Thank You !!

 

 

 

 

 

On Wed, May 30, 2018 at 4:20 PM, vikrant8051 <vikrant8051@...> wrote:

Hi Carles,

 

Now get these FAULT/OOPS,

 

***** MPU FAULT *****

  Executing thread ID (thread): 0x20001eb0
  Faulting instruction address:  0x200006b8
  Instruction Access Violation
Fatal fault in thread 0x20001eb0! Aborting.
***** USAGE FAULT *****
  Executing thread ID (thread): 0x20001eb0
  Faulting instruction address:  0x200006b8
  Illegal load of EXC_RETURN into PC
Fatal fault in thread 0x20001eb0! Aborting.
***** USAGE FAULT *****
  Executing thread ID (thread): 0x20001eb0
  Faulting instruction address:  0x200006b8
  Illegal load of EXC_RETURN into PC
Fatal fault in thread 0x20001eb0! Aborting.
***** Kernel OOPS! *****
Current thread ID = 0x20001eb0
Faulting instruction address = 0x14f10

Fatal fault in ISR! Spinning...

 

 

 

Input -->

 

#/opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e /home/vikrant/projects/zephyr/zephyr/samples/bluetooth/mesh2/build/zephyr/zephyr.elf 0x14f10

 

Output -->

 

/home/vikrant/projects/zephyr/zephyr/subsys/bluetooth/controller/ll_sw/ctrl.c:4702

 

 

Thanks !!

 

 

On Wed, May 30, 2018 at 4:11 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Vikrant,

 

Thanks for looking into this. It seems like we do not get a buffer back from the command tx queue: https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/bluetooth/host/hci_core.c#L3318

 

I have copied Luiz and Johan from Intel in case they know what the cause might be.

 

Regards,

 

Carles

 

From: users@... <users@...> On Behalf Of vikrant8051
Sent: 30 May 2018 12:31


To: Cufi, Carles <carles.cufi@...>
Cc: devel@...; users@...
Subject: Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hi Carles,

 

Input ->

/opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e /home/vikrant/projects/zephyr/zephyr/samples/bluetooth/mesh2/build/zephyr/zephyr.elf 0x5222

 

Output ->

/home/vikrant/projects/zephyr/zephyr/subsys/bluetooth/host/hci_core.c:3318

 

Thank You !!

 

On Wed, May 30, 2018 at 3:51 PM, Cufi, Carles <Carles.Cufi@...> wrote:

If you are using the Zephyr SDK:

 

path-to-zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e zephyr.elf <addr>

 

Carles

 

 

From: Vikrant More <vikrant8051@...>
Sent: 30 May 2018 12:11
To: Cufi, Carles <carles.cufi@...>
Cc: devel@...; users@...
Subject: Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hi Carles,

 

I will but don't know, how to do that ?

 

 

On Wed, May 30, 2018 at 3:19 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Vikrant,

 

Can you please run addr2line with this address present in the error log: 0x5222?

 

Thanks,

 

Carles

 

From: users@... <users@...> On Behalf Of vikrant8051
Sent: 30 May 2018 11:29
To: devel@...; users@...
Subject: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hello World !!

 

Today after upgrading to v1.12.0-rc2, I'm getting following error while playing with sample code which is inspired from sample/bluetooth/mesh

 

 

[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [ERR] event_scan_prepare: assert: '!_radio.ticker_id_prepare' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x1b77e
Fatal fault in ISR! Spinning...

 

-------------------------------------------------------------------------------------------------------------------------

 

Sometime it completely hangs & nothing get displayed on debug terminal

 

-------------------------------------------------------------------------------------------------------------------------

 

Thank You !!

 

 

 

 

 

 

 

 

 


Re: flash testing app(soc_flash_nrf5) fails to complete when using segger RTT.

Carles Cufi
 

Hi Adberrezak,

I can reproduce the same issue here locally. I am copying Krzysztof and Andrzej to let them know, it might be that RTT has an issue with flash writes.

Regards,

Carles

-----Original Message-----
From: devel@... <devel@...> On
Behalf Of Abderrezak Mekkaoui
Sent: 30 May 2018 16:51
To: devel@...
Subject: [Zephyr-devel] flash testing app(soc_flash_nrf5) fails to
complete when using segger RTT.

Hi All,

When running the zephyr supplied flash test sample
(..\zephyr\samples\drivers\soc_flash_nrf5), it produces the correct
output when using the regular UART console.
But when I switch to the segger RTT it hangs before completing.
I would appreciate If you have any input on why this might be happening.
Is there any special precaution one has to observe when using the segger
RTT?
Thank you

Abderrezak


================================================================

..\zephyr\samples\drivers\soc_flash_nrf5

Output when using the segger RTT:

***** BOOTING ZEPHYR OS v1.11.0 - BUILD: May 29 2018 21:58:25 *****

Nordic nRF5 Flash Testing
=========================

Test 1: Flash erase page at 0x40000
   Flash erase succeeded!

Test 2: Flash write (word array 1)
   Attempted to write 1122 at 0x40000
   Attempted to read 0x40000
   Data read: 1122
   Data read matches data written. Good!
   Attempted to write aabb at 0x40004
   Attempted to read 0x40004
   Data read: aabb
   Data read matches data written. Good!
   Attempted to write abcd at 0x40008
   Attempted to read 0x40008
   Data read: abcd
   Data read matches data written. Good!
   Attempted to write 1234 at 0x4000c
   Attempted to read 0x4000c
   Data read: 1234
   Data read matches data written. Good!

Test 3: Flash erase (4 pages at 0x3e000)
   Flash erase succeeded!

Test 4: Flash write (word array 2)
   Attempted to write 1234 at 0x40000
   Attempted to read 0x40000
   Data read: 1234
   Data read matches data written. Good!
   Attempted to write aabb at 0



flash testing app(soc_flash_nrf5) fails to complete when using segger RTT.

Abderrezak Mekkaoui
 

Hi All,

When running the zephyr supplied flash test sample (..\zephyr\samples\drivers\soc_flash_nrf5), it produces the correct output when using the regular UART console.
But when I switch to the segger RTT it hangs before completing.
I would appreciate If you have any input on why this might be happening. Is there any special precaution one has to observe when using the segger RTT?
Thank you

Abderrezak


================================================================

..\zephyr\samples\drivers\soc_flash_nrf5

Output when using the segger RTT:

***** BOOTING ZEPHYR OS v1.11.0 - BUILD: May 29 2018 21:58:25 *****

Nordic nRF5 Flash Testing
=========================

Test 1: Flash erase page at 0x40000
   Flash erase succeeded!

Test 2: Flash write (word array 1)
   Attempted to write 1122 at 0x40000
   Attempted to read 0x40000
   Data read: 1122
   Data read matches data written. Good!
   Attempted to write aabb at 0x40004
   Attempted to read 0x40004
   Data read: aabb
   Data read matches data written. Good!
   Attempted to write abcd at 0x40008
   Attempted to read 0x40008
   Data read: abcd
   Data read matches data written. Good!
   Attempted to write 1234 at 0x4000c
   Attempted to read 0x4000c
   Data read: 1234
   Data read matches data written. Good!

Test 3: Flash erase (4 pages at 0x3e000)
   Flash erase succeeded!

Test 4: Flash write (word array 2)
   Attempted to write 1234 at 0x40000
   Attempted to read 0x40000
   Data read: 1234
   Data read matches data written. Good!
   Attempted to write aabb at 0


Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception #bluetoothmesh

Carles Cufi
 

This is starting to look more and more like a memory corruption or kernel issue at this point.

I cannot reproduce this easily by running our standard Bluetooth samples, so I am a bit at a loss here. I will try to run a mesh sample to see if it fails in the same way.

 

From: Vikrant More <vikrant8051@...>
Sent: 30 May 2018 13:05
To: Cufi, Carles <carles.cufi@...>
Cc: Von Dentz, Luiz <luiz.von.dentz@...>; Johan Hedberg <johan.hedberg@...>; devel@...; users@...
Subject: Re: [Zephyr-devel] [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hi to all,

 

Suddenly get this non-stoppable FAULT

 

***** BUS FAULT *****
  Executing thread ID (thread): 0x20000220
  Faulting instruction address:  0x1c9a4
  Precise data bus error
  Address: 0xe5f7ffbe
Fatal fault in thread 0x20000220! Aborting.

 

Input -->

 

#/opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e /home/vikrant/projects/zephyr/zephyr/samples/bluetooth/mesh2/build/zephyr/zephyr.elf 0x1c9a4

 

Output -->

 

/home/vikrant/projects/zephyr/zephyr/kernel/include/ksched.h:153

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

Thank You !!

 

 

 

 

 

On Wed, May 30, 2018 at 4:20 PM, vikrant8051 <vikrant8051@...> wrote:

Hi Carles,

 

Now get these FAULT/OOPS,

 

***** MPU FAULT *****

  Executing thread ID (thread): 0x20001eb0
  Faulting instruction address:  0x200006b8
  Instruction Access Violation
Fatal fault in thread 0x20001eb0! Aborting.
***** USAGE FAULT *****
  Executing thread ID (thread): 0x20001eb0
  Faulting instruction address:  0x200006b8
  Illegal load of EXC_RETURN into PC
Fatal fault in thread 0x20001eb0! Aborting.
***** USAGE FAULT *****
  Executing thread ID (thread): 0x20001eb0
  Faulting instruction address:  0x200006b8
  Illegal load of EXC_RETURN into PC
Fatal fault in thread 0x20001eb0! Aborting.
***** Kernel OOPS! *****
Current thread ID = 0x20001eb0
Faulting instruction address = 0x14f10

Fatal fault in ISR! Spinning...

 

 

 

Input -->

 

#/opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e /home/vikrant/projects/zephyr/zephyr/samples/bluetooth/mesh2/build/zephyr/zephyr.elf 0x14f10

 

Output -->

 

/home/vikrant/projects/zephyr/zephyr/subsys/bluetooth/controller/ll_sw/ctrl.c:4702

 

 

Thanks !!

 

 

On Wed, May 30, 2018 at 4:11 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Vikrant,

 

Thanks for looking into this. It seems like we do not get a buffer back from the command tx queue: https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/bluetooth/host/hci_core.c#L3318

 

I have copied Luiz and Johan from Intel in case they know what the cause might be.

 

Regards,

 

Carles

 

From: users@... <users@...> On Behalf Of vikrant8051
Sent: 30 May 2018 12:31


To: Cufi, Carles <carles.cufi@...>
Cc: devel@...; users@...
Subject: Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hi Carles,

 

Input ->

/opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e /home/vikrant/projects/zephyr/zephyr/samples/bluetooth/mesh2/build/zephyr/zephyr.elf 0x5222

 

Output ->

/home/vikrant/projects/zephyr/zephyr/subsys/bluetooth/host/hci_core.c:3318

 

Thank You !!

 

On Wed, May 30, 2018 at 3:51 PM, Cufi, Carles <Carles.Cufi@...> wrote:

If you are using the Zephyr SDK:

 

path-to-zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e zephyr.elf <addr>

 

Carles

 

 

From: Vikrant More <vikrant8051@...>
Sent: 30 May 2018 12:11
To: Cufi, Carles <carles.cufi@...>
Cc: devel@...; users@...
Subject: Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hi Carles,

 

I will but don't know, how to do that ?

 

 

On Wed, May 30, 2018 at 3:19 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Vikrant,

 

Can you please run addr2line with this address present in the error log: 0x5222?

 

Thanks,

 

Carles

 

From: users@... <users@...> On Behalf Of vikrant8051
Sent: 30 May 2018 11:29
To: devel@...; users@...
Subject: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hello World !!

 

Today after upgrading to v1.12.0-rc2, I'm getting following error while playing with sample code which is inspired from sample/bluetooth/mesh

 

 

[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [ERR] event_scan_prepare: assert: '!_radio.ticker_id_prepare' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x1b77e
Fatal fault in ISR! Spinning...

 

-------------------------------------------------------------------------------------------------------------------------

 

Sometime it completely hangs & nothing get displayed on debug terminal

 

-------------------------------------------------------------------------------------------------------------------------

 

Thank You !!

 

 

 

 

 

 

 

 

 


Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception #bluetoothmesh

vikrant8051 <vikrant8051@...>
 

Hi to all,

Suddenly get this non-stoppable FAULT

***** BUS FAULT *****
  Executing thread ID (thread): 0x20000220
  Faulting instruction address:  0x1c9a4
  Precise data bus error
  Address: 0xe5f7ffbe
Fatal fault in thread 0x20000220! Aborting.

Input -->

#/opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e /home/vikrant/projects/zephyr/zephyr/samples/bluetooth/mesh2/build/zephyr/zephyr.elf 0x1c9a4

Output -->

/home/vikrant/projects/zephyr/zephyr/kernel/include/ksched.h:153
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Thank You !!





On Wed, May 30, 2018 at 4:20 PM, vikrant8051 <vikrant8051@...> wrote:
Hi Carles,

Now get these FAULT/OOPS,

***** MPU FAULT *****
  Executing thread ID (thread): 0x20001eb0
  Faulting instruction address:  0x200006b8
  Instruction Access Violation
Fatal fault in thread 0x20001eb0! Aborting.
***** USAGE FAULT *****
  Executing thread ID (thread): 0x20001eb0
  Faulting instruction address:  0x200006b8
  Illegal load of EXC_RETURN into PC
Fatal fault in thread 0x20001eb0! Aborting.
***** USAGE FAULT *****
  Executing thread ID (thread): 0x20001eb0
  Faulting instruction address:  0x200006b8
  Illegal load of EXC_RETURN into PC
Fatal fault in thread 0x20001eb0! Aborting.
***** Kernel OOPS! *****
Current thread ID = 0x20001eb0
Faulting instruction address = 0x14f10
Fatal fault in ISR! Spinning...



Input -->

#/opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e /home/vikrant/projects/zephyr/zephyr/samples/bluetooth/mesh2/build/zephyr/zephyr.elf 0x14f10

Output -->

/home/vikrant/projects/zephyr/zephyr/subsys/bluetooth/controller/ll_sw/ctrl.c:4702


Thanks !!


On Wed, May 30, 2018 at 4:11 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Vikrant,

 

Thanks for looking into this. It seems like we do not get a buffer back from the command tx queue: https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/bluetooth/host/hci_core.c#L3318

 

I have copied Luiz and Johan from Intel in case they know what the cause might be.

 

Regards,

 

Carles

 

From: users@... <users@...> On Behalf Of vikrant8051
Sent: 30 May 2018 12:31


To: Cufi, Carles <carles.cufi@...>
Cc: devel@...; users@...
Subject: Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hi Carles,

 

Input ->

/opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e /home/vikrant/projects/zephyr/zephyr/samples/bluetooth/mesh2/build/zephyr/zephyr.elf 0x5222

 

Output ->

/home/vikrant/projects/zephyr/zephyr/subsys/bluetooth/host/hci_core.c:3318

 

Thank You !!

 

On Wed, May 30, 2018 at 3:51 PM, Cufi, Carles <Carles.Cufi@...> wrote:

If you are using the Zephyr SDK:

 

path-to-zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e zephyr.elf <addr>

 

Carles

 

 

From: Vikrant More <vikrant8051@...>
Sent: 30 May 2018 12:11
To: Cufi, Carles <carles.cufi@...>
Cc: devel@...; users@...
Subject: Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hi Carles,

 

I will but don't know, how to do that ?

 

 

On Wed, May 30, 2018 at 3:19 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Vikrant,

 

Can you please run addr2line with this address present in the error log: 0x5222?

 

Thanks,

 

Carles

 

From: users@... <users@...> On Behalf Of vikrant8051
Sent: 30 May 2018 11:29
To: devel@...; users@...
Subject: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hello World !!

 

Today after upgrading to v1.12.0-rc2, I'm getting following error while playing with sample code which is inspired from sample/bluetooth/mesh

 

 

[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [ERR] event_scan_prepare: assert: '!_radio.ticker_id_prepare' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x1b77e
Fatal fault in ISR! Spinning...

 

-------------------------------------------------------------------------------------------------------------------------

 

Sometime it completely hangs & nothing get displayed on debug terminal

 

-------------------------------------------------------------------------------------------------------------------------

 

Thank You !!

 

 

 

 

 

 

 




Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception #bluetoothmesh

vikrant8051 <vikrant8051@...>
 

Hi Carles,

Now get these FAULT/OOPS,

***** MPU FAULT *****
  Executing thread ID (thread): 0x20001eb0
  Faulting instruction address:  0x200006b8
  Instruction Access Violation
Fatal fault in thread 0x20001eb0! Aborting.
***** USAGE FAULT *****
  Executing thread ID (thread): 0x20001eb0
  Faulting instruction address:  0x200006b8
  Illegal load of EXC_RETURN into PC
Fatal fault in thread 0x20001eb0! Aborting.
***** USAGE FAULT *****
  Executing thread ID (thread): 0x20001eb0
  Faulting instruction address:  0x200006b8
  Illegal load of EXC_RETURN into PC
Fatal fault in thread 0x20001eb0! Aborting.
***** Kernel OOPS! *****
Current thread ID = 0x20001eb0
Faulting instruction address = 0x14f10
Fatal fault in ISR! Spinning...



Input -->

#/opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e /home/vikrant/projects/zephyr/zephyr/samples/bluetooth/mesh2/build/zephyr/zephyr.elf 0x14f10

Output -->

/home/vikrant/projects/zephyr/zephyr/subsys/bluetooth/controller/ll_sw/ctrl.c:4702


Thanks !!


On Wed, May 30, 2018 at 4:11 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Vikrant,

 

Thanks for looking into this. It seems like we do not get a buffer back from the command tx queue: https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/bluetooth/host/hci_core.c#L3318

 

I have copied Luiz and Johan from Intel in case they know what the cause might be.

 

Regards,

 

Carles

 

From: users@... <users@...> On Behalf Of vikrant8051
Sent: 30 May 2018 12:31


To: Cufi, Carles <carles.cufi@...>
Cc: devel@...; users@...
Subject: Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hi Carles,

 

Input ->

/opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e /home/vikrant/projects/zephyr/zephyr/samples/bluetooth/mesh2/build/zephyr/zephyr.elf 0x5222

 

Output ->

/home/vikrant/projects/zephyr/zephyr/subsys/bluetooth/host/hci_core.c:3318

 

Thank You !!

 

On Wed, May 30, 2018 at 3:51 PM, Cufi, Carles <Carles.Cufi@...> wrote:

If you are using the Zephyr SDK:

 

path-to-zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e zephyr.elf <addr>

 

Carles

 

 

From: Vikrant More <vikrant8051@...>
Sent: 30 May 2018 12:11
To: Cufi, Carles <carles.cufi@...>
Cc: devel@...; users@...
Subject: Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hi Carles,

 

I will but don't know, how to do that ?

 

 

On Wed, May 30, 2018 at 3:19 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Vikrant,

 

Can you please run addr2line with this address present in the error log: 0x5222?

 

Thanks,

 

Carles

 

From: users@... <users@...> On Behalf Of vikrant8051
Sent: 30 May 2018 11:29
To: devel@...; users@...
Subject: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hello World !!

 

Today after upgrading to v1.12.0-rc2, I'm getting following error while playing with sample code which is inspired from sample/bluetooth/mesh

 

 

[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [ERR] event_scan_prepare: assert: '!_radio.ticker_id_prepare' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x1b77e
Fatal fault in ISR! Spinning...

 

-------------------------------------------------------------------------------------------------------------------------

 

Sometime it completely hangs & nothing get displayed on debug terminal

 

-------------------------------------------------------------------------------------------------------------------------

 

Thank You !!

 

 

 

 

 

 

 



Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception #bluetoothmesh

Carles Cufi
 

Hi Vikrant,

 

Thanks for looking into this. It seems like we do not get a buffer back from the command tx queue: https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/bluetooth/host/hci_core.c#L3318

 

I have copied Luiz and Johan from Intel in case they know what the cause might be.

 

Regards,

 

Carles

 

From: users@... <users@...> On Behalf Of vikrant8051
Sent: 30 May 2018 12:31
To: Cufi, Carles <carles.cufi@...>
Cc: devel@...; users@...
Subject: Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hi Carles,

 

Input ->

/opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e /home/vikrant/projects/zephyr/zephyr/samples/bluetooth/mesh2/build/zephyr/zephyr.elf 0x5222

 

Output ->

/home/vikrant/projects/zephyr/zephyr/subsys/bluetooth/host/hci_core.c:3318

 

Thank You !!

 

On Wed, May 30, 2018 at 3:51 PM, Cufi, Carles <Carles.Cufi@...> wrote:

If you are using the Zephyr SDK:

 

path-to-zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e zephyr.elf <addr>

 

Carles

 

 

From: Vikrant More <vikrant8051@...>
Sent: 30 May 2018 12:11
To: Cufi, Carles <carles.cufi@...>
Cc: devel@...; users@...
Subject: Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hi Carles,

 

I will but don't know, how to do that ?

 

 

On Wed, May 30, 2018 at 3:19 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Vikrant,

 

Can you please run addr2line with this address present in the error log: 0x5222?

 

Thanks,

 

Carles

 

From: users@... <users@...> On Behalf Of vikrant8051
Sent: 30 May 2018 11:29
To: devel@...; users@...
Subject: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hello World !!

 

Today after upgrading to v1.12.0-rc2, I'm getting following error while playing with sample code which is inspired from sample/bluetooth/mesh

 

 

[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [ERR] event_scan_prepare: assert: '!_radio.ticker_id_prepare' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x1b77e
Fatal fault in ISR! Spinning...

 

-------------------------------------------------------------------------------------------------------------------------

 

Sometime it completely hangs & nothing get displayed on debug terminal

 

-------------------------------------------------------------------------------------------------------------------------

 

Thank You !!

 

 

 

 

 

 

 


Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception #bluetoothmesh

vikrant8051 <vikrant8051@...>
 

Hi Carles,

Input ->
/opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e /home/vikrant/projects/zephyr/zephyr/samples/bluetooth/mesh2/build/zephyr/zephyr.elf 0x5222

Output ->
/home/vikrant/projects/zephyr/zephyr/subsys/bluetooth/host/hci_core.c:3318

Thank You !!

On Wed, May 30, 2018 at 3:51 PM, Cufi, Carles <Carles.Cufi@...> wrote:

If you are using the Zephyr SDK:

 

path-to-zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e zephyr.elf <addr>

 

Carles

 

 

From: Vikrant More <vikrant8051@...>
Sent: 30 May 2018 12:11
To: Cufi, Carles <carles.cufi@...>
Cc: devel@...; users@...
Subject: Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hi Carles,

 

I will but don't know, how to do that ?

 

 

On Wed, May 30, 2018 at 3:19 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Vikrant,

 

Can you please run addr2line with this address present in the error log: 0x5222?

 

Thanks,

 

Carles

 

From: users@... <users@...> On Behalf Of vikrant8051
Sent: 30 May 2018 11:29
To: devel@...; users@...
Subject: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hello World !!

 

Today after upgrading to v1.12.0-rc2, I'm getting following error while playing with sample code which is inspired from sample/bluetooth/mesh

 

 

[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [ERR] event_scan_prepare: assert: '!_radio.ticker_id_prepare' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x1b77e
Fatal fault in ISR! Spinning...

 

-------------------------------------------------------------------------------------------------------------------------

 

Sometime it completely hangs & nothing get displayed on debug terminal

 

-------------------------------------------------------------------------------------------------------------------------

 

Thank You !!

 

 

 

 

 

 



Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception #bluetoothmesh

Carles Cufi
 

If you are using the Zephyr SDK:

 

path-to-zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-addr2line -e zephyr.elf <addr>

 

Carles

 

 

From: Vikrant More <vikrant8051@...>
Sent: 30 May 2018 12:11
To: Cufi, Carles <carles.cufi@...>
Cc: devel@...; users@...
Subject: Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hi Carles,

 

I will but don't know, how to do that ?

 

 

On Wed, May 30, 2018 at 3:19 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Vikrant,

 

Can you please run addr2line with this address present in the error log: 0x5222?

 

Thanks,

 

Carles

 

From: users@... <users@...> On Behalf Of vikrant8051
Sent: 30 May 2018 11:29
To: devel@...; users@...
Subject: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hello World !!

 

Today after upgrading to v1.12.0-rc2, I'm getting following error while playing with sample code which is inspired from sample/bluetooth/mesh

 

 

[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [ERR] event_scan_prepare: assert: '!_radio.ticker_id_prepare' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x1b77e
Fatal fault in ISR! Spinning...

 

-------------------------------------------------------------------------------------------------------------------------

 

Sometime it completely hangs & nothing get displayed on debug terminal

 

-------------------------------------------------------------------------------------------------------------------------

 

Thank You !!

 

 

 

 

 

 


Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception #bluetoothmesh

vikrant8051 <vikrant8051@...>
 

Hi Carles,

I will but don't know, how to do that ?


On Wed, May 30, 2018 at 3:19 PM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi Vikrant,

 

Can you please run addr2line with this address present in the error log: 0x5222?

 

Thanks,

 

Carles

 

From: users@... <users@...> On Behalf Of vikrant8051
Sent: 30 May 2018 11:29
To: devel@...; users@...
Subject: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hello World !!

 

Today after upgrading to v1.12.0-rc2, I'm getting following error while playing with sample code which is inspired from sample/bluetooth/mesh

 

 

[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [ERR] event_scan_prepare: assert: '!_radio.ticker_id_prepare' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x1b77e
Fatal fault in ISR! Spinning...

 

-------------------------------------------------------------------------------------------------------------------------

 

Sometime it completely hangs & nothing get displayed on debug terminal

 

-------------------------------------------------------------------------------------------------------------------------

 

Thank You !!

 

 

 

 

 



Re: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception #bluetoothmesh

Carles Cufi
 

Hi Vikrant,

 

Can you please run addr2line with this address present in the error log: 0x5222?

 

Thanks,

 

Carles

 

From: users@... <users@...> On Behalf Of vikrant8051
Sent: 30 May 2018 11:29
To: devel@...; users@...
Subject: [Zephyr-users] #BluetoothMesh ...about latest kernel OOPS & exception

 

Hello World !!

 

Today after upgrading to v1.12.0-rc2, I'm getting following error while playing with sample code which is inspired from sample/bluetooth/mesh

 

 

[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [ERR] event_scan_prepare: assert: '!_radio.ticker_id_prepare' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x1b77e
Fatal fault in ISR! Spinning...

 

-------------------------------------------------------------------------------------------------------------------------

 

Sometime it completely hangs & nothing get displayed on debug terminal

 

-------------------------------------------------------------------------------------------------------------------------

 

Thank You !!

 

 

 

 

 


#BluetoothMesh ...about latest kernel OOPS & exception #bluetoothmesh

vikrant8051 <vikrant8051@...>
 

Hello World !!

Today after upgrading to v1.12.0-rc2, I'm getting following error while playing with sample code which is inspired from sample/bluetooth/mesh


[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [WRN] process_events: Unexpected k_poll event state 7
[bt] [WRN] process_events: Unexpected k_poll event state 8
[bt] [ERR] hci_tx_thread: assert: 'err == 0' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x5222
Fatal fault in thread 0x20000484! Aborting.
[bt] [ERR] event_scan_prepare: assert: '!_radio.ticker_id_prepare' failed
***** Kernel OOPS! *****
Current thread ID = 0x20000484
Faulting instruction address = 0x1b77e
Fatal fault in ISR! Spinning...

-------------------------------------------------------------------------------------------------------------------------

Sometime it completely hangs & nothing get displayed on debug terminal

-------------------------------------------------------------------------------------------------------------------------

Thank You !!






Re: How to support multiple defconfigs to be merged?

Sebastian Boe
 

CONF_FILE is a space-separated list instead of the normal CMake semicolon-separated list.

So doing

set(CONF_FILE "defconfig_1 defconfig_2 defconfig_3")

is expected to work without any upstream modifications.

I can't remember the reason it was decided to be space-separated.

It could have been to support the user specifying

cmake -DCONF_FILE="a b c"

instead of

cmake -DCONF_FILE="a;b;c"

________________________________________
From: devel@... <devel@...> on behalf of Li, Jun R <jun.r.li@...>
Sent: Wednesday, 30 May 2018 1:24:31 AM
To: Rosen, Michael R; devel@...
Subject: Re: [Zephyr-devel] How to support multiple defconfigs to be merged?

Thank you, Mike! Yeah, it is better to have a PR in Zephyr to support this.

Regards,
Jun


From: <devel@...> on behalf of Michael Rosen <michael.r.rosen@...>
Date: Tuesday, May 29, 2018 at 16:12
To: Jun Li <jun.r.li@...>, "devel@..." <devel@...>
Subject: Re: [Zephyr-devel] How to support multiple defconfigs to be merged?

Jun,

As we discussed, you can use the following to do what you have below in the new cmake system:

set(CONF_FILE “defconfig_1”)
list(APPEND CONF_FILE “defconfig_2”)
list(APPEND CONF_FILE “defconfig_3”)

However, you need to update cmake/kconfig.cmake:13 to be:

string(REPLACE " " ";" CONF_FILE_AS_LIST "${CONF_FILE}")

ie, add quotes to CONF_FILE. Unless the Zephyr team has another suggestion for how to achieve multiple defconfig files; it might be good to add these quotes to the actual release (I can make a pull request if this is the suggestions approach)

Mike

From: devel@... [mailto:devel@...] On Behalf Of Li, Jun R
Sent: Tuesday, May 29, 2018 2:22 PM
To: devel@...
Subject: [Zephyr-devel] How to support multiple defconfigs to be merged?

Hi everyone,

Before Zephyr adopted cmake as the building tool, it supported to merge multiple defconfig files in project’s makefile by the following way:

CONF_FILE = defconfig_1
CONF_FILE += defconfig_2
CONF_FILE += defconfig_3

The three “defconfig_x” files will be merged together when being built.

However, in the current version with CMake, only one defconfig is acceptable by the following way in the project’s CMakeLists.txt:

set(CONF_FILE defconfig_1)

Other “set” operations on “CONF_FILE” will make previous ones to be ignored, meaning only the last “set(CONF_FILE defconfig_x)” works.

So, is there still a way to merge multiple defconfigs by using CMake?

Thank you!

Jun Li


Zephyr 1.12.0-rc2 tagged

Maureen Helm
 

Hi all,

 

We have just tagged Zephyr 1.12.0-rc2.

 

The merge window for new features has been closed since rc1, and we will continue to merge only bug fixes and documentation until the release is finalized. As a reminder, we must have zero open high priority bugs and less than 20 open medium priority bugs before we can release. Please review any open bugs that have been assigned to you.

https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aopen+is%3Aissue+label%3Abug+label%3A%22priority%3A+high%22

https://github.com/zephyrproject-rtos/zephyr/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3Abug+label%3A%22priority%3A+medium%22+-milestone%3Av1.13.0

 

The full release log can be found here:

https://github.com/zephyrproject-rtos/zephyr/releases/tag/v1.12.0-rc2

 

Thanks to everybody who contributed to this release!

 

Maureen


Re: How to support multiple defconfigs to be merged?

Li, Jun R
 

Thank you, Mike! Yeah, it is better to have a PR in Zephyr to support this.

 

Regards,

Jun

 

 

From: <devel@...> on behalf of Michael Rosen <michael.r.rosen@...>
Date: Tuesday, May 29, 2018 at 16:12
To: Jun Li <jun.r.li@...>, "devel@..." <devel@...>
Subject: Re: [Zephyr-devel] How to support multiple defconfigs to be merged?

 

Jun,

 

As we discussed, you can use the following to do what you have below in the new cmake system:

 

set(CONF_FILE “defconfig_1”)

list(APPEND CONF_FILE “defconfig_2”)

list(APPEND CONF_FILE “defconfig_3”)

 

However, you need to update cmake/kconfig.cmake:13 to be:

 

string(REPLACE " " ";" CONF_FILE_AS_LIST "${CONF_FILE}")

 

ie, add quotes to CONF_FILE. Unless the Zephyr team has another suggestion for how to achieve multiple defconfig files; it might be good to add these quotes to the actual release (I can make a pull request if this is the suggestions approach)

 

Mike

 

From: devel@... [mailto:devel@...] On Behalf Of Li, Jun R
Sent: Tuesday, May 29, 2018 2:22 PM
To: devel@...
Subject: [Zephyr-devel] How to support multiple defconfigs to be merged?

 

Hi everyone,

 

Before Zephyr adopted cmake as the building tool, it supported to merge multiple defconfig files in project’s makefile by the following way:

 

CONF_FILE = defconfig_1

CONF_FILE += defconfig_2

CONF_FILE += defconfig_3

 

The three “defconfig_x” files will be merged together when being built.

 

However, in the current version with CMake, only one defconfig is acceptable by the following way in the project’s CMakeLists.txt:

 

set(CONF_FILE defconfig_1)

 

Other “set” operations on “CONF_FILE” will make previous ones to be ignored, meaning only the last “set(CONF_FILE defconfig_x)” works.

 

So, is there still a way to merge multiple defconfigs by using CMake?

 

Thank you!

 

Jun Li

 

 


Re: How to support multiple defconfigs to be merged?

Michael Rosen
 

Jun,

 

As we discussed, you can use the following to do what you have below in the new cmake system:

 

set(CONF_FILE “defconfig_1”)

list(APPEND CONF_FILE “defconfig_2”)

list(APPEND CONF_FILE “defconfig_3”)

 

However, you need to update cmake/kconfig.cmake:13 to be:

 

string(REPLACE " " ";" CONF_FILE_AS_LIST "${CONF_FILE}")

 

ie, add quotes to CONF_FILE. Unless the Zephyr team has another suggestion for how to achieve multiple defconfig files; it might be good to add these quotes to the actual release (I can make a pull request if this is the suggestions approach)

 

Mike

 

From: devel@... [mailto:devel@...] On Behalf Of Li, Jun R
Sent: Tuesday, May 29, 2018 2:22 PM
To: devel@...
Subject: [Zephyr-devel] How to support multiple defconfigs to be merged?

 

Hi everyone,

 

Before Zephyr adopted cmake as the building tool, it supported to merge multiple defconfig files in project’s makefile by the following way:

 

CONF_FILE = defconfig_1

CONF_FILE += defconfig_2

CONF_FILE += defconfig_3

 

The three “defconfig_x” files will be merged together when being built.

 

However, in the current version with CMake, only one defconfig is acceptable by the following way in the project’s CMakeLists.txt:

 

set(CONF_FILE defconfig_1)

 

Other “set” operations on “CONF_FILE” will make previous ones to be ignored, meaning only the last “set(CONF_FILE defconfig_x)” works.

 

So, is there still a way to merge multiple defconfigs by using CMake?

 

Thank you!

 

Jun Li

 

 


How to support multiple defconfigs to be merged?

Li, Jun R
 

Hi everyone,

 

Before Zephyr adopted cmake as the building tool, it supported to merge multiple defconfig files in project’s makefile by the following way:

 

CONF_FILE = defconfig_1

CONF_FILE += defconfig_2

CONF_FILE += defconfig_3

 

The three “defconfig_x” files will be merged together when being built.

 

However, in the current version with CMake, only one defconfig is acceptable by the following way in the project’s CMakeLists.txt:

 

set(CONF_FILE defconfig_1)

 

Other “set” operations on “CONF_FILE” will make previous ones to be ignored, meaning only the last “set(CONF_FILE defconfig_x)” works.

 

So, is there still a way to merge multiple defconfigs by using CMake?

 

Thank you!

 

Jun Li

 

 


POSIX clock_gettime() has meaningless 'tv_nsec' field.

David Brown
 

I’ve created Issue 8009 to track this.

 

The current implementation of clock_gettime() attempts to use the k_cycle_get_32() counter to provide a more accurate notion of time (filling in the tv_nsec field). Unfortunately, on targets where the cycle counter is not a power-of-two division of seconds, after the first time the counter wraps, the resulting value becomes meaningless.

 

For example, on the frdm-k64f, after 35 seconds, the time will appear to jump backwards a bit (when the counter wraps), and then once a second, the time will jump backward a bit, because the cycle counter is out of phase with seconds. Every roughly 35 seconds, the jump in the time will shift. The clock will shift around in the sub-second value, only returning to the correct offset for a 35 second period about every 94 days.

 

The reason for this email, though, is to try and determine what the best way of fixing this is. I see two ways to fix it:

 

  1. Don’t use k_cycle_get_32(), and just use the ms accuracy of the system timer. This is an easier solution, and having ms accuracy of the sub-second field is certainly more useful than having a meaningless number.
  2. Implement a 64-bit counter to detect wrap around of the cycle counter. One way to do this would be to check the cycle counter on each clock interrupt, and when it has wrapped, increment an upper 32-bit value counter.

 

Any thoughts on what would be the best way to fix this?

 

Thanks,

David


[Bluetooth pairing] psskey_confirm callback is not executing even after successful pairing

vikrant8051 <vikrant8051@...>
 

Hi,

static void auth_passkey_confirm(struct bt_conn *conn, unsigned int passkey)
{
    printk("\n\rauth_passkey_confirm !!\n\r");
}

static struct bt_conn_auth_cb auth_cb_display = {
    .passkey_display = auth_passkey_display,
    .passkey_entry = NULL,
    .cancel = auth_cancel,
    .passkey_confirm = auth_passkey_confirm,
};

I've edited samples/bluetooth/peripheral  as shown above.
But auth_passkey_confirm is not executing even after successful pairing.

Am I missing something ?

Thank You !!

4001 - 4020 of 8640