1d8c9ca224
gw: Start testing peak detector, and fix a bug!
2023-05-27 10:36:42 -06:00
f6d3868273
re-arrange things and start a simple test manager
2023-05-13 09:49:58 -06:00
2faf509506
gw: implement sampler controller with peak detector
...
Mostly untested, will need testing with simulated waveforms to validate
correctness.
2023-05-07 15:15:18 -06:00
c887cd135c
hw: update README for new revision
2023-05-07 10:54:09 -06:00
fe4fb11f7e
hw: fix DRC issues, export Rev B
2023-05-07 10:48:03 -06:00
b330e5c447
Update to KiCAD 7 and fix most issues
2023-05-07 10:41:40 -06:00
40b88557d8
hw: update gitignore
2023-05-07 10:40:46 -06:00
3c94c3ed53
hw: create KiBOM config
2023-05-07 10:39:18 -06:00
39b5dd7193
gw: finish CDC sampler module
...
Just need to hook this into the FIFO I made before, and write all the
peak detection, triggering, and trigger enable logic, + hook everything
into a single wishbone address space.
2023-04-23 20:45:57 -06:00
0bf6c2336c
gw: finish testing sampler and fix a couple bugs
2023-04-23 20:08:17 -06:00
dc762bca8d
gw: start writing circular buffer
2023-04-23 19:46:23 -06:00
05fed9e28e
remove extra submodule I added for testing
2023-04-22 18:41:12 -06:00
5cfc562190
fixup fw
2023-04-22 18:39:59 -06:00
9dec411ff0
hw: Add a few more HW bugs found to the README
2023-04-22 18:39:40 -06:00
35a8841aa5
fw: update some drivers for LiteX
...
Still need to re-do some stuff and clean up, but it runs on LiteX now
2023-04-22 18:39:01 -06:00
c5db01c70f
gw: fix eth.py addressing issues
2023-04-22 18:38:26 -06:00
c0b293e0c7
gateware: move back to LiteX
...
Had too many issues with integrating LiteEth. I put my FW into a LiteX
SoC and it worked, so I migrated back. With the knowledge I gained doing
Amaranth I could fix the issues I had adding a wishbone slave device
pretty easily.
2023-04-22 18:35:13 -06:00
833db12d58
fw: make build script return with error code so it can be scripted
2023-04-22 17:41:51 -06:00
a864da5354
fw: eth testing and debug process
2023-04-22 13:39:32 -06:00
29ec5a8a43
tracking a couple files I missed
2023-04-16 11:06:02 -06:00
9b49f1184e
fw: more progress for ethernet, unable to read data
2023-04-15 22:43:52 -06:00
3b2af908c7
gw: get LiteEth working!
...
Link comes up! Not working fully, but that could be firmware too
2023-04-15 18:11:16 -06:00
1204be4fa0
fw: mostly implement smoltcp driver? unsure if it works
2023-04-15 17:06:59 -06:00
d207181ef5
gw: increase ROM size
2023-04-15 13:00:06 -06:00
005a053624
fw: testing and fix a couple blocking bugs!
2023-04-15 12:59:54 -06:00
b7b556f6d2
firmware: i2c work, not finished
2023-03-25 15:21:54 -06:00
60e468340c
gateware: make i2c actually read status bits
2023-03-25 15:21:35 -06:00
241cb72553
gateware: fix RAM and ROM issues
2023-03-25 15:21:03 -06:00
ac746a8c5a
firmware: add I2C
2023-03-24 20:54:59 -06:00
bf482e740d
firmware: add UART
2023-03-24 20:54:50 -06:00
a05af8739c
gateware: fix UART and connections
2023-03-24 20:54:05 -06:00
348f6d5ba6
gateware: fix sizing and add size configurability
2023-03-24 20:53:37 -06:00
96dabe013a
gateware: add UART to CSR
2023-03-24 17:42:27 -06:00
32fb8383d1
just create a local platforms folder instead of a forked amaranth_boards
2023-03-24 17:33:13 -06:00
f846cc1fab
gw: get i2c up and running (ish) in simulation
2023-03-21 20:09:04 -06:00
ea32a00b68
fw: write common read/write function
2023-03-05 19:37:54 -07:00
4e7c9984d7
add vscode settings to make rust-analyzer work
2023-03-05 19:19:45 -07:00
26389576d5
fw: first attempt at writing a packet
...
Unsure if this is working, not sure if I have the tools to even know if
it does.
I could spend the time to actually write the packet by hand, or I could
probably spend ~2x the time and get smoltcp up.
Either way, the HW is validated, I am bringing up a link, I can talk to
LiteEth, so past here is driver stuff
2023-03-05 12:58:18 -07:00
925a605af9
hw: revision A gerbers
2023-03-05 11:53:18 -07:00
fdf3ddeb4a
hw: added some notes on RevA bringup issues
2023-03-05 11:52:41 -07:00
54ac22429e
add jtagdap submodule for now
...
(need to update it to use amaranth to do debug in minerva)
2023-03-05 11:52:16 -07:00
6ef410786e
fw: moving forward a bit
2023-03-05 11:48:08 -07:00
cc763a3e9b
requirements.tx: amaranth-community-unofficial -> amaranth-farm
2023-03-05 11:47:09 -07:00
8d00e15835
gateware: fix dumb mistakes
...
Bus widths should now all be correct. (addresses and sizes in amaranth
take into account the granularity selection, so granularity acts like
two extra bits on the bus address line)
Also don't ignore a warning about undriven resets. Turns out that can
gate *everything* off in your design.
2023-03-05 11:43:59 -07:00
60b7b485da
fw: start janky ethernet bringup testing
2023-03-04 12:42:22 -07:00
a970a0154b
hardware: add some bringup notes for rev A
2023-03-04 12:42:15 -07:00
8b19464608
gateware: propogate MDIO signal correctly w/o IOBUF
...
This was causing my nextpnr crash. I really do need to figure out how to
do this in a less hacky way. Or even just make it more explicit that I
am doing this for a reason.
2023-03-04 12:41:16 -07:00
6e89c0d837
gateware: actually integrate ethernet
2023-03-04 10:54:43 -07:00
56d13a0e77
gateware: add PLL and generate two clocks
...
TODO is make a proper clock gen object, maybe it could run ecppll by
itself?
2023-02-25 12:56:09 -07:00
1b39199df3
gateware: generate PLL with 'ecppll'
2023-02-25 12:24:03 -07:00
