Friday, 2022-09-30

*** tpb <[email protected]> has joined #yosys00:00
*** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Ping timeout: 258 seconds)00:03
*** ec <ec!~ec@gateway/tor-sasl/ec> has joined #yosys00:05
mewtIs there a way to add some -chparam within synth_ice40's hierarchy pass?00:31
mewtOr do you need to split it out00:31
loftymewt: just run hierarchy before synth_ice4001:34
mewtah that should have worked then01:36
mewtThe rerun won't blow it away?01:36
mewt(I think I saw some way to just run a subset of synth_ice40 so I guess absolute worst case I can do read_verilog; hierarchy blablabla; proc; then run the rest of synth_ice40...maybe01:38
mewt)01:38
*** pbsds <[email protected]> has quit IRC (Ping timeout: 252 seconds)04:18
*** FabM <FabM!~FabM@2a03:d604:103:600:2e60:8c7c:e8fb:7990> has joined #yosys06:10
*** zxrom <[email protected]> has joined #yosys07:13
RowanG[m]Is it possible to do some kind of "safe" OTA using an ECP5 + open source toolchain? I want to deploy some ECP5 modules which are connected via ethernet. I want to implement an update procedure. Basically I want to have multiple images in the flash. One "bootloader" bitstream that first boots which can then manually be instructed to load the second image. If the second bitstream doesn't do something within some period of time the FPGA should09:42
RowanG[m]be reset so it returns to the bootloader. 09:42
RowanG[m]Is this at all possible with an ECP5? 09:42
tntWell you can't do the "auto-reset" in the FPGA, you'd need some external watchdog for that.09:54
tntBut for the rest, yes, this seems doable.09:54
aggI guess you could have a separate logic circuit in your design that needs to be turned off by the main design and eventually triggers reset if not (you'd need to wire a gpio to the programn pin to trigger the reset)? the ecp5 can automatically reset to a 'golden' image if the main image fails to load at all, too, so hopefully between the two you'd be covered12:11
*** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Ping timeout: 258 seconds)12:52
*** ec <ec!~ec@gateway/tor-sasl/ec> has joined #yosys12:53
*** Sarayan <Sarayan!~galibert@2a01:e0a:1d7:77e0:beae:c5ff:fee3:518f> has quit IRC (Ping timeout: 244 seconds)13:56
*** zxrom <[email protected]> has left #yosys (Leaving)14:03
*** FabM <FabM!~FabM@armadeus/team/FabM> has quit IRC (Quit: Leaving)15:53
*** Sarayan <Sarayan!~galibert@2a01:e0a:1d7:77e0:beae:c5ff:fee3:518f> has joined #yosys16:05
*** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Ping timeout: 258 seconds)17:31
*** ec <ec!~ec@gateway/tor-sasl/ec> has joined #yosys17:31
*** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Remote host closed the connection)18:21
*** ec <ec!~ec@gateway/tor-sasl/ec> has joined #yosys18:24
*** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Ping timeout: 258 seconds)19:09
*** philtor <[email protected]> has quit IRC (Ping timeout: 244 seconds)19:09
*** ec <ec!~ec@gateway/tor-sasl/ec> has joined #yosys19:12
*** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Remote host closed the connection)19:21
*** ec <ec!~ec@gateway/tor-sasl/ec> has joined #yosys19:21
*** philtom <[email protected]> has joined #yosys19:37
*** philtom is now known as philtor19:38
*** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Ping timeout: 258 seconds)20:28
*** ec <ec!~ec@gateway/tor-sasl/ec> has joined #yosys20:30
*** nonchip <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)22:04
*** nonchip <[email protected]> has joined #yosys22:04
*** nelgau_ <[email protected]> has quit IRC (Remote host closed the connection)22:55
*** nelgau <[email protected]> has joined #yosys22:56

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!