Hi Don, > I don't like having to run a series of several commands over and over. > It seems like I frequently miss one and things get confused.
Yes I agree, it's best to automate steps if possible with a reasonable amount of work. One other method is to include the test vectors in the stm32 unit tests as a header file, for example when testing the OFDM modulator: - run x86 test program to generate target modulator samples as raw file - convert say 1 sec of raw file to a C header file - build this with stm32 unit test - stm32 unit tests compares it's output with samples in header file - stm32 unit test prints pass/fail So the steps to run the test are "make" and the step to flash the stm32 using the tool of your choice. The steps above can be implemented in cmake files, and be part of the automated build process for the unit test. I think there is already a raw2h.c utility for generating the header files. - David ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Freetel-codec2 mailing list Freetel-codec2@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freetel-codec2
