01:32 <harryho> Astro-_ : Do you need a full power cycling on the zc706 now?

03:46 <whitequark> harryho: sorry, I somehow missed your message about Adapter, I'll take a look soon

03:46 <whitequark> as for CSR reset, I think they should normally be reset together with the peripheral

04:20 <mtrbot-ml> [mattermost] <harryho> whitequark: Do you mean a reset on the busses should not affect the values that are already written to the CSR?

04:31 <nmg-questions> Regarding nmigen: Is it fair to run `python setup.py test` in the main directory and expect all the tests to pass? If so, I notice that tests regarding the FIFO fail. I am going to bisect a little bit and see where they started failing/

04:32 <nmg-questions> I couldn't quite tell from the travis run that these are actually being run

04:40 <whitequark> harryho: yes, the CSR bus reset should not actually reset the registers themselves

04:40 <whitequark> peripherals can have state that is intertwined with the state in CSRs so those two should be reset together

04:40 <whitequark> of course, in practice, usually you would have one global reset in a design that resets the CPU, the peripherals, and the CSRs all at once

04:41 <whitequark> nmg-questions: FIFO tests pass both here and on CI

04:44 <sb0> Astro-_: I have power cycled the zc706

04:44 <sb0> let me test

04:45 <sb0> I'm not sure if the rustc pinning really worked?

04:45 <mtrbot-ml> [mattermost] <harryho> whitequark: Thanks! I think my latest code would satisfy that. I'll make a detailed doc soon.

04:45 <sb0> shell.nix just does "builtins.fetchTarball https://github.com/mozilla/nixpkgs-mozilla/archive/master.tar.gz", which is not stable

04:47 <_whitenotifier-f> [smoltcp] whitequark closed pull request #312: dhcp:max message size option - https://git.io/JeEP0

04:47 <_whitenotifier-f> [m-labs/smoltcp] whitequark pushed 1 commit to master [+0/-0/±2] https://git.io/JeaPf

04:47 <_whitenotifier-f> [m-labs/smoltcp] MabezDev 8eb01ac - Add suppor for DHCP maximum message size option.

04:49 <nmg-questions> whitequark: Hmm, Could it be a yosys version error? https://pastebin.com/s2Vk0Gjd

04:53 <nmg-questions> whitequark: My yosys version: Yosys 0.9+932 (git sha1 5110a34d, clang 7.0.1-8 -fPIC -Os)I also have 11 cases, all of them FIFOFormalCase related

04:53 <cr1901_modern> nmg-questions: You need to install an SMT solver

04:54 <cr1901_modern>  No such file or directory: 'yices-smt2': 'yices-smt2'

04:55 <nmg-questions> ok. let me look around for that. I got past installing sby :) ... Thanks cr1901_modern

04:56 <_whitenotifier-f> [smoltcp] Success. The Travis CI build passed - https://travis-ci.org/m-labs/smoltcp/builds/608563484?utm_source=github_status&utm_medium=notification

05:04 <nmg-questions> All good on my side for now

05:13 <sb0> Astro-_: ping is working fine now

05:13 <sb0> well done!

05:15 <sb0> large packets also work

08:20 <_whitenotifier-f> [m-labs/nmigen] whitequark pushed 1 commit to master [+0/-0/±2] https://git.io/JeaM7

08:20 <_whitenotifier-f> [m-labs/nmigen] whitequark 9749c70 - hdl.ir: lower domains before resolving hierarchy conflicts.

08:20 <_whitenotifier-f> [nmigen] whitequark closed issue #265: Multiple ResetSynchronizers don't seem to work - https://git.io/Je2L1

08:37 <_whitenotifier-f> [nmigen] Success. The Travis CI build passed - https://travis-ci.org/m-labs/nmigen/builds/608615782?utm_source=github_status&utm_medium=notification

08:37 <_whitenotifier-f> [nmigen] Success. 82.07% (+0%) compared to e988778 - https://codecov.io/gh/m-labs/nmigen/commit/9749c70730f7859eb26af61e9abdb1cb5c78be97

08:37 <_whitenotifier-f> [nmigen] Success. 100% of diff hit (target 82.07%) - https://codecov.io/gh/m-labs/nmigen/commit/9749c70730f7859eb26af61e9abdb1cb5c78be97

09:42 <mtrbot-ml> [mattermost] <hartytp> @astro great!

09:42 <mtrbot-ml> [mattermost] <hartytp> What are the remaining items to get artiq up and running? What’s left that looks high risk?

09:43 <mtrbot-ml> [mattermost] <sb10q> stress the inter-core communication code and check that nothing funny is happening

09:43 <mtrbot-ml> [mattermost] <sb10q> remaining steps, there are a lot

09:43 <mtrbot-ml> [mattermost] <sb10q> but except for inter-core communication it's relatively standard stuff and should not be very risky

09:45 <mtrbot-ml> [mattermost] <hartytp> Cool! That’s really great

12:09 <Astro-_> that is incredibly great news

12:09 <Astro-_> because the device kept playing deaf last night

23:36 <mtrbot-ml> [mattermost] <pathfinder49> @astro What's the intended usage of the "pwm ch width total" command for Thermostat. My understanding is it should turn on the TEC with the corresponding current?