icestorm/icepack, branch main

Update Claire's name and fix the reference image in the iceprog help

2025-06-03T09:06:08+00:00

icebram,icepack: use correct format specifiers for size

2024-06-21T21:36:34+00:00

For printing `size_t` the format specifier `%lu` was used in the code. However, `%lu` is used to print `unsigned long`. The correct format specifier for `size_t` is `%zu`, so let's use that.

Add more build products to .gitignore.

2021-03-05T12:43:57+00:00

icepack: show program name in usage.

2020-06-24T19:57:22+00:00

Cleanup FpgaConfig::write_cram_pbm tile_type initialization

2020-04-22T16:05:12+00:00

Signed-off-by: Claire Wolf

Merge pull request #242 from The6P4C/master

2020-04-22T16:01:58+00:00

icepack: Fix Windows-only stack overflow in CRAM pbm generation (fixe…

Support custom PROGRAM_PREFIX

2020-04-10T08:05:17+00:00

icepack: Fix Windows-only stack overflow in CRAM pbm generation (fixes #241)

2019-12-08T13:52:05+00:00

On Windows, attempting to generate a netpbm image of the CRAM with `icepack -b` causes the tool to crash after writing only the netpbm header due to a stack overflow. The bug did not appear on Linux. This was traced to a large stack-allocated variable length array (`tile_type`) inside `FpgaConfig::write_cram_pbm`. For an 8k ice40 with 4 banks, `cram_width = 872` and `cram_height = 272` the `tile_type` array ends up at `4 * 872 * 272 * sizeof(uint32_t) =` 3794944 bytes, or about 3.6 MiB. The fix replaces the large stack VLA with an array of 4 (bank) 2D C++ vectors, moving the large amount of data to the heap. Even though the fix is not in a Windows-specific code path (and hence applies to all platforms), I think it's wise to eliminate such a large stack allocation entirely. The fix has been tested working on both Windows and an Ubuntu WSL install.

Fix typo

2019-09-13T10:55:48+00:00

Signed-off-by: Clifford Wolf

Only write bram data to ASCII output if bram data is present, fixes #228

2019-08-08T15:02:44+00:00

Signed-off-by: Clifford Wolf