08:37 <ryan-summers[m]> jordens: Is there a special openocd configuration needed for firmware bringup? I'm not seeing any of the stm32h7 openocd config files in the openocd configuration folders

08:48 <ryan-summers[m]> * jordens: Is there a special openocd configuration needed for Stabilizer firmware bringup? I'm not seeing any of the stm32h7 openocd config files in the openocd configuration folders

09:00 <mtrbot-ml> [mattermost] <hartytp> @rjo any thoughts re the phaser noise eater implementation quote we discussed?

09:01 <mtrbot-ml> [mattermost] <hartytp> @rjo what's your pipeline looking like? Assuming Greg's guys get you hardware soon, what timeline are we looking at for RF out of Phaser? Is it likely we'll be able to get something faster than the 12 weeks on the quote?

09:11 <rjo> ryan-summers: might require a recent openocd: from stabilizer.cfg: https://github.com/ntfreak/openocd/blob/master/tcl/target/stm32h7x_dual_bank.cfg

09:19 <rjo> hartytp: I'd like to do this differently this time. Let's start with you writing down a robust specification of what is required. Take su-servo or the Sayma/SAWG servo description as a background. I'd like to avoid a couple of the iterations where I have to determine what you need.

09:20 <mtrbot-ml> [mattermost] <hartytp> ok. We did a bit of that in a previous chat and I had the impression that you had what you needed, but I'm happy to write some more detailed notes up as a starting point

09:22 <rjo> hartytp: let's stick with the 12 week timeline for the Phaser implementation for now. There might be something earlier for characterization but it will be incomplete.

09:22 <mtrbot-ml> [mattermost] <hartytp> ok

09:36 <mtrbot-ml> [mattermost] <sb10q> but behavior is different between the two boards or not?

15:31 <mtrbot-ml> [mattermost] <astro> @hartytp did you start testing the thermostat v2 firmware? I just want to make sure I'm not missing out on your feedback.

15:32 <mtrbot-ml> [mattermost] <hartytp> no not yet

15:32 <mtrbot-ml> [mattermost] <hartytp> I wasn't aware that the FW was ready for us to test

15:32 <mtrbot-ml> [mattermost] <astro> oh, sorry for not communicating that clearly

15:32 <mtrbot-ml> [mattermost] <hartytp> that's fine

15:33 <mtrbot-ml> [mattermost] <hartytp> in terms of development process, I think it's probably most efficient for you to setup a test rig where you can test the basic functionality yourself

15:33 <mtrbot-ml> [mattermost] <hartytp> I'm not expecting you to verify hw performance or anything like that but IME it's inefficient all round if we test each bit of code as you write it

15:33 <mtrbot-ml> [mattermost] <hartytp> feedback loop bandwidth is too low

15:34 <mtrbot-ml> [mattermost] <hartytp> is there anything you're blocked on?

15:34 <mtrbot-ml> [mattermost] <hartytp> is there any aspect of the code that you don't know how to test using your setup?

15:34 <mtrbot-ml> [mattermost] <astro> ok, can do, but remember than I'm no expert in the domain

15:34 <mtrbot-ml> [mattermost] <hartytp> absolutely

15:34 <mtrbot-ml> [mattermost] <hartytp> that's why I'm here to help!

15:35 <mtrbot-ml> [mattermost] <hartytp> IMHO the best way of doing this is to break the required functionality down into small pieces (program the DAC Iset etc)

15:35 <mtrbot-ml> [mattermost] <hartytp> for any piece feel free to ask me what's required or anything you don't know (register values)

15:35 <mtrbot-ml> [mattermost] <hartytp> and how to verify performance/what to expect

15:36 <mtrbot-ml> [mattermost] <hartytp> e.g. for the Iset DAC the DAC output goes to an ADC

15:36 <mtrbot-ml> [mattermost] <hartytp> so it's worth getting the ADC up and running (we need it for the TEC offset calibration anyway)

15:37 <mtrbot-ml> [mattermost] <hartytp> the TEC driver reference also goes to the ADC so we can start by reading that and checking that it's 1.5V as specified by the data sheet. That would be a good next step AFAICT

15:48 <mtrbot-ml> [mattermost] <astro> I'm not yet sure what ADC input to expect from our current lab setup

16:06 <mtrbot-ml> [mattermost] <hartytp> ok

16:06 <mtrbot-ml> [mattermost] <hartytp> sec while I find the schematics

16:06 <mtrbot-ml> [mattermost] <hartytp> do you have them?

16:07 <mtrbot-ml> [mattermost] <hartytp> regardless of the setup (i.e. the external connections) the TEC driver produces a 1.5V reference on pin 4

16:10 <mtrbot-ml> [mattermost] <hartytp> from the BD on page 10 of the MAX1968 datasheet it looks like the REF is enabled even when the chip is shutdown, but I couldn't be 100% sure about that without measuring

16:11 <mtrbot-ml> [mattermost] <astro> yes, I open them in the altium online viewer

16:12 <mtrbot-ml> [mattermost] <hartytp> cool (there is also a PDF in the releases page)

16:13 <mtrbot-ml> [mattermost] <hartytp> on schematic page 7 (in the pdf) you can see the microprocessor connections

16:13 <mtrbot-ml> [mattermost] <hartytp> TEC 0 vref goes to PA0

16:14 <mtrbot-ml> [mattermost] <hartytp> TEC1 vref goes to PA3

16:16 <mtrbot-ml> [mattermost] <hartytp> The CPU ADC ref looks to be 3V0 driven by an OpAmp (5V0 and then a potential divider)

16:16 <mtrbot-ml> [mattermost] <hartytp> (R87 and R88)

16:17 <mtrbot-ml> [mattermost] <astro> I am still searching for the link to that PDF...

16:17 <mtrbot-ml> [mattermost] <astro> which file?

16:17 <mtrbot-ml> [mattermost] <hartytp> So I'd try reading those two ADC channels out (in the long run there are a few other channels you may find useful during debugging, but that would be a good start)

16:17 <mtrbot-ml> [mattermost] <hartytp> https://github.com/sinara-hw/thermostat/releases

16:17 <mtrbot-ml> [mattermost] <hartytp> Thermostat.Standalone.PDF

16:17 <mtrbot-ml> [mattermost] <hartytp>

16:17 <mtrbot-ml> [mattermost] <hartytp> (not the most obvious naming I admit)

16:18 <mtrbot-ml> [mattermost] <astro> oh, I was looking at my git checkout :)

16:18 <mtrbot-ml> [mattermost] <hartytp> yeah, the PDFs are huge so we publish them as releases rather than putting then in VC

16:19 <mtrbot-ml> [mattermost] <astro> ok, I'll see what I can do with these pins...

16:21 <mtrbot-ml> [mattermost] <astro> thank you

17:05 <mtrbot-ml> [mattermost] <hartytp> Cool! Let me know how you get on. Might be worth checking those are within spec (roughly defined by the ref accuracy and the accuracy of the adc ref divider) as part of BST