poleguy looking for lost toolsMaking it match the sim.
Clock shows one clock between last data transition and rising edge of we_n, scope shows two.
Getting closer!
Start rtl counter with a timer that is initialized 10 seconds from a 32bit wrap point so that the software handling of wrap-around is well exercised during development.
#rtl #fpga #verilog #vhdl #xilinx #alchitry #eureka #protonpack #software #softwaredevelopment #hardware #embedded #fensterFreitag
I cleaned up a bunch of the vis code.
Added trigger settings buttons, status messages, and forward/reverse triggering.
Save settings in a json file automatically now.
Started capturing with all telemetry turned on.
It seems like the test_counter is getting corrupted on these captures.
It's not clear where in the pipeline this is happening.
Time to debug.
I contributed to the #FPGA, #Modem, #PCB design, impedance detection, portable telemetry and lots of the testing for this project.
I'm still supporting it, and will be likely until I die or am fired. It seems people like it!
#shure #NAMM #AxientDigital #PSM #IEM #protonpack #proaudio #livesound
@jaseg @azonenberg I was recently reminded that I still need to make sure I have a "go-to" async fifo, and vet what I currently have in my #protonpack project.
@azonenberg I just started reading through your manual:
https://www.ngscopeclient.org/downloads/ngscopeclient-manual.pdf
I'm seriously considering connecting my #protonpack telemetry system to it to see how it goes. I have my own visualization and triggering system in python/matplotlib that works quite well, but I don't see why I can't do the same thing with ngscopeclient.
Hmm..
I feel like there must be a better xkcd for this scenario than this one, isn't there?
To be continued on Monday!
4/n
Oh, I've got a story tonight. Oh what a classic:
When I blew up my Alchitry Pt #FPGA board back in November, I ordered two more and took a break on the #protonpack project. When I got back to it two weeks ago. I put it together wrong.
I had put in the Ft+ instead of the regular Ft board.
And I damaged the coax.
Tonight I found and fixed the damaged coax and could see good data flowing again. A relief, but I still wasn't getting good data over the FT600 USB interface.
1/n
Working on the #protonpack again.
I'm now getting lots of packets with no errors.
The cause for the errors I've been seeing was fun...
@geerlingguy I have bookmarked this. I am going to need usec level synchronization across multiple devices for my "#protonpack" telemetry work.
But I first need to get the first device working reliably.