Mark VanderVoord

:) the tricky part is that many of the steps require the previous step to be run before we know what is to be run for that step. For example,...

:) I wasn't going to try to talk you out of disabling the preprocessing. I was just attempting to narrow down the situations where this problem happens.

I might be misunderstanding, but it sounds like the main issue you're running into is that the things you want to test have dependencies in other modules? Things that can...

Thanks for the detailed investigation! This should definitely help me to hunt down the issue!

I think it's less about the number of arguments and more about total line length? (which is 8191 characters on Windows)

is that what most of the characters are in your setup? include directories?

Here are some ideas towards working with registers: https://vandervoord.net/blog/2015/5/24/unit-test-how-registers https://vandervoord.net/blog/2015/5/24/unit-test-how-faking-changing-registers https://vandervoord.net/blog/2015/5/24/unit-test-how-verifying-multiple-register-writes To mock low-level API calls which are macros, you can perform a similar trick. ``` #ifdef TEST void WRITE_REG(uint32_t...

If you rerun the test with verbosity turned up, it should show the call you're making to the assembler. Does it look correct? It seems like it's trying to call...

It appears from that snippet that motorDrive.c includes peripherals.h which includes ccjubmUE.s (or does motorDrive.c directly include it?) I'm just trying to see how you get to the point where...

Nope. All of Ceedling's output goes into the build directory and subdirectory. This is one of the other tools. I'm not really sure what is going on here. If you...