<cr1901_modern>
which one? Admittedly I lost a few hours a few days ago trying to figure out whether mspdebug supports remote detach (it doesn't- there's a config file option to restart the gdb server on kill) because I didn't read the manual.
<_whitenotifier>
[m-labs/nmigen-boards] whitequark pushed 1 commit to de10_nano [+1/-0/±0] https://git.io/JeO5V
<Dar1us>
cr1901_modern: The Ti dongle, mspdebug and Code Composer seem to do it
<cr1901_modern>
the PCB shaped like a rocket?
<Dar1us>
I didn't get past "this is janky and annoying so I need to put the kid gloves on"
<Dar1us>
no, the blck silicone(?) Ti debugger
<Dar1us>
custom VHF power amplifier is the debugee
<_whitenotifier>
[m-labs/nmigen-boards] whitequark pushed 1 commit to de10_nano [+0/-0/±1] https://git.io/JeO5o
<_whitenotifier>
[m-labs/nmigen-boards] whitequark e77daf8 - numato_mimas: SW* are actually buttons.
<mtrbot-ml>
[mattermost] <sb10q> yeah in hindsight I should have definitely gotten a PoE switch with controllable port, because of course embedded devices always fuck up and need power cycles etc.
<cr1901_modern>
Dar1us: Huh, less than $50 on AliExpress, not bad at all
<cr1901_modern>
Can an injector be used when the port that leads to the switch already is using the Ethernet lines for power w/o destroying the device?
<cr1901_modern>
(since the m-labs switch supports PoE)
<cr1901_modern>
w/o destroying the injector*
<Dar1us>
cr1901_modern: I assume the inject is capacitively coupled to the switch side but probably worth checking I suppose...
harryho has quit [Ping timeout: 245 seconds]
sb0 has quit [Ping timeout: 265 seconds]
mtrbot-ml has quit [Ping timeout: 276 seconds]
harryho has joined #m-labs
sb0 has joined #m-labs
mtrbot-ml has joined #m-labs
<zignig>
if it is a reasonable capable switch , you should be able to switch the poe for a port on and off with a snmp write?
<zignig>
what brand is it ?
* zignig
had to reboot a POE device from time to time a few years ago.
<mtrbot-ml>
[mattermost] <sb10q> not sure if that's a real issue or not
<mtrbot-ml>
[mattermost] <sb10q> was it printing it already with the ST-Link?
mauz555 has quit [Read error: Connection reset by peer]
mauz555 has joined #m-labs
mauz555 has quit [Ping timeout: 264 seconds]
mauz555 has joined #m-labs
mauz555 has quit [Read error: Connection reset by peer]
<mtrbot-ml>
[mattermost] <pathfinder49> pathfinder49 joined the team.
sb0 has quit [Quit: Leaving]
<mtrbot-ml>
[mattermost] <pathfinder49> Hi, I'm working with @hartytp on thermostat. Thanks to the new build guide I got the board flashed. However, I'm unsure whether two behaviors I'm seeing are expected. Firstly, the initial read of the ADC is corrupted. Further reads return the correct ID (see here https://pastebin.com/kJ0vQ3Ka). Secondly, the MAC address is read as invalid (see here https://pastebin.com/THDZjj4A).
plonk has quit [Ping timeout: 246 seconds]
plonk has joined #m-labs
plonk has quit [Ping timeout: 240 seconds]
lkcl has quit [Ping timeout: 276 seconds]
<mtrbot-ml>
[mattermost] <pathfinder49> @astro can you have a look at the current command parser implementation plz?
<mtrbot-ml>
[mattermost] <pathfinder49> e.g. it's a little confusing that "report\n" gives "Command error: Parser (Tag)\n" (not a helpful error msg)
<mtrbot-ml>
[mattermost] <pathfinder49> so one has to send "report \n"
<mtrbot-ml>
[mattermost] <pathfinder49> can you check the reg map plz?
<mtrbot-ml>
[mattermost] <pathfinder49> @astro what is the tick duration? (units of time?)
<mtrbot-ml>
[mattermost] <astro> @pathfinder49 tick as in systick? 10 Hz. but `board::systick::get_time()` evaluates the systick registers to produce sub-ms precision
<mtrbot-ml>
[mattermost] <astro> @pathfinder49 sorry for the command parser bugs, I was not able to test during the last few days but I will hopefully be able to do so today.
<mtrbot-ml>
[mattermost] <astro> @pathfinder49 firmware startup reads the ADC ID in a loop til it's correct *because* of the first read that is always corrupted. I should probably silence the output. (semihosting output must be removed prior to production anyway)
<mtrbot-ml>
[mattermost] <hartytp> Bit for buffers etc
<mtrbot-ml>
[mattermost] <hartytp> What’s the units of the time for the reporting?
rohitksingh has quit [Ping timeout: 245 seconds]
rohitksingh has joined #m-labs
<mtrbot-ml>
[mattermost] <hartytp> @astro see data sheet for bits of setup reg the top word but offsets are not right
<mtrbot-ml>
[mattermost] <astro> units are nanoseconds
<mtrbot-ml>
[mattermost] <hartytp> Ack thanks that’s what I guessed (but can you document at some point)
<mtrbot-ml>
[mattermost] <hartytp> Can you expose the post filter sample rate on the eth interface plz? Allows users to trade off noise rejection for loop be
<mtrbot-ml>
[mattermost] <hartytp> Bw
<mtrbot-ml>
[mattermost] <hartytp> @astro nb your ADC is prob operating out of spec so may play up due to wrong diode on supply (@sb10q can you fix)
<mtrbot-ml>
[mattermost] <hartytp> @pathfinder49 can you see if the ADC error still happens now we fixed the rail voltage?
<mtrbot-ml>
[mattermost] <astro> @hartytp I just pushed a fix for the wrong SetupCon bits
<mtrbot-ml>
[mattermost] <astro> please wish for any configuration bits you would like to control :)
<mtrbot-ml>
[mattermost] <hartytp> Still not right I think
<mtrbot-ml>
[mattermost] <hartytp> Well I’m also happy to add once the fw is finished, it’s not a big deal
<mtrbot-ml>
[mattermost] <hartytp> Nope sorry
<mtrbot-ml>
[mattermost] <hartytp> You’re right this time, I most remembered
<mtrbot-ml>
[mattermost] <hartytp> Misremembered
<mtrbot-ml>
[mattermost] <astro> good
<mtrbot-ml>
[mattermost] <astro> thank you for verifying
<mtrbot-ml>
[mattermost] <hartytp> Np nice to see working. Want to take a few more Adc measurements then will look at pwm
<mtrbot-ml>
[mattermost] <hartytp> These adcs are basically magic though
<mtrbot-ml>
[mattermost] <astro> how so?
<mtrbot-ml>
[mattermost] <hartytp> 10nK rms noise in such a cheap package. That’s pretty cool.
<mtrbot-ml>
[mattermost] <hartytp> Shows how much you can do with a good front end and a lot of dsp
<mtrbot-ml>
[mattermost] <hartytp> Also unlike lots of ics I’ve used they are easy to configure, default to sensible values and kind of “just work”
<mtrbot-ml>
[mattermost] <hartytp> I’m pleasantly surprised we can stick that ADC so close to a dirty Poe smps, microprocessor etc and still hit sub uV noise floor
<mtrbot-ml>
[mattermost] <astro> yeah, that chip is a vanilla SPI peripheral indeed :)
<mtrbot-ml>
[mattermost] <hartytp> Yep let’s see what cranking the tec driver to 11 does to the ADC readings
mumptai has quit [Remote host closed the connection]
<mtrbot-ml>
[mattermost] <hartytp> Also the 18bit dac on the new version is cool too
<mtrbot-ml>
[mattermost] <astro> how do I handle that there are two inputs? do we want separate PID instances that control different PWM channels?
rohitksingh has quit [Ping timeout: 245 seconds]
rohitksingh has joined #m-labs
<mtrbot-ml>
[mattermost] <hartytp> You need two different integrators, sets of gains etc
<mtrbot-ml>
[mattermost] <hartytp> @astro any idea why our board doesn’t pick up a MAC address from the eeprom? Does this work for you?
gnufan_home has joined #m-labs
<mtrbot-ml>
[mattermost] <astro> I haven't touched any of the ethernet setup code from ionpak
<mtrbot-ml>
[mattermost] <astro> @hartytp any differences in the hardware?
rohitksingh has quit [Ping timeout: 246 seconds]
<mtrbot-ml>
[mattermost] <astro> oh, `ff-ff-ff-ff-ff-ff` here as well
<mtrbot-ml>
[mattermost] <hartytp> Okay good to know. Not a prob for now I guess
<mtrbot-ml>
[mattermost] <hartytp> Would have to check schematic connections I guess
<mtrbot-ml>
[mattermost] <astro> it should be wired to pins that are valid for `tm4c129x::FLASH_CTRL`
<mtrbot-ml>
[mattermost] <astro> I'm still getting `sens0=FFFFFF` and `sens1=FFFFFF` with the fixed buffer bits
<mtrbot-ml>
[mattermost] <hartytp> Okay well let’s forget about the eeprom for now but make sure it’s connected properly in the next hw rev
<mtrbot-ml>
[mattermost] <hartytp> Re the ADC. I think you have two issues: (a) the ADC is running off the wrong rail because of the zener
<mtrbot-ml>
[mattermost] <hartytp> (B) you need to add a load resistor
<mtrbot-ml>
[mattermost] <hartytp> If you don’t have a resistor then the inputs are tied to vref and gnd so you expect to read fs
<mtrbot-ml>
[mattermost] <hartytp> @sb10q can you stick 10ks in the shutter cons plz?
cedric has quit [Ping timeout: 265 seconds]
cedric has joined #m-labs
cedric has quit [Changing host]
cedric has joined #m-labs
<mtrbot-ml>
[mattermost] <hartytp> @astro oh and let’s remove the odr write since it doesn’t do anything with the postfilter