wafer.space Community - TQVA & HZ80

8:20 a.m.

https://wafer.space/ws-run1-cob/TQVA/2026-09-20/index.html

8:21 a.m.

https://wafer.space/ws-run1-cob/HZ80/2026-09-20/index.html

8:21 a.m.

@Lauri - Those two, right?

yes

What shape is the TQVA? Is that the one quarter slot?

8:23 a.m.

TQVA TinyQV - Crowdsourced Risc-V SoC 0p5x0p5 A Risc-V RV32EC SoC with peripherals from the Tiny Tapeout Risc-V competition. This version uses a quarter sized slot. https://github.com/MichaelBell/ws01-tinyQV

GitHub - MichaelBell/ws01-tinyQV: TinyQV for Wafer Space run 1 on g...

TinyQV for Wafer Space run 1 on gf180mcu. Contribute to MichaelBell/ws01-tinyQV development by creating an account on GitHub.

8:25 a.m.

The HZ80 page says 0p5x1 -- but the TQVA page doesn't say 0p5x0p5?

There was one HZ80 that failed. I inspected it and the bond looked okau. So I resoldered failed bonds connector pin. After this it passed. (these restests are visible in the raw json in gh)

8:25 a.m.

TQVA - 0.5x0.5 HZ80 - 0.5x1

@Leo Moser (mole99) - Do we publish some type of manifest / inventory type json for a run?

8:27 a.m.

@Lauri

Tim 'mithro' Ansell

@Leo Moser (mole99) - Do we publish some type of manifest / inventory type json for a run?

Not exactly sure what you mean by that? We do have the manifest.csv for each run. It contains a number of things such as the slot size for each project.

@Leo Moser (mole99) - I was wondering if we had something that Lauri could use to populate the cob output web pages with a bit of extra details & links without having to think about it at all?

These are currently all the keys we have in our manifest: CODE,PROJECT,SLOT_SIZE,TOP,SHA256,LAYOUT,VISIBILITY,PROJECT_DETAILS,REPOSITORY

8:55 a.m.

The reticle stitcher does not mind additional keys

8:55 a.m.

Also, the precheck generates a render of the layout that could be displayed

Tim 'mithro' Ansell

The HZ80 page says 0p5x1 -- but the TQVA page doesn't say 0p5x0p5?

It's because this die uses custom TQVA PCB. It's not generic 0.5x0.5

9:01 a.m.

I actually have a repo that renders the dies (for bonding diagrams) and already thought about using these renders for the results page as well. Just haven't gotten around to updating the results page. Should add camera photos as well

Leo Moser (mole99)

These are currently all the keys we have in our manifest: CODE,PROJECT,SLOT_SIZE,TOP,SHA256,LAYOUT,VISIBILITY,PROJECT_DETAILS,REPOSITORY

@Leo Moser (mole99) Could this (public) information be included in the ws-run1 repo? (i think the manifest you're referring to is private?)

@Leo Moser (mole99) - It doesn't seem to be in the https://github.com/wafer-space/ws-run1 repo?

GitHub - wafer-space/ws-run1: wafer.space GF180MCU Run 1

wafer.space GF180MCU Run 1. Contribute to wafer-space/ws-run1 development by creating an account on GitHub.

10:31 a.m.

@Leo Moser (mole99) - But I could also be blind

We cannot publish the full manifest which includes information about the private projects. I could push the manifest for the public ones, but all the information is already in the Readme.

10:49 a.m.

@Lauri you should be able to get the manifest directly from the server. I can also send it to you tomorrow morning.

@Leo Moser (mole99) - Could we publish a redacted .csv / .json file with the same info at the README so people don't have to pull it back out of the README table?

Lauri

I actually have a repo that renders the dies (for bonding diagrams) and already thought about using these renders for the results page as well. Just haven't gotten around to updating the results page. Should add camera photos as well

Made a test version that uses die renders instead of generic box. imo generic box is better, less distracting

(edited)

Tim 'mithro' Ansell

@Leo Moser (mole99) - Could we publish a redacted .csv / .json file with the same info at the README so people don't have to pull it back out of the README table?

Yes, this would be great

@Lauri You can now find the public manifests for ws-run #1 and #2 here:

1

Leo Moser (mole99)

@Lauri You can now find the public manifests for ws-run #1 and #2 here:

@Leo Moser (mole99) - Do you think it makes sense to include the private ones in the same way as you do in the README.md ?