Date   

Now: Zephyr: Toolchain Working Group - 07/26/2021 #cal-notice

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

Zephyr: Toolchain Working Group

When:
07/26/2021
3:00pm to 4:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

Organizer: Torsten Rasmussen

Description:

________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 682 738 030#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 


Event: Zephyr: Toolchain Working Group - 07/26/2021 #cal-reminder

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

Reminder: Zephyr: Toolchain Working Group

When:
07/26/2021
3:00pm to 4:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

Organizer: Torsten Rasmussen

An RSVP is requested. Click here to RSVP

Description:

________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 682 738 030#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 


Re: Zephyr RTOS

lairdjm
 

From: devel@... <devel@...> On Behalf Of Rakshali Jain via lists.zephyrproject.org
Sent: 26 July 2021 15:37
To: devel@...
Subject: [Zephyr-devel] Zephyr RTOS

 

Hey, I am trying to install Zephyr OS on raspberry pi 4 since long time I referred your blog but then also I was unable to do so. Please guide me on it.


Zephyr RTOS

Rakshali Jain <rakshalijain1010@...>
 

Hey, I am trying to install Zephyr OS on raspberry pi 4 since long time I referred your blog but then also I was unable to do so. Please guide me on it.


Bug-Bashing Week :beetle: (Aug 1-7)

Christopher Friedt
 

Hi Devs!

As noted in the Review and TSC meetings, we will have a feature pause
for the 1st week of August (August 1st through 7th) where only bug fix
PR's will be merged, although the official mailing list announcement
might still be on the way. The goal is to mitigate as many bugs as
possible prior to the 2.7.0 LTS release.Currently, there are:

4 High Priority bugs
27 medium priority bugs
103 low priority bugs

Incentives
As usual, PR's are welcome However, we would also like to incentivize
contributors to squash as many bugs as possible. The incentives will
likely be in the following form for top "Pest Control" experts:

Honourable mention in a list of "Top-Ten Exterminators"
Possibly some kind of GitHub badge, if such a thing exists
Other items such as dev boards or swag (TBD)

The list of bugs slated for extermination before the 2.7.0 LTS release is below
https://stats.zephyrproject.org/testing/d/K57-gHUGk/bug-tracking-experimental

Let's try to clean up as many as we can! Remember, it's not a serious
competition - everyone wins, and the point is really just having fun
taking part

Looking forward to it,

Chris Friedt
v2.7.0 Release Manager


Problem when compiling in Seeger Embedded studio

Omar Morceli
 

Hi 
I made some changes in the chat project that is found in NRF Connect SDK
and when I build the change project this error occurs


kobj-types-enum.h: No such file or directory
Build failed

 

this is the full building output:
Building ‘C:/Users/OMAR/ncs/v1.5.1/zephyr/misc/empty_file.c’ from solution ‘build’ in configuration ‘Common’
Building ‘C:/Users/OMAR/ncs/v1.5.1/zephyr/include/dt-bindings/gpio/gpio.h’ from solution ‘build’ in configuration ‘Common’
Building ‘C:/Users/OMAR/ncs/v1.5.1/zephyr/include/dt-bindings/i2c/i2c.h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/misc/generated/syscalls.json’ from solution ‘build’ in configuration ‘Common’
  Combining ‘zephyr/misc/generated/syscalls.json’
Building ‘zephyr/misc/generated/struct_tags.json’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/CMakeFiles/parse_syscalls_target’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/parse_syscalls_target’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/driver-validation.h’ from solution ‘build’ in configuration ‘Common’
  Combining ‘zephyr/include/generated/driver-validation.h’
Building ‘zephyr/CMakeFiles/driver_validation_h_target’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/driver_validation_h_target’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/kobj-types-enum.h’ from solution ‘build’ in configuration ‘Common’
  Combining ‘zephyr/include/generated/kobj-types-enum.h’
Building ‘zephyr/include/generated/otype-to-str.h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/CMakeFiles/kobj_types_h_target’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/kobj_types_h_target’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/syscall_list.h’ from solution ‘build’ in configuration ‘Common’
  Combining ‘zephyr/include/generated/syscall_list.h’
Building ‘zephyr/CMakeFiles/syscall_list_h_target’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/syscall_dispatch.c’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/syscall_list_h_target’ from solution ‘build’ in configuration ‘Common’
Building ‘cmake_object_order_depends_target_offsets’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj’ from solution ‘build’ in configuration ‘Common’
  Compiling ‘offsets.c’
    kernel_includes.h
    kernel.h
    offsets_aarch32.c
    offsets.c
    kobj-types-enum.h: No such file or directory
