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...
Add support for the following in the input hexfiles:
* Horizontal whitespace (space, tab, cr)
* Multiple words on the same line
* Empty lines
* Embedded underscores (_) in the words
* x and z nibbles (interpreted as zero)
In addition, allow for the to_hexfile to be shorter than the
from_hexfile, padding with zeroes as needed.
used in $(PREFIX)/share/ to install the chip database. This provides a
mechanism to choose a directory different than icebox (default).
I.e. fpga-icestorm/chipdb for Debian.
correct LDLIBS and CFLAGS for Mac OS X.
This attempts to detect the correct version of the FTDI headers and
sets the correct CFLAGS for the version of the FTDI headers installed.
Cleaned up Makefile and removed verbose checking of FTDI version.
Cleaned up Makefile and removed verbose checking of uname.
The fix will check to see if you are compiling on Mac OS X and set the
correct LDLIBS and CFLAGS for Mac OS X.
This attempts to detect the correct version of the FTDI headers and
sets the correct CFLAGS for the version of the FTDI headers installed.