Add a weak pull-up on fx3_uart_rxd
This is a bus used for both FPGA-to-FX3 UART data and FX3-to-Flash
SPI data, and without something driving it, it tends to float around
0.55 volts (which is very much a low/asserted signal for the UART).
When the FX3 SPI interface has the bus, it puts the FPGA into reset
via fx3_ctl(7), and fx3_uart_rxd goes high-Z accordingly.
I suspect what we're running into is a race condition between the FX3
reconfiguring the pin to UART mode and bringing the FPGA out of reset,
and the FPGA shifting from high-Z to high/idle, given:
- All of the "junk bytes" seen so far have been all ones followed by
all zeroes, e.g. 0xF0, 0xFC, etc
- Being low for 5 clocks and then going high is indistinguishable from
a start bit followed by 0xF0 followed by a stop bit.
Thus, by maintaining a constant weak pull-up on this bus, we can
ensure it's a logic high when idle.
There are possible side effects when the bus is in its SPI MOSI role,
but I believe they are minor. The FX3 is not expecting a pull-up/down
on this signal, and this is a critical pin for flash access. But,
C5's R_pu is 25 kohms, which means sinking 1.4 mA to pull it low, and
the FX3's absolute maximum output current is 20 mA, so I think we are
good here.
The 16 LSBs of the flag word are overwritten by the GPIF state machine. The
other half is under control by the fifo_writer. Care should be taken when
appropriating new bits.
Bit 1 now encodes no "underrun", and bit 0 continues to encode "underrun."
There is a case to say that this file should not be duplicated and kept in
common/. However the platform common directory is more much more abstract pieces
of code.
bladerf-adsb.vhd is a direct copy of bladerf-hosted.vhd. rx-adsb.vhd is a direct
copy of rx.vhd. These files will be modified to instantiate and enable the ADS-B
core.
The use of 'readlink' with 'quartus_sh' results in bogus paths when
inside a Cygwin environment. Use of 'readlink' was determined to be
unnecessary and was removed.
synchronizes and/or registers:
lms_rx_enable_qualified, into rx_clock
xb_gpio_dir and dac_csx, into 80MHz
fx3_uart_cts, into fx3_pclk_pll
Improves timing closure probability
This commit updates the timing constraints for the bladerf1 to
constrain a number of previously-unconstrained paths:
fx3_uart_cts
lms_sclk
exp_{spi_clock,spi_mosi,gpio[*],clock_in}
mini_exp{1,2}
It also fixes the false_path for the TX FIFO ACLRs.
Move the bladerf_agc_lms_drv component into the 80 MHz clock domain.
This ensures that it has a consistent clock to work with, instead of the
variable rx_clock. This ensures the SPI clock will always be 20 MHz, and
that everything is passing between known clock domains.
Adds the requisite synchronizers, etc.
Fixes#607
The nios_gpio bit assignment for AGC_EN was already being used for
led(1). This commit also fixes a bug in the agc_band_sel signal
assignment introduced in 3b670ca.
Latch the data heading to the DAC, so that it is valid when the AD9361
interface expects it.
This addresses a bug in single-channel TX mode where samples would get
rearranged under some circumstances.
* hdl: bladeRF-micro: adjust pin layout for rev1.1 hw
Update the pinouts for adi_{rx,tx}_spdt{1,2}_v{1,2} to reflect move from
bank 5A to banks 5B/4A
Move INA219 I2C pins to bank 5A
Move ADP2384 sync pins to bank 7A
Move ADF4002 control pins to bank 5A
* hdl: bladeRF-micro: move {rx,tx}_bias_en from bank 7A to 5A
rx_bias_en moves from J11 to R22
tx_bias_en moves from A13 to R21
* hdl: bladeRF-micro: move mini_exp{1,2}, rm c5_clock1
In Bank 7A,
c5_clock1 is deleted from H16
mini_exp1 moves from J18 to H16
mini_exp2 moves from J17 to H15
* hdl: bladeRF-micro: remove refs to c5_clock1
* hdl: bladeRF-micro: set max toggle rate for SPDT switches
Fixes Critical Warning (12888) for high estimated crosstalk
on adi_rx_data[1] by adi_{rx,tx}_spdt{1,2}_v[{1,2}]
Changed from "output" to "inout" to accept inputs. In this mode, the
GPIO has two independent buses, one for input, one for output. In order
to maintain previous behavior, which allowed the Nios to read the
current values being output, we must explicitly feed back the output bus
to the input bus.
Add bladerf_p.vhd package, which handles nios_gpio packing and unpacking
between bits and record elements. This consolidates bit-to-function
mapping, making it easier to modify the mapping in the future.
This package also defines the FIFO record types and the nios_system
component for easier re-use.
Delete empty SOPC directories created by Quartus during IP core
generation. These empty directories are created in the user's home
directory and can accumulate if left unchecked. Use `find' with
approprate filters to (hopefully) avoid deleting anything important!
Quartus supports different build flows. Adding support for that so that
a user can choose to simply generate the project files, run synthesis
only (e.g. to check syntax), or do the full place and route to generate
programming files.
The project revision option specified on the command line was not being
passed to the build Tcl file.
Changed handling of message suppression files. Filename should be the
same as the revision name. Instead of managing potentially several
identical or nearly identical .srf files, just manage the one and have
the build script rename it when copying it to the build directory.
Fixed references to the nios_system.qip file in bladerf-fsk_bridge.qip
and bladerf-qpsk_tx.qip.
- Add "board" as a required option in help text
- The description of the SignalTap force option was vague.
- Added check for null argument.
- Do not print full usage information for an invalid option.
Beginning in Quartus 14.0, the NiosII processor split into two versions:
Classic and Gen 2. Development of new features for the Classic ceased in
Quartus 14.0. Nuand upgraded to the Gen 2 core for the release of the
bladeRF micro. The Gen 2 core does not have an option for the
Small (NiosII/s) implementation, so the option was removed from the
build script.
Nuand may add a NiosII/s approximation of the NiosII/f in the
future. This will happen quicker if we get requests to do so. :)