Developing HAL Components

Hi,

I'm wondering if there are any best practices and strategies for developing HAL components. Code testing is a bit hard in the context of a RT thread. Is there any approach for unit testing of components?
Something like JUinit would be great that one can define the test cases together with the code.

Maybe this is already somewhere but I missed it.

Regards,
Tom

most hal componets are made bye Users themself for special cases
the standard components are integreded and as so many uses them are testet all over

so what are you trying to get working
did you check the comps in the system
linuxcnc.org/docs/html/man/man9/
linuxcnc.org/docs/html/man/man1/

It's not my aim to re-test existing components. I want to test my own ones.

I now figured out how halstreamer and halsampler works for testing logic. I also saw how to test timing functions. But I still lock for a way to test the component with different parameters. I could create a (sub) test for each parameter combinations. This should work. Maybe there is a better way to do this.

Debugging Interrupt driven code is always hard. In the first instance, small components are easier to debug than complex ones. Studying your code critically before deployment is the next step. Building a sim config is also powerful.

Some behaviour is pretty easy to debug with halshow but for more complex real time stuff, Halscope is very useful as it shows what is going on in real time. Also there is a module called sim_pin which allows you to change data on the fly while debugging. The current docs are not leaping out at me so read this:
linuxcnc.org/docs/html/man/man1/sim_pin.1.html

So putting this together, I have one config originally written by Dewey Garrett that opens up several SIM-PIN windows and Halscope with prediefned variables which is quite an eyeopener