diff options
| author | Mihály Horváth <hermitsoft@users.noreply.github.com> | 2017-03-05 22:25:47 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-03-05 22:25:47 +0100 |
| commit | fdf863b791ac3b09345e59456185d07589b9bbaa (patch) | |
| tree | 80cab540be488dc4ee8c8313233de6795cbdebde /README | |
| parent | 7ea1726fcc07b5320af48a37ec1397c6935dd49a (diff) | |
| download | icestorm-fdf863b791ac3b09345e59456185d07589b9bbaa.tar.gz icestorm-fdf863b791ac3b09345e59456185d07589b9bbaa.tar.bz2 icestorm-fdf863b791ac3b09345e59456185d07589b9bbaa.zip | |
LP384 support in icepack (tested on real chip)
LP384 is now supported in icepack, it was fairly easy to realize as only the main chip dimensions are required that could be found out from the .bin bitsream file generated by iCEcube.
Tested by creating .asc then packing it back to .bin. The testcase is just a simple LED on/off on a port though but that shows geometries are fine.
Now I'm trying to have and support chipdb-384.txt hopefully with some help from the authors and anyone who already knows the internals of IceStorm well. I need info, how to reverse-engineer iCE40 chips the easiest way. Scripts maybe.
I'm trying to reach my goal in any way coz iCEcube sucks and IceStorm integrates well into commandline...
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions