Johan Kanflo
Johan Kanflo
I am having a look into it right now. Will try all combinations of boot loader/app pre/post #176.
Bummer, reopening...
Weeeeell, this was a rather disappointing Sunday outing for me. I am using macOS which means a world of pain nowadays when it comes to serial devices. FTDI support is...
I got it going, sort of. I loose a bunch of frames from time to time which reminds me to stabilise the UART upgrade protocol, will open separate issue.
Using a logic analyser I see that the data Pyserial claims have been written never reaches the TX line. TX stops moving in the middle of a frame and is...
256 bytes works for me. I think I saw a number of buffer overruns in the code but need to look more carefully in the coming week.
Additionally, If I send a 512 byte frame I end up getting a ```SIGSEGV``` in ```memcpy(frame->buffer, data, status)``` called from ```uframe_extract_payload(...)``` on the reception of the 512 byte frame. Not...
I think SCPI would be very useful. The eez-open project is really cool and puts this side project of mine to shame ;)
For anyone wanting to add SCPI support, I can recommend [this library](https://github.com/j123b567/scpi-parser) by @j123b567.
Cool, looking forward to see the complete command set. Please try to follow the coding style so far. That is would be ``` static scpi_result_t dps_output_enable(scpi_t * context) { ......