It appears that the voltage across the LEDs is always large
enough to keep them ON despite the output voltage.
A potential workaround for this rev of the XB100 is to use the
directionality of the LED IO pins to turn the LED on/off.
Both the host and NIOS II FPGA retuning modes now make use of
FPGA v0.4.0's atomic write of the LMS6002D NINT and NFRAC PLL registers.
This helps avoid changing the PLL multiple times when attempting to
configure it.
Achieved by adding extra address bit (now 8 bits) to Avalon-MM
interface. The MSB indicates a multi-write instruction. For TX, the
addresses are 0x90-0x93. For RX, the addresses are 0xA0-0xA3. The
individual writes are queued up until a write to the final address is
detected (0x93 or 0xA3), then all four PLL configuration registers are
written to the LMS chip in one contiguous chip select burst.
Testbench updated to be self-checking.
This should help clarify the cause of file-related errors in
cases where folks are trying to rx into a location where they
do not have write permissions.
The cause of tuning failures in "FPGA tuning" mode is caused by
long VTUNE settling times when switching between the search for
VTUNE HIGH and VTUNE LOW.
We now try to force VTUNE to the opposite value and poll for the
expected change instead of simply delaying and hoping VTUNE
has settled before we sample it. If we don't hit the expected VTUNE
value, we'll attempt to walk VTUNE into that region.
With the addition of a warning to the lms.c code, we've been seeing
some codes hit a max VCOCAP value before hitting a VCO limit, indicating
that we're too close to the edge of a band.
Updated 'print' to note that all parameters are now printed when
no arguments are provided.
Adjusted print and set widths to yield the same formatting in the
bladeRF-cli help output. (Closes#422)
Added help text entries for xb_* commands. (Closes#423)
Various items supported by 'print' have been made a bit more
consistent in terms of spacing.
Units have been separated from numbers, as typically recommended by
NIST.
Some options have been added to the printset_table to specify how
to group items when printing all of them (and to skip items).
The print command invoked without arguments in bladeRF-cli
is modified to invoke all the print/set parameter
handlers in order. Old behavior was to display usage note.
The leading and trailing cosmetic newlines were moved from the
individual printset handlers to cmd_print() to allow for a concise
table.
Original usage information is still available via help command.
While we could read back the mux state via gpio to infer what filters were
previously set, we don't know if the user had selected them explicitly or
had been using the auto_1db or auto_3db filters. Since it's ambiguous, we
should instead apply a default so that users can expect consistent results.
Handling of the XB-200 hard and auto filters is separated into two
paths to avoid the confusion introduced in the fix for #404.
xb200_set_filterbank is the internal API entry point for the external
bladerf_xb200_set_filterbank. If the configured filter is a hard
filter, then internal state is updated and set_filterbank_mux is
invoked to realize the hardware changes.
If the configured filter is an automatic filter, then internal state
is updated and xb200_auto_filter_selection() is called with the
currently tuned frequency for specificed module.
xb200_auto_filter_selection() then invokes set_filterbank_mux to
realize the hardware changes.
Enable/Disable the TalkBack feature of Quartus based on SignalTap
insertion and if the user really wants to force the script to enable
and disable it at the end of building.
If TalkBack is disabled, and SignalTap is requested to be added to
the project, then the build will now fail instead of warn about
TalkBack not being enabled.
Updating the simulation 'model' for the NIOS II component so the
entire top level can be simulated in ModelSim.
Also changing a generate from generating many processes to a single
process with a for-loop inside of it.
Failures have been observed when using FPGA tuning to retune
between vastly different frequencies. It appears that in cases
where significant VCOCAP changes take place, much longer delay between
VCOCAP updates and VTUNE reads are needed than currently utilized in the
NIOS II implementation.
Until this is resolved, host tuning is being set as the default mode,
which does not exhibit this failure because register access overhead
incurs more than ample delay.
Per CID 1288660 and CID 1288661, these cases were the only times
these were accessed without holding the buffer management lock.
Although there shouldn't be a race here, this change is introduced to
maintain consistency with other accesses of the sync i/f state info.
This addresses an item picked up by Coverity. Defects in bands[] or
frequency checks could potentially cause an out-of-bounds memory access.
A bounds check has been added to avoid an invalid access, should one of
the aforementioned defect ever creep in.