| Rev |
Log message |
Author |
Age |
Path |
| 29 |
some bugfixes and here and there some comment cleaning |
nussgipfel |
5369d 16h |
/gecko3/trunk/GECKO3COM/gecko3com-fw/ |
| 28 |
switched to work on the v1 production GECKO3main. the timing is a big issue
with the prototype system. the cabeling and the possibly bad influence of the
prototype board layout makes it impossible to run this core in sync with the
host transfers.
out transfer is fully working. always in sync with the transfers and reads all
tmc headers correctly.
abort handling in the core works as well. there were some fixes needed in the
firmware, not all IN FIFO buffer where flushed.
a lot of work was done for the IN transfer (fpga to pc). the in transfer
handling in GECKO3COM_simple_test.vhd is finished.
the GECKO3COM_simple_datapath/fsm is finished.
there is still an issue left but I think the problem is in the gpif_com
module. for long IN transfers, we still not receive the correct number of bytes.
it works great for all sort of short transfers.
Here I present a time measurement to show the achieved message throughput:
(Response message was 1 byte, total with header and align bytes was 16 byte)
time for i in {0..100000}; do cat /dev/usbtmc1 > /dev/null; done
real 5m45.706s
user 0m27.498s
sys 4m52.676s
This shows that we can read data from the fpga with a rate up to 290 Hz |
nussgipfel |
5371d 17h |
/gecko3/trunk/GECKO3COM/gecko3com-fw/ |
| 21 |
system is fully working and tested with big files over 4 Gbyte. there were some smaller bugs and glitches which caused
sometimes a deadlock. they are fixed now.
one was because the fx2 reads the done pin sometimes wrong during a long data
transfer. I don't now if this is because of crosstalk on my prototyping system or fpga internal weakness.
a simple debouncing (read again after 40 ms) did the trick.
changed firmware version to 0.5rc0, basically all features targeted for 0.5 are done. |
nussgipfel |
5400d 17h |
/gecko3/trunk/GECKO3COM/gecko3com-fw/ |
| 20 |
basic synchronous IN (fpga to host) transfer works.
detail changes:
-the scpi command "fpga:data" checks now, if the fpga is configured before it changes the context to the fpga. if the fpga is
not configured, it returns an "EXECUTE ERROR".
in the same way, the main_loop checks if the fpga looses his configuration. it disables the GPIF, switches the context back
to the fx2 if so. this is mainly to avoid undeterministic behaviour if you reconfigure the fpga via jtag.
-introduced the new signal "EOM" end of message from the "usb tmc protokoll interpreter" to the gpif_com module
-changed the GPIF waveform for the FIFO IN transfer to the new scheme.
-implemented the same waveform into the gpif_com_fsm.vhd. works well together.
-bugfixed the gpif_com_test.vhd. sends the new EOM signal, the response message generator works now as it should.
-added the missing AUTHORS README and COPYING (license) files to the core directory. |
nussgipfel |
5401d 15h |
/gecko3/trunk/GECKO3COM/gecko3com-fw/ |
| 19 |
found a pinning error in the series production documentation. fixed in the wiki and the core.
really stable host to fpga data transfer achieved. several time over 4Gbyte transfered. including switching to fpga to
host GPIF waveform to listen to possible fpga transfer tries. but fpga to host transfers still not finished.
the correct length of data is read from the gpif_fsm now. still untested data consitency when data flow throtling occours.
need bigger buffers to test this. will be done on a higher level. |
nussgipfel |
5409d 17h |
/gecko3/trunk/GECKO3COM/gecko3com-fw/ |
| 18 |
I achieved now stable OUT transfers (from the PC to the FPGA) with working throtling (when the FPGA consumes data slower than the host delivers).
The basics needed for this are implemented in the FPGA like handshaking with the FX2 and clock domain transistion from the Interface clock to the user defined system clock.
in the gpif_com_test.vhd is a message rom, containing a prepared answer message to generate an IN transfer. this is needed for the next step. |
nussgipfel |
5413d 02h |
/gecko3/trunk/GECKO3COM/gecko3com-fw/ |
| 17 |
killed a bug that caused unreliable out transfers. detection of a ongoing in transfer is malfunctioning. needs redesign. |
nussgipfel |
5414d 16h |
/gecko3/trunk/GECKO3COM/gecko3com-fw/ |
| 16 |
release candidate 3: 0.4rc3
fixed a bug in the get_capabilities function. was fixed before but it was back again...
removed one file from the build process, that shouldn't be in the subversion. |
nussgipfel |
5427d 21h |
/gecko3/trunk/GECKO3COM/gecko3com-fw/ |
| 15 |
this is the release of version 0.4rc2
we provide now the downloadable *.iic file of the current version in the repository at the convinient place
"gecko3com-fw/firmware/" |
nussgipfel |
5440d 22h |
/gecko3/trunk/GECKO3COM/gecko3com-fw/ |
| 13 |
included the gecko3com_0.31.tar.gz firmware package needed to initialize fresh produced boards without any
serial number or fpga type information.
fixed two bugs that were found during testing of the version 0.4-rc
- the GET_CAPABILITIES function in the usb_tmc module was using a wrong pointer and returned garbage
- the SLOT_ADRESS defines for the spi write functions were using constants only usable on the GECKO3main prototype
changed some other small stuff to avoid compiler warnings or clarifie some comments. |
nussgipfel |
5441d 00h |
/gecko3/trunk/GECKO3COM/gecko3com-fw/ |
| 9 |
First commit to the OC svn.
This is the release candidate for the GECKO3COM firmware version 0.4.
Included are all sources, scripts and helper tools.
Implemented functionality to this firmware version:
- FW upgrade through USB DFU class
- works as a USB TMC device (test and measurement class)
- handles all mandatory IEEE488 and SCPI commands
- fpga can be configured through USB
- two different fpga configuration files can be downloaded the the onboard memory
- loads one of these configuration files during power on
next step is to implement the transparent data communication between the USB host and the FPGA |
nussgipfel |
5472d 22h |
/gecko3/trunk/GECKO3COM/gecko3com-fw/ |
