interrupt | A community for embedded software makers

Try this it may help

A lot could be said about this code. I really don't understand why you're doing things quite the way you are. But, if I go for the smallest change that would make your code work, it's as follows.

You have this sort of pattern repeated in your dot, line, pause:

volatile informs the compiler that object is side effects prone. It means that it can be changed by something which is not in the program execution path.

As you never call the interrupt routine directly compiler assumes that the test variable will never be 1. You need to tell him (volatile does it) that it may change anyway.

example:

From some research, it looks like computers have a hardware timer called a programmable interval timer (PIT), which the OS can use to set a time in the future to cause an "interrupt" in some milliseconds or nanoseconds in the future.

Is there generic practices and patterns to succesfully switch from dynamic to static memory allocation without breaking the code ?

No, not really. You'll have to rewrite all such code in pretty radical ways.

You have to realize why all safety-related and embedded systems ban malloc. The main reason is that it is non-deterministic. Instead of allowing completely variable sizes, you have to specify a maximum size for each such item, to cover the worst case scenario of the application.

Also, the presence of things like pointer-to-pointers instead of 2D arrays is a pretty certain indication that the original programmer didn't quite know what they were doing in the first place.

Additionally you need to drop the default types of C for stdint.h ones. That's standard practice in all embedded systems.

In general, I'd strongly advise to drop those "NASA rules" and implement MISRA-C instead. It's a way more professional and in-depth document. Some of the "NASA rules" simply don't make sense and the rest can be summarized as "No s***t Sherlock" beginner-level stuff which we were already told during our first beginner-level C programming class back in school. If these rules come as a surprise to someone, they shouldn't be writing mission-critical firmware in the first place.

Search your code for where the @interface for ESPTaskParameter is defined, that will be in some .h file. Then, make sure the .m file #imports that header file. If it doesn’t the there would indeed be no visible interface defining the selector you want to call to the .m file that is trying to call it

And check that the interface .h does indeed declare a public setter for broadcast.

The solution is to create a .env file to set the src folder in PYTHONPATH otherwise pytest is unable to find the model package. Also, putting conftest.py inside the src folder doesn't help as suggested by someone.

According to Docs, there is table(DB instance class) which tells which settings can be changed, you can change your instance class for your aurora, as a note An outage occurs during this change.

For redis

according to docs, you can scale down node type of your redis cluster (version 3.2 or newer). During scale down ElastiCache dynamically resizes your cluster while remaining online and serving requests.

In both the cases your data will be preserved.