https://open-source-silicon.dev
Join Slack
Hello all, I have made a submission for GFMPW-0 and the project is failing tapeout job. The issue up...
# gf180mcu
a
Hello all, I have made a submission for GFMPW-0 and the project is failing tapeout job. The issue upon inspecting the logs is that during the gds to oas conversion the error occurs of "unknown format" for the generated gds file. I have tried to open the said gds file (caravel_<id>.gds) with klayout but it gives the same issue. What could be the possible reason for this error and how can it be fixed?? Is there any file missing in my submission which is causing this issue??
v
is precheck passed at the time of submission or not?
still I see this message 
"Tapeout for this shuttle is not available at this time. It will be enabled in the future
for tapeout job
t
@Abdul Moiz Sheikh: It sounds like the GDS file is corrupted. If, in Linux, you type 
file caravel_<id>.gds
, what does it say? Is it a compressed format file that has been overwritten with the 
.gds
extension?
a
@Tim Edwards I inspected the log files for the tapeout job which ran on the efabless server. In the gds to oas log file there was an error saying the unknown format. I have not tried the file command but I tried opening the said gds with klayout and it showed the same error of unknown format
@Vijayan Krishnan the tapeout jobs and prechecks (for some projects) are being run by the efabless organizers I dont know if participants can run it themselves
@Tim Edwards running the file command returns the result that the file is empty
g
probably something is going wrong in 
make ship
- between using mag files from submission repos rather the gds and/or the magic FDs issue - https://open-source-silicon.slack.com/archives/C016G7Z8GDR/p1670861702358219?thread_ts=1670845449.468939&amp;cid=C016G7Z8GDR but this very much for efabless to worry about, and as they haven't said anything about tapeout being final at this stage I'd not worry either
a
@gatecat I guess so... I was worried that I might have made an error during design or uploading design which I did not want to carry over.
t
Have you checked the size of the .gds? I got the same error on the conversion, but it ended up being because the gds was 0 bytes. The error was actually somewhere else, causing it to write an empty gds.
a
@Tholin where was the error??
My gds is also shown as 0 bytes
t
ship_truck.log
a
Ther is an error here, says "failure to read entire subtree of cells." There is an I/O error in writing the gds file and file is hence not written.
Is this due to design being too large or lack of memory ??
g
This might be the problem that 
make ship
seems to be wrongly using the .mag view inside of the submission repo instead of the .gds as would be expected - it's still early days for tapeout jobs so I hope this will be fixed....
(of my projects that passed tapeout, I never bothered committing an updated .mag as only the gds should matter, so the tapeout job has ended up running on the example project...)
v
@jeffdi fyi
a
@gatecat hope this is fixed
Open in Slack
PreviousNext
Powered by

What is Linen?

Linen is a search-engine friendly community platform. We offer integrations with existing Slack/Discord communities and make those conversations Google-searchable.

Powered by