Build failed



thanks


Event: Zephyr Dev environment kickoff meeting - Friday, July 30, 2021 #cal-invite

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

Zephyr Dev environment kickoff meeting

When:
Friday, July 30, 2021
2:00pm to 3:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

Organizer: tsc@...

An RSVP is requested. Click here to RSVP

Description:

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


Re: Issue when log2, printk and assert together

Srinivasan Tamilarasan
 

Hi Krzysztof,

Ok. Thank you for the support.

 

Regards,

Srinivasan

 

From: devel@... <devel@...> On Behalf Of Chruscinski, Krzysztof
Sent: 23 July 2021 01:07 PM
To: Srinivasan Tamilarasan <Srinivasan.Tamilarasan@...>; devel@...
Subject: [Zephyr-devel] ODP: Issue when log2, printk and assert together

 

[External Email]: This email arrived from an external source - Please exercise caution when opening any attachments or clicking on links.

Hi,

 

this will not go away, it's a standard warning generated by cmake to notify user that ASSERTs are enabled since they bump footprint significantly and may not be welcomed for release build.

 

regards,

Krzysztof


Od: Srinivasan Tamilarasan <Srinivasan.Tamilarasan@...>
Wysłane: piątek, 23 lipca 2021 09:15
Do: Chruściński, Krzysztof <Krzysztof.Chruscinski@...>; devel@... <devel@...>
Temat: RE: Issue when log2, printk and assert together

 

Hi Krzysztof,

The build error is due to our internal logic. Now the build error got resolved and working fine.

 

But the warning “__ASSERT() statements are globally ENABLED” I am getting always.

 

How to resolve this warning?

 

Thank you for your support.

 

Regards,

Srinivasan

 

From: Chruściński, Krzysztof <Krzysztof.Chruscinski@...>
Sent: 23 July 2021 11:56 AM
To: Srinivasan Tamilarasan <Srinivasan.Tamilarasan@...>; devel@...
Subject: ODP: Issue when log2, printk and assert together

 

[External Email]: This email arrived from an external source - Please exercise caution when opening any attachments or clicking on links.

Hi,

 

just tried it in hello_world and it compiles fine with configuration you've provided. Can you make sure that CBPRINTF_STATIC_PACKAGE_CHECK_ALIGNMENT is not set (it should be disabled by CONFIG_LOG_PRINTK).

 

regards,

Krzysztof


Od: Srinivasan Tamilarasan <Srinivasan.Tamilarasan@...>
Wysłane: piątek, 23 lipca 2021 08:16
Do: Chruściński, Krzysztof <Krzysztof.Chruscinski@...>; devel@... <devel@...>
Temat: RE: Issue when log2, printk and assert together

 

Hi,

I have cherry picked below 2 commits to zephyr2.6 branch and build it.

 

Then I have included the macros CONFIG_LOG=y , CONFIG_LOG2_MODE_DEFERRED=y, CONFIG_LOG_PRINTK=y and CONFIG_ASSERT=y. Then the build error got resolved and got below warning,

__ASSERT() statements are globally ENABLED

 

 

After that I have added below statement in my application,

__ASSERT(0, "ERRROR:Line:%d,File:%s\n", line, file);

 

Then again I am getting build error same like before the fix.

 

Is this issue completely resolved in the rtos? If it is any other commits do I need to take to resolve this issue?

 

Regards,

Srinivasan

 

From: Srinivasan Tamilarasan
Sent: 21 July 2021 06:07 PM
To: 'Chruściński, Krzysztof' <Krzysztof.Chruscinski@...>; devel@...
Subject: RE: Issue when log2, printk and assert together

 

Hi,

Good. It is got fixed now.

 

Thank you for the response.

 

Regards,

Srinivasan

 

From: Chruściński, Krzysztof <Krzysztof.Chruscinski@...>
Sent: 21 July 2021 05:56 PM
To: devel@...; Srinivasan Tamilarasan <Srinivasan.Tamilarasan@...>
Subject: ODP: Issue when log2, printk and assert together

 

[External Email]: This email arrived from an external source - Please exercise caution when opening any attachments or clicking on links.

Hi,

 

good timing. Fix for that has been merged 40 minutes ago: https://github.com/zephyrproject-rtos/zephyr/pull/36883

When printk is redirected to logging (CONFIG_LOG_PRINTK) then printk.h includes log_msg2.h which includes cbprintf_internal.h which includes __assert.h which includes printk.h. Fixing it by adding compile time switches for including and using asserts in cbprintf and forcing to not use them when LOG_PRINTK is set. Fixes #36486.

github.com

 

 

regards,

Krzysztof


Od: devel@... <devel@...> w imieniu użytkownika Srinivasan Tamilarasan via lists.zephyrproject.org <srinivasan.tamilarasan=onsemi.com@...>
Wysłane: środa, 21 lipca 2021 14:23
Do: devel@... <devel@...>
Temat: [Zephyr-devel] Issue when log2, printk and assert together

 

Hi all,

When enable CONFIG_LOG2_MODE_DEFERRED=y, CONFIG_LOG_PRINTK=y and CONFIG_ASSERT=y flag. I am getting the build error even there is no log/assert messages are used.

 

PFA of cmake error log.

 

But when I change to old method CONFIG_LOG_MODE_DEFERRED=y then there is no build error.

 

Can anyone help me to resolve this error?

 

Idea is I need to use both assert and log together in the same project and printk messages needs to route via logging subsystem.

 

Regards,

Srinivasan


ODP: Issue when log2, printk and assert together

Chruściński, Krzysztof
 

Hi,

this will not go away, it's a standard warning generated by cmake to notify user that ASSERTs are enabled since they bump footprint significantly and may not be welcomed for release build.

regards,
Krzysztof

Od: Srinivasan Tamilarasan <Srinivasan.Tamilarasan@...>
Wysłane: piątek, 23 lipca 2021 09:15
Do: Chruściński, Krzysztof <Krzysztof.Chruscinski@...>; devel@... <devel@...>
Temat: RE: Issue when log2, printk and assert together
 

Hi Krzysztof,

The build error is due to our internal logic. Now the build error got resolved and working fine.

 

But the warning “__ASSERT() statements are globally ENABLED” I am getting always.

 

How to resolve this warning?

 

Thank you for your support.

 

Regards,

Srinivasan

 

From: Chruściński, Krzysztof <Krzysztof.Chruscinski@...>
Sent: 23 July 2021 11:56 AM
To: Srinivasan Tamilarasan <Srinivasan.Tamilarasan@...>; devel@...
Subject: ODP: Issue when log2, printk and assert together

 

[External Email]: This email arrived from an external source - Please exercise caution when opening any attachments or clicking on links.

Hi,

 

just tried it in hello_world and it compiles fine with configuration you've provided. Can you make sure that CBPRINTF_STATIC_PACKAGE_CHECK_ALIGNMENT is not set (it should be disabled by CONFIG_LOG_PRINTK).

 

regards,

Krzysztof


Od: Srinivasan Tamilarasan <Srinivasan.Tamilarasan@...>
Wysłane: piątek, 23 lipca 2021 08:16
Do: Chruściński, Krzysztof <Krzysztof.Chruscinski@...>; devel@... <devel@...>
Temat: RE: Issue when log2, printk and assert together

 

Hi,

I have cherry picked below 2 commits to zephyr2.6 branch and build it.

 

Then I have included the macros CONFIG_LOG=y , CONFIG_LOG2_MODE_DEFERRED=y, CONFIG_LOG_PRINTK=y and CONFIG_ASSERT=y. Then the build error got resolved and got below warning,

__ASSERT() statements are globally ENABLED

 

 

After that I have added below statement in my application,

__ASSERT(0, "ERRROR:Line:%d,File:%s\n", line, file);

 

Then again I am getting build error same like before the fix.

 

Is this issue completely resolved in the rtos? If it is any other commits do I need to take to resolve this issue?

 

Regards,

Srinivasan

 

From: Srinivasan Tamilarasan
Sent: 21 July 2021 06:07 PM
To: 'Chruściński, Krzysztof' <Krzysztof.Chruscinski@...>; devel@...
Subject: RE: Issue when log2, printk and assert together

 

Hi,

Good. It is got fixed now.

 

Thank you for the response.

 

Regards,

Srinivasan

 

From: Chruściński, Krzysztof <Krzysztof.Chruscinski@...>
Sent: 21 July 2021 05:56 PM
To: devel@...; Srinivasan Tamilarasan <Srinivasan.Tamilarasan@...>
Subject: ODP: Issue when log2, printk and assert together

 

[External Email]: This email arrived from an external source - Please exercise caution when opening any attachments or clicking on links.

Hi,

 

good timing. Fix for that has been merged 40 minutes ago: https://github.com/zephyrproject-rtos/zephyr/pull/36883

When printk is redirected to logging (CONFIG_LOG_PRINTK) then printk.h includes log_msg2.h which includes cbprintf_internal.h which includes __assert.h which includes printk.h. Fixing it by adding compile time switches for including and using asserts in cbprintf and forcing to not use them when LOG_PRINTK is set. Fixes #36486.

github.com

 

 

regards,

Krzysztof


Od: devel@... <devel@...> w imieniu użytkownika Srinivasan Tamilarasan via lists.zephyrproject.org <srinivasan.tamilarasan=onsemi.com@...>
Wysłane: środa, 21 lipca 2021 14:23
Do: devel@... <devel@...>
Temat: [Zephyr-devel] Issue when log2, printk and assert together

 

Hi all,

When enable CONFIG_LOG2_MODE_DEFERRED=y, CONFIG_LOG_PRINTK=y and CONFIG_ASSERT=y flag. I am getting the build error even there is no log/assert messages are used.

 

PFA of cmake error log.

 

But when I change to old method CONFIG_LOG_MODE_DEFERRED=y then there is no build error.

 

Can anyone help me to resolve this error?

 

Idea is I need to use both assert and log together in the same project and printk messages needs to route via logging subsystem.

 

Regards,

Srinivasan


Re: Issue when log2, printk and assert together

Srinivasan Tamilarasan
 

Hi Krzysztof,

The build error is due to our internal logic. Now the build error got resolved and working fine.

 

But the warning “__ASSERT() statements are globally ENABLED” I am getting always.

 

How to resolve this warning?

 

Thank you for your support.

 

Regards,

Srinivasan

 

From: Chruściński, Krzysztof <Krzysztof.Chruscinski@...>
Sent: 23 July 2021 11:56 AM
To: Srinivasan Tamilarasan <Srinivasan.Tamilarasan@...>; devel@...
Subject: ODP: Issue when log2, printk and assert together

 

[External Email]: This email arrived from an external source - Please exercise caution when opening any attachments or clicking on links.

Hi,

 

just tried it in hello_world and it compiles fine with configuration you've provided. Can you make sure that CBPRINTF_STATIC_PACKAGE_CHECK_ALIGNMENT is not set (it should be disabled by CONFIG_LOG_PRINTK).

 

regards,

Krzysztof


Od: Srinivasan Tamilarasan <Srinivasan.Tamilarasan@...>
Wysłane: piątek, 23 lipca 2021 08:16
Do: Chruściński, Krzysztof <Krzysztof.Chruscinski@...>; devel@... <devel@...>
Temat: RE: Issue when log2, printk and assert together

 

Hi,

I have cherry picked below 2 commits to zephyr2.6 branch and build it.

 

Then I have included the macros CONFIG_LOG=y , CONFIG_LOG2_MODE_DEFERRED=y, CONFIG_LOG_PRINTK=y and CONFIG_ASSERT=y. Then the build error got resolved and got below warning,

__ASSERT() statements are globally ENABLED

 

 

After that I have added below statement in my application,

__ASSERT(0, "ERRROR:Line:%d,File:%s\n", line, file);

 

Then again I am getting build error same like before the fix.

 

Is this issue completely resolved in the rtos? If it is any other commits do I need to take to resolve this issue?

 

Regards,

Srinivasan

 

From: Srinivasan Tamilarasan
Sent: 21 July 2021 06:07 PM
To: 'Chruściński, Krzysztof' <Krzysztof.Chruscinski@...>; devel@...
Subject: RE: Issue when log2, printk and assert together

 

Hi,

Good. It is got fixed now.

 

Thank you for the response.

 

Regards,

Srinivasan

 

From: Chruściński, Krzysztof <Krzysztof.Chruscinski@...>
Sent: 21 July 2021 05:56 PM
To: devel@...; Srinivasan Tamilarasan <Srinivasan.Tamilarasan@...>
Subject: ODP: Issue when log2, printk and assert together

 

[External Email]: This email arrived from an external source - Please exercise caution when opening any attachments or clicking on links.

Hi,

 

