disabling optimization on part of code

RE: disabling optimization on part of code

bloobird0 — Wed, 19 Oct 2016 11:19:32 GMT

Thanks. It should do the work.

RE: disabling optimization on part of code

bloobird0 — Wed, 19 Oct 2016 11:19:02 GMT

@RK: I agree with you. Because the behaviour was not the same between optimization levels 0 and 1, I thought it could be an optimization problem.

RE: disabling optimization on part of code

bjorn-spockeli — Tue, 18 Oct 2016 08:59:13 GMT

You can set the optimization level of individual files in Keil by right-clicking them, select "Options for file" and then select the "C/C++" tab, see attached screenshot.

-Bjørn

RE: disabling optimization on part of code

RK — Mon, 17 Oct 2016 23:06:59 GMT

Just because you can't set a breakpoint on the line doesn't mean the code hasn't been compiled. It's been compiled and it's in the executable, it just has been optimised so there is no debug information about that line.

You have misidentified your problem.

RE: disabling optimization on part of code

FormerMember — Mon, 17 Oct 2016 17:31:00 GMT

Not sure, but replacing the inline function with directly writing to the register as shown below might enable you to set a breakpoint.

NRF_GPIO->PIN_CNF[15] = (NRF_GPIO_PIN_SENSE_LOW << GPIO_PIN_CNF_SENSE_Pos) | (GPIO_PIN_CNF_DRIVE_S0S1 << GPIO_PIN_CNF_DRIVE_Pos) | (NRF_GPIO_PIN_PULLUP << GPIO_PIN_CNF_PULL_Pos) | (GPIO_PIN_CNF_INPUT_Connect << GPIO_PIN_CNF_INPUT_Pos) | (GPIO_PIN_CNF_DIR_Input << GPIO_PIN_CNF_DIR_Pos);