[chirp_devel] Run_Tests errors
I am getting the following error from BruteForce testing- Failed to validate Memory 0: 2.400000/0.600000 LSB () r88.5 c88.5 d023 NN [5.00]: ['Frequency 2.400000 is out of supported range'] Failed to validate Memory 0: 2.400000/0.600000 USB () r88.5 c88.5 d023 NN [5.00]: ['Frequency 2.400000 is out of supported range'] Failed to validate Memory 0: 2.400000/0.600000 CW () r88.5 c88.5 d023 NN [5.00]: ['Frequency 2.400000 is out of supported range'] Failed to validate Memory 0: 2.400000/0.600000 FM () r88.5 c88.5 d023 NN [5.00]: ['Frequency 2.400000 is out of supported range'] Failed to validate Memory 0: 2.400000/0.600000 AM () r88.5 c88.5 d023 NN [5.00]: ['Frequency 2.400000 is out of supported range'] Failed to validate Memory 0: 2.400000/0.600000 FSK () r88.5 c88.5 d023 NN [5.00]: ['Frequency 2.400000 is out of supported range'] Failed to validate Memory 0: 2.400000/0.600000 CW-R () r88.5 c88.5 d023 NN [5.00]: ['Frequency 2.400000 is out of supported range'] Failed to validate Memory 0: 2.400000/0.600000 FSK-R () r88.5 c88.5 d023 NN [5.00]: ['Frequency 2.400000 is out of supported range'] Failed to validate Memory 0: 2.400000/0.600000 Data+LSB () r88.5 c88.5 d023 NN [5.00]: ['Frequency 2.400000 is out of supported range'] Failed to validate Memory 0: 2.400000/0.600000 Data+USB () r88.5 c88.5 d023 NN [5.00]: ['Frequency 2.400000 is out of supported range'] Failed to validate Memory 0: 2.400000/0.600000 Data+FM () r88.5 c88.5 d023 NN [5.00]: ['Frequency 2.400000 is out of supported range']
Where is that 2.4 MHz value coming from? The Valid Bands declaration excludes it, so yes, it will fail. My test img file has 3.985 MHz in memory channel 0. This is also causing the Edges test to fail with: "No mutable memory locations found"
Where is that 2.4 MHz value coming from? The Valid Bands declaration excludes it, so yes, it will fail. My test img file has 3.985 MHz in memory channel 0.
You'll have to read the test, but it's probably choosing one of the band edges you've provided. It is trying to take the features a driver exposes and synthesize a memory that the driver will accept in order to poke everything else about it. If it's choosing poorly, the test might need a tweak, but we should do so carefully.
This is also causing the Edges test to fail with: "No mutable memory locations found"
This is it doing a similar thing, looking for a memory/location combo that works so it can try things like setting memories *at* the band edges, etc.
--Dan
participants (2)
-
Dan Smith -
Rick DeWitt AA0RD