Then use it from the USB CDC code so we can set baudrate, stopbits etc over USB.

So my idea is to have a errors.h file with base defines per module and then in each module have custom error codes using the base + 1, 2, 3, etc. This way each module gets unique errors :)

https://github.com/kbeckmann/xildebug/blob/fe7ccd1fc2e7b4f892d373cbefc386ada887a9ee/app/drivers/mcp4018t.c#L6

What voltage does the test value set and the default value as well, if we have a 1.8V device connected and we restart xildebug, what if it sets the voltage to 5V or something. Would be bad.

Also regarding the API, maybe instead of set_value we should have set_voltage, easier to understand.

https://github.com/kbeckmann/xildebug/blob/fe7ccd1fc2e7b4f892d373cbefc386ada887a9ee/app/drivers/max14662.c#L19

Remember to toggle the analog switches using the max14662 driver.

Thinking if we should do this or not. If we do it, we can port easily to other hardware. Then again, it might just be an annoying abstraction. Thoughts?

Idea is to let our code call gpio_write() etc instead of calling HAL_GPIO_WritePin etc.

I messed up here a bit, sometimes i use something_set, other times it's set_something.

What should we use? something_set feels a bit more api-ish than set_something, right? @arturo182

Generate the serial number based on STM UID

If the client asks for 9600 baud, we should change to that etc.

Didn't you mean *p_val and not p_val[0].

Also we should check p_val for NULL.

Maybe this module should control the shunt switches too. Need feedback from ADC module.

We need to store calibration data in flash.

We could also store the last state such as voltage on the LDO, state of the analog switches etc.

Need to figure out which flash storage approach to use. Probably don't need a proper filesystem, but maybe something to reduce the wear of the flash.

Implement an uart bridge over usb with no data loss, lag or weird behaviour.

Should also support configuring baudrate, stop bits etc.

Add a simple CDC endpoint that can be used for:

• Configuring the unit
  • Set calibration data (todo: store in flash)
  • Set threshold values for the shunt switches
  • Toggle the MAX analog switch
  • Toggle VDD_DUT_EN
  • Toggle GPIOs
  • ...
• Running production tests
• Stream ADC data
• ...

Not sure how much energy we should spend on this but it kinda sucks to do

if (r != ERR_OK)
	while (1) ;

We don't need to do fancy ram dumping and so on, but just halt the cpu and perhaps disable interrupts and that we get a central point where we can set a breakpoint when debugging.