-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to verify basic blinky on iCESugar-nano #484
Comments
Can you build and verify the example iCESugar_1_5/Blinky?
Type this in an empty directory and it will copy the project files. Then
try apio build and apio verify and see if they work.
apio examples -f iCESugar_1_5/Blinky
On my system (mac) I get this (with apio Version: 0.9.5):
$ apio verify
iverilog -B "/Users/user/.apio/packages/tools-oss-cad-suite/lib/ivl" -o
hardware.out -D VCD_OUTPUT=dummy_vcd_output -D NO_ICE40_DEFAULT_ASSIGNMENTS
"/Users/user/.apio/packages/tools-oss-cad-suite/share/yosys/ice40/cells_sim.v"
blink.v
===============================================================================
[*SUCCESS*] Took 0.11 seconds
BTW, the command 'apio verify' is going to be deprecated and replaced by
'apio lint'.
…On Mon, Dec 2, 2024 at 7:57 PM Offbeat ***@***.***> wrote:
I'm trying to follow Introduction to FPGA Part 2 - Getting Started with
Yosys, IceStorm, and Apio | Digi-Key Electronics
<https://www.youtube.com/watch?v=gtkQ84Euyww&ab_channel=DigiKey> however
I'm using the latest version of apio, 0.9.5 as well as Python 3.11.7 with
an iCESugar-nano dev board. I'm trying to hold the yellow LED high on the
board, which is on pin B6. my icesugar.pcf file looks like this:
# For the iCESugar Board (iCE40UP5K-QFN48)
set_io D1 B6
my apio.ini file:
[env]
board = iCESugar-nano
top-module = blink_test
and my blink.v file:
module blink_test (
output D1
);
assign D1 = 1'b1;
endmodule
when I call apio verify I get this in return
C:\Users\henry\Desktop\FPGA_Practice\test1\iCESugar_1_5\Blinky>apio verify
iverilog -o hardware.out -D VCD_OUTPUT=dummy_vcd_output -D NO_ICE40_DEFAULT_ASSIGNMENTS "C:\Users\henry\.apio\packages\tools-oss-cad-suite\share\yosys/ice40/cells_sim.v" blink.v
scons: *** [hardware.out] Error 1
================================================ [ ERROR ] Took 0.21 seconds ================================================
C:\Users\henry\Desktop\FPGA_Practice\test1\iCESugar_1_5\Blinky>
I'm not sure how to interpret this error
—
Reply to this email directly, view it on GitHub
<#484>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQVMQPPYXEBTGMSZ54YB5L2DUT25AVCNFSM6AAAAABS42MJSWVHI2DSMVQWIX3LMV43ASLTON2WKOZSG4YTGOJSGM3DQMQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I was not able to reproduce on my win 10 machine. This below is a log of what I did and attached is a zip with the project directory. Please try to unzip this project and see you can build or verify.
|
I attempted to build and verify the blink apio example iCESugar_1_5/Blinky this is the result:
I also downloaded your example project zip, unzipped it and tried to build to no avail. The only obvious difference between our setups is that you're using python 3.12 and I'm using 3.11.7, though I don't think this is the source of the issue. Here's the results of building the example project
|
I reinstalled apio from scratch and tried the project in the zip file I sent you. BTW, that was fixed in the ongoing apio dev version (next apio release) and This is how I reinstalled apio from scratch
My results with the project in the zip file
|
The issue was fixed and will be included in next release. Closing. |
I'm trying to follow Introduction to FPGA Part 2 - Getting Started with Yosys, IceStorm, and Apio | Digi-Key Electronics however I'm using the latest version of apio, 0.9.5 as well as Python 3.11.7 with an iCESugar-nano dev board. I'm trying to hold the yellow LED high on the board, which is on pin B6. my icesugar.pcf file looks like this:
my apio.ini file:
and my blink.v file:
when I call
apio verify
I get this in returnI'm not sure how to interpret this error
The text was updated successfully, but these errors were encountered: