<|{ame>
hello, when checking the code with verilator --lint-only, I get the following error
<|{ame>
%Error-TIMESCALEMOD: lasoc.v:86:7: Timescale missing on this module as other modules have it (IEEE 1800-2017 3.14.2.2)
<|{ame>
Is there any way to remove it?
<|{ame>
(I am using picosoc)
FabM has joined #yosys
Xark has quit [Ping timeout: 246 seconds]
Xark has joined #yosys
arogora has joined #yosys
killjoy has quit [Ping timeout: 268 seconds]
arogora is now known as killjoy
killjoy has joined #yosys
killjoy has quit [Changing host]
<lofty>
|{ame: verilator is parsing picosoc as systemverilog, but you should change it to parse it as verilog
schaeg has joined #yosys
kraiskil has joined #yosys
|{ame has quit [Quit: Client closed]
|{ame has joined #yosys
cr1901 has quit [Remote host closed the connection]
<|{ame>
lofty: thank you. I tried verilator --lint-only --default-language "1364-2005" --language "1364-2005" $(PROJECT).v but I still get the above error
cr1901 has joined #yosys
|{ame has quit [Quit: Client closed]
schaeg has quit [Quit: Konversation terminated!]
schaeg has joined #yosys
sugarbeet has quit [Ping timeout: 240 seconds]
sugarbeet has joined #yosys
sugarbeet has quit [Ping timeout: 240 seconds]
sugarbeet has joined #yosys
cr1901 has quit [Remote host closed the connection]
kraiskil has quit [Ping timeout: 246 seconds]
bjorkint0sh has joined #yosys
bjorkintosh has quit [Ping timeout: 265 seconds]
skipwich has quit [Quit: DISCONNECT]
skipwich has joined #yosys
cr1901 has joined #yosys
cr1901 has quit [Remote host closed the connection]
cr1901 has joined #yosys
cr1901 has quit [Remote host closed the connection]
so-offish has joined #yosys
FabM has quit [Remote host closed the connection]
citypw has quit [Ping timeout: 240 seconds]
cr1901 has joined #yosys
cr1901 has quit [Remote host closed the connection]
cr1901 has joined #yosys
SpaceCoaster has quit [Ping timeout: 240 seconds]
SpaceCoaster has joined #yosys
ec has quit [Ping timeout: 240 seconds]
ec has joined #yosys
<so-offish>
ERROR: syntax error, unexpected TOK_ID <- Is there a way to get Yosys to give me what token it's ingesting that's causing the problem, or more information?
bjorkint0sh has quit [Ping timeout: 248 seconds]
bjorkintosh has joined #yosys
bjorkintosh has joined #yosys
<whitequark>
not as far as I know; the official recommendation is to run your code through something like verilator first
<whitequark>
(ideally the Verilog parser would be improved, but no one who has seen the code wants to do that)
Klotz has joined #yosys
Klotz has quit [Quit: Klotz]
kraiskil has joined #yosys
kraiskil has quit [Ping timeout: 256 seconds]
<so-offish>
whitequark: Oh that's an excellent idea; I'll work that into my workflow