Some WARNNING in compiling.

RE: Some WARNNING in compiling.

Carl Richard — Wed, 04 Nov 2020 09:07:58 GMT

Good to hear! Glad I could help.

The topic is now closed. Have a good day!

Best regards,
Carl Richard

RE: Some WARNNING in compiling.

wzszzxj — Wed, 04 Nov 2020 02:16:24 GMT

Hi，Carl：

Thank you for your reply, Pls close this topic,thank you!

RE: Some WARNNING in compiling.

Carl Richard — Mon, 14 Sep 2020 11:51:57 GMT

Hello!

Could you try to turn of compilation optimization in Segger and see if that helps? Right click the project, select "options" and choose "Optimization level" none for all project instances. See the picture below:

It could be that "m" is optimized away if it's not used.

Best regards,
Carl Richard

RE: Some WARNNING in compiling.

wzszzxj — Sat, 12 Sep 2020 03:28:33 GMT

Hi,Carl:

About the bTime1msInterval is solved,I changed it' type from union to staic bool. But this morning,I use a local parameter in a function.When reaching it,I can't be changed correctly by OR 0x01.The code is blow:

Step1:

Step2:

when the PC reach m=m|0x01;,and surmount it,It's value still is 0x00.

RE: Some WARNNING in compiling.

Carl Richard — Fri, 11 Sep 2020 11:56:35 GMT

Hi!

1. Good that it works with the nRF52833. What kind of warning do you get when compiling?

2. I see that bTime1msInterval is declared using #define, and using data from the timeflag1 union which doesn't make much sense as #define are handled during compilation, while timeflag1 will be declared during runtime. What are you trying to achieve?

Best regards,
Carl Richard

RE: Some WARNNING in compiling.

wzszzxj — Thu, 10 Sep 2020 13:24:58 GMT

Hi,Carl Richard:

1 .nrf5 SDk16 examples: BLE_APP_mouse But i have change to nrf52833 chip, and it can work in a part of working not finished.Just come out the warnning when compiling.

2.here,there is also a question:from the picture below, the bit flag bTime1msInterval has already been 0x01,while it can reach the next breakpoint. En,the question is about the segger Embeded Studio,the bTime1msInterval is the bitfield defined by me as below: but even if() statement has been no influence to it,Ex if(bTime1msInterval)...

union
{
uint32_t byte;
struct{
bool time1ms ;
bool time1msinterval ;
bool timepwmchange ;
}bits;
}timeflag1;

#define vTimeFlag1 timeflag1.byte
#define bTime1ms timeflag1.bits.time1ms
#define bTime1msInterval timeflag1.bits.time1msinterval
#define bTimePwmChange timeflag1.bits.timepwmchange

RE: Some WARNNING in compiling.

Carl Richard — Thu, 10 Sep 2020 09:03:59 GMT

Hi!

First some questions to clarify things:

- What SDK are you using?

- Are your code based on an example? If so, which and Is it modified?

- What is your development environment?

Could you also provide a more detailed log of the events?

Best regards,
Carl Richard