good timing. Fix for that has been merged 40 minutes ago: https://github.com/zephyrproject-rtos/zephyr/pull/36883

When printk is redirected to logging (CONFIG_LOG_PRINTK) then printk.h includes log_msg2.h which includes cbprintf_internal.h which includes __assert.h which includes printk.h. Fixing it by adding compile time switches for including and using asserts in cbprintf and forcing to not use them when LOG_PRINTK is set. Fixes #36486.

github.com

 

 

regards,

Krzysztof


Od: devel@... <devel@...> w imieniu użytkownika Srinivasan Tamilarasan via lists.zephyrproject.org <srinivasan.tamilarasan=onsemi.com@...>
Wysłane: środa, 21 lipca 2021 14:23
Do: devel@... <devel@...>
Temat: [Zephyr-devel] Issue when log2, printk and assert together

 

Hi all,

When enable CONFIG_LOG2_MODE_DEFERRED=y, CONFIG_LOG_PRINTK=y and CONFIG_ASSERT=y flag. I am getting the build error even there is no log/assert messages are used.

 

PFA of cmake error log.

 

But when I change to old method CONFIG_LOG_MODE_DEFERRED=y then there is no build error.

 

Can anyone help me to resolve this error?

 

Idea is I need to use both assert and log together in the same project and printk messages needs to route via logging subsystem.

 

Regards,

Srinivasan


ODP: Issue when log2, printk and assert together

Chruściński, Krzysztof
 

Hi,

just tried it in hello_world and it compiles fine with configuration you've provided. Can you make sure that CBPRINTF_STATIC_PACKAGE_CHECK_ALIGNMENT is not set (it should be disabled by CONFIG_LOG_PRINTK).

regards,
Krzysztof

Od: Srinivasan Tamilarasan <Srinivasan.Tamilarasan@...>
Wysłane: piątek, 23 lipca 2021 08:16
Do: Chruściński, Krzysztof <Krzysztof.Chruscinski@...>; devel@... <devel@...>
Temat: RE: Issue when log2, printk and assert together
 

Hi,

I have cherry picked below 2 commits to zephyr2.6 branch and build it.

 

Then I have included the macros CONFIG_LOG=y , CONFIG_LOG2_MODE_DEFERRED=y, CONFIG_LOG_PRINTK=y and CONFIG_ASSERT=y. Then the build error got resolved and got below warning,

__ASSERT() statements are globally ENABLED

 

 

After that I have added below statement in my application,

__ASSERT(0, "ERRROR:Line:%d,File:%s\n", line, file);

 

Then again I am getting build error same like before the fix.

 

Is this issue completely resolved in the rtos? If it is any other commits do I need to take to resolve this issue?

 

Regards,

Srinivasan

 

From: Srinivasan Tamilarasan
Sent: 21 July 2021 06:07 PM
To: 'Chruściński, Krzysztof' <Krzysztof.Chruscinski@...>; devel@...
Subject: RE: Issue when log2, printk and assert together

 

Hi,

Good. It is got fixed now.

 

Thank you for the response.

 

Regards,

Srinivasan

 

From: Chruściński, Krzysztof <Krzysztof.Chruscinski@...>
Sent: 21 July 2021 05:56 PM
To: devel@...; Srinivasan Tamilarasan <Srinivasan.Tamilarasan@...>
Subject: ODP: Issue when log2, printk and assert together

 

[External Email]: This email arrived from an external source - Please exercise caution when opening any attachments or clicking on links.

Hi,

 

good timing. Fix for that has been merged 40 minutes ago: https://github.com/zephyrproject-rtos/zephyr/pull/36883

When printk is redirected to logging (CONFIG_LOG_PRINTK) then printk.h includes log_msg2.h which includes cbprintf_internal.h which includes __assert.h which includes printk.h. Fixing it by adding compile time switches for including and using asserts in cbprintf and forcing to not use them when LOG_PRINTK is set. Fixes #36486.

github.com

 

 

regards,

Krzysztof


Od: devel@... <devel@...> w imieniu użytkownika Srinivasan Tamilarasan via lists.zephyrproject.org <srinivasan.tamilarasan=onsemi.com@...>
Wysłane: środa, 21 lipca 2021 14:23
Do: devel@... <devel@...>
Temat: [Zephyr-devel] Issue when log2, printk and assert together

 

Hi all,

When enable CONFIG_LOG2_MODE_DEFERRED=y, CONFIG_LOG_PRINTK=y and CONFIG_ASSERT=y flag. I am getting the build error even there is no log/assert messages are used.

 

PFA of cmake error log.

 

But when I change to old method CONFIG_LOG_MODE_DEFERRED=y then there is no build error.

 

Can anyone help me to resolve this error?

 

Idea is I need to use both assert and log together in the same project and printk messages needs to route via logging subsystem.

 

Regards,

Srinivasan


Re: Issue when log2, printk and assert together

Srinivasan Tamilarasan
 

Hi,

I have cherry picked below 2 commits to zephyr2.6 branch and build it.

 

Then I have included the macros CONFIG_LOG=y , CONFIG_LOG2_MODE_DEFERRED=y, CONFIG_LOG_PRINTK=y and CONFIG_ASSERT=y. Then the build error got resolved and got below warning,

__ASSERT() statements are globally ENABLED

 

 

After that I have added below statement in my application,

__ASSERT(0, "ERRROR:Line:%d,File:%s\n", line, file);

 

Then again I am getting build error same like before the fix.

 

Is this issue completely resolved in the rtos? If it is any other commits do I need to take to resolve this issue?

 

Regards,

Srinivasan

 

From: Srinivasan Tamilarasan
Sent: 21 July 2021 06:07 PM
To: 'Chruściński, Krzysztof' <Krzysztof.Chruscinski@...>; devel@...
Subject: RE: Issue when log2, printk and assert together

 

Hi,

Good. It is got fixed now.

 

Thank you for the response.

 

Regards,

Srinivasan

 

From: Chruściński, Krzysztof <Krzysztof.Chruscinski@...>
Sent: 21 July 2021 05:56 PM
To: devel@...; Srinivasan Tamilarasan <Srinivasan.Tamilarasan@...>
Subject: ODP: Issue when log2, printk and assert together

 

[External Email]: This email arrived from an external source - Please exercise caution when opening any attachments or clicking on links.

Hi,

 

good timing. Fix for that has been merged 40 minutes ago: https://github.com/zephyrproject-rtos/zephyr/pull/36883

When printk is redirected to logging (CONFIG_LOG_PRINTK) then printk.h includes log_msg2.h which includes cbprintf_internal.h which includes __assert.h which includes printk.h. Fixing it by adding compile time switches for including and using asserts in cbprintf and forcing to not use them when LOG_PRINTK is set. Fixes #36486.

github.com

 

 

regards,

Krzysztof


Od: devel@... <devel@...> w imieniu użytkownika Srinivasan Tamilarasan via lists.zephyrproject.org <srinivasan.tamilarasan=onsemi.com@...>
Wysłane: środa, 21 lipca 2021 14:23
Do: devel@... <devel@...>
Temat: [Zephyr-devel] Issue when log2, printk and assert together

 

Hi all,

When enable CONFIG_LOG2_MODE_DEFERRED=y, CONFIG_LOG_PRINTK=y and CONFIG_ASSERT=y flag. I am getting the build error even there is no log/assert messages are used.

 

PFA of cmake error log.

 

But when I change to old method CONFIG_LOG_MODE_DEFERRED=y then there is no build error.

 

Can anyone help me to resolve this error?

 

Idea is I need to use both assert and log together in the same project and printk messages needs to route via logging subsystem.

 

Regards,

Srinivasan


Re: Dev-Review Meeting Agenda July 22th

Bolivar, Marti
 


Event: Zephyr Project: Dev Meeting - 07/22/2021 #cal-reminder

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

Reminder: Zephyr Project: Dev Meeting

When:
07/22/2021
3:00pm to 4:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

Organizer: devel@...

An RSVP is requested. Click here to RSVP

Description:

________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 483 314 739#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
 
 
________________________________________________________________________________


Dev-Review Meeting Agenda July 22th

Kumar Gala
 

linker: aarch32: automatic derivation of region names from devicetree nodes:
- https://github.com/zephyrproject-rtos/zephyr/pull/36365

RFC: API Change: Flash map:
- https://github.com/zephyrproject-rtos/zephyr/issues/34706

Plus anything anyone else has.

- k


Developer Experience WG kickoff, Doodle

Jonathan Beri
 

Hi all,

During the Developer Summit there was a great session on developer environments and we decided to kickoff a Developer Experience WG (see RFC here.) We want to have broad input so the group is open to the community. We're planning a kickoff event and since scheduling is hard, there's a Doodle. Please add your availability by July 23, 12pm PT.

Looking forward to improving the overall experience of Zephyr, together!

--


Re: Issue when log2, printk and assert together

Srinivasan Tamilarasan
 

Hi,

Good. It is got fixed now.

 

Thank you for the response.

 

Regards,

Srinivasan

 

From: Chruściński, Krzysztof <Krzysztof.Chruscinski@...>
Sent: 21 July 2021 05:56 PM
To: devel@...; Srinivasan Tamilarasan <Srinivasan.Tamilarasan@...>
Subject: ODP: Issue when log2, printk and assert together

 

[External Email]: This email arrived from an external source - Please exercise caution when opening any attachments or clicking on links.

Hi,

 

good timing. Fix for that has been merged 40 minutes ago: https://github.com/zephyrproject-rtos/zephyr/pull/36883

When printk is redirected to logging (CONFIG_LOG_PRINTK) then printk.h includes log_msg2.h which includes cbprintf_internal.h which includes __assert.h which includes printk.h. Fixing it by adding compile time switches for including and using asserts in cbprintf and forcing to not use them when LOG_PRINTK is set. Fixes #36486.

github.com

 

 

regards,

Krzysztof


Od: devel@... <devel@...> w imieniu użytkownika Srinivasan Tamilarasan via lists.zephyrproject.org <srinivasan.tamilarasan=onsemi.com@...>
Wysłane: środa, 21 lipca 2021 14:23
Do: devel@... <devel@...>
Temat: [Zephyr-devel] Issue when log2, printk and assert together

 

Hi all,

When enable CONFIG_LOG2_MODE_DEFERRED=y, CONFIG_LOG_PRINTK=y and CONFIG_ASSERT=y flag. I am getting the build error even there is no log/assert messages are used.

 

PFA of cmake error log.

 

But when I change to old method CONFIG_LOG_MODE_DEFERRED=y then there is no build error.

 

Can anyone help me to resolve this error?

 

Idea is I need to use both assert and log together in the same project and printk messages needs to route via logging subsystem.

 

Regards,

Srinivasan


ODP: Issue when log2, printk and assert together

Chruściński, Krzysztof
 

Hi,

good timing. Fix for that has been merged 40 minutes ago: https://github.com/zephyrproject-rtos/zephyr/pull/36883
When printk is redirected to logging (CONFIG_LOG_PRINTK) then printk.h includes log_msg2.h which includes cbprintf_internal.h which includes __assert.h which includes printk.h. Fixing it by adding compile time switches for including and using asserts in cbprintf and forcing to not use them when LOG_PRINTK is set. Fixes #36486.
github.com


regards,
Krzysztof

Od: devel@... <devel@...> w imieniu użytkownika Srinivasan Tamilarasan via lists.zephyrproject.org <srinivasan.tamilarasan=onsemi.com@...>
Wysłane: środa, 21 lipca 2021 14:23
Do: devel@... <devel@...>
Temat: [Zephyr-devel] Issue when log2, printk and assert together
 

Hi all,

When enable CONFIG_LOG2_MODE_DEFERRED=y, CONFIG_LOG_PRINTK=y and CONFIG_ASSERT=y flag. I am getting the build error even there is no log/assert messages are used.

 

PFA of cmake error log.

 

But when I change to old method CONFIG_LOG_MODE_DEFERRED=y then there is no build error.

 

Can anyone help me to resolve this error?

 

Idea is I need to use both assert and log together in the same project and printk messages needs to route via logging subsystem.

 

Regards,

Srinivasan


Issue when log2, printk and assert together

Srinivasan Tamilarasan
 

Hi all,

When enable CONFIG_LOG2_MODE_DEFERRED=y, CONFIG_LOG_PRINTK=y and CONFIG_ASSERT=y flag. I am getting the build error even there is no log/assert messages are used.

 

PFA of cmake error log.

 

But when I change to old method CONFIG_LOG_MODE_DEFERRED=y then there is no build error.

 

Can anyone help me to resolve this error?

 

Idea is I need to use both assert and log together in the same project and printk messages needs to route via logging subsystem.

 

Regards,

Srinivasan


API meeting cancelled today

Carles Cufi
 

Hi all,

I cancelled the API meeting today, due to holidays and lack of urgent issues to discuss.

Thanks,

Carles

1 - 400 of 7909