Infinite build loop with some examples, dirty build.ninja

RE: Infinite build loop with some examples, dirty build.ninja

alnyland — Mon, 08 Jul 2024 15:25:44 GMT

Glad to hear, I honestly forgot that I'd put a conclusion to this issue. I'll go ahead and mark it as solved, hopefully that allows it to stay around for others to look at when needed.

This issue was so weird, it was I guess a compile time error that was shown to the developer as a very different issue. And it doesn't help when there are multiple layers of build systems.

RE: Infinite build loop with some examples, dirty build.ninja

Th2001 — Mon, 08 Jul 2024 14:39:24 GMT

Thanks alnyland, I've just encountered this issue today

RE: Infinite build loop with some examples, dirty build.ninja

alnyland — Mon, 26 Feb 2024 16:18:14 GMT

The issue ended up being from a compile time error that was hidden in the print statements most of the time I tried.

/opt/nordic/ncs/v2.5.2/nrf/lib/edge_impulse/ei_wrapper.cpp: At global scope:

/opt/nordic/ncs/v2.5.2/nrf/lib/edge_impulse/ei_wrapper.cpp:56:31: error: static assertion failed

   56 | BUILD_ASSERT(DATA_BUFFER_SIZE > INPUT_WINDOW_SIZE);

/opt/nordic/ncs/v2.5.2/zephyr/include/zephyr/toolchain/gcc.h:70:50: note: in definition of macro 'BUILD_ASSERT'

   70 | #define BUILD_ASSERT(EXPR, MSG...) static_assert(EXPR, "" MSG)

      |                                                  ^~~~

/opt/nordic/ncs/v2.5.2/nrf/lib/edge_impulse/ei_wrapper.cpp:56:31: note: the comparison reduces to '(2500 > 9216)'

   56 | BUILD_ASSERT(DATA_BUFFER_SIZE > INPUT_WINDOW_SIZE);

/opt/nordic/ncs/v2.5.2/zephyr/include/zephyr/toolchain/gcc.h:70:50: note: in definition of macro 'BUILD_ASSERT'

   70 | #define BUILD_ASSERT(EXPR, MSG...) static_assert(EXPR, "" MSG)

      |                                                  ^~~~

ninja: build stopped: subcommand failed.

By adding CONFIG_EI_WRAPPER_DATA_BUF_SIZE=[bigger size] to the prj.conf I was able to fix this issue.

Edit (an hour later): This only fixed it for the one project, the Continuous Motion project that was working before is not working currently.

RE: Infinite build loop with some examples, dirty build.ninja

alnyland — Mon, 26 Feb 2024 16:15:21 GMT

I haven't tried the data_forwarder example as I have no sensors so I'm only using the Wrapper example. It was only reproducible with EI generated code for certain types of projects.

I ended up figuring it out finally. I'll add that here or edit the original post so anyone else in the future can fix it as well.

RE: Infinite build loop with some examples, dirty build.ninja

runsiv — Fri, 23 Feb 2024 13:58:36 GMT

I honestly don't know. I tried to build just the forwarder example on my end and everything was working. I would presume this is when you are uploading an EI generated code?

Regards

Runar

RE: Infinite build loop with some examples, dirty build.ninja

alnyland — Thu, 22 Feb 2024 17:51:27 GMT

Now I'm getting a new/diff error that be more nRF related:

/opt/nordic/ncs/v2.5.2/nrf/lib/edge_impulse/ei_wrapper.cpp: At global scope:
/opt/nordic/ncs/v2.5.2/nrf/lib/edge_impulse/ei_wrapper.cpp:56:31: error: static assertion failed
56 | BUILD_ASSERT(DATA_BUFFER_SIZE > INPUT_WINDOW_SIZE);
/opt/nordic/ncs/v2.5.2/zephyr/include/zephyr/toolchain/gcc.h:70:50: note: in definition of macro 'BUILD_ASSERT'
70 | #define BUILD_ASSERT(EXPR, MSG...) static_assert(EXPR, "" MSG)
| ^~~~
/opt/nordic/ncs/v2.5.2/nrf/lib/edge_impulse/ei_wrapper.cpp:56:31: note: the comparison reduces to '(2500 > 9216)'
56 | BUILD_ASSERT(DATA_BUFFER_SIZE > INPUT_WINDOW_SIZE);
/opt/nordic/ncs/v2.5.2/zephyr/include/zephyr/toolchain/gcc.h:70:50: note: in definition of macro 'BUILD_ASSERT'
70 | #define BUILD_ASSERT(EXPR, MSG...) static_assert(EXPR, "" MSG)

Is this an EI or nRF issue? I'm not sure where I could modify the DATA_BUFFER_SIZE value and it appears to be provided by nRF code.

RE: Infinite build loop with some examples, dirty build.ninja

alnyland — Thu, 22 Feb 2024 16:34:56 GMT

I'm pretty sure my clock is correct, I've checked that a few times. I'm on macOS so the path issue should exist here, my time is set to time.apple.com but I've tried updating from ntp as well. The weirder part is that yesterday morning, I had two almost identical projects setup and one worked just fine and the other did not (had this issue), but I can't find any relevant file differences that would seem to cause it. I know the main difference is out of scope for here but it's a somewhat commonly used same provided by nRF so I thought maybe someone here had seen this problem before.

RE: Infinite build loop with some examples, dirty build.ninja

runsiv — Thu, 22 Feb 2024 13:27:22 GMT

So its might sound a bit strange, but are you sure your computer time is correct? I found a issue at ninjas github where people wrote adjusting the computers/sync it fixed their error. Other solutions was path length, but that should not be an issue for OSX as far as I know or if you have any special symbols in your path.

Have you tried to delete the build folder and create a new config and build it? It often fixes strange problems

Regards

RE: Infinite build loop with some examples, dirty build.ninja

runsiv — Thu, 22 Feb 2024 11:44:34 GMT

Hi Andrew

I will look into the case and get back to you

Regards

Runar