|
From: Charles S. <ch...@st...> - 2014-07-01 17:49:03
|
On 7/1/2014 12:36 PM, Marius Liebenberg wrote: > I am using the print thing now so that helps s lot. > The problem I have with loading the realtime subsystem is that when I > screw up I already have a module loaded that is sometimes difficult to > remove without rebooting the system. I've generally found that: realtime stop halrun -U ...fixes up most problems, but then I generally play around in user space and not kernel mode. Regardless, unless your problematic realtime module is required to test your python script, just don't load it. Simply starting the realtime so HAL has a place to put pins and parameters is enough to do testing with usermode python scripts. If you do need some sort of input, you can probably use existing and (hopefully) well behaved HAL components to generate it (siggen, sim_encoder, streamer, etc) either by hand or with a simple HAL file to use as a testbench. -- Charles Steinkuehler ch...@st... |