- Posts: 959
- Thank you received: 489
Please Log in or Create an account to join the conversation.
Hi cakeslob,
I think that maintaining the JSON config file format would be the more straight forward approach. Less to rework on the firmware side. The JSON parsing and module loading would not need to be modified, just where the JSON file is being fetched from . This could be from the EEPROM for example.
But how to get it over to the board? I'll need to investigate how to send a text file via SPI. For Ethernet I'd need to establish a TCP connection I think.
For the NVEM board I'm working on it would be neat to be able to send over the config to allow for customisation by the user. It's currently hard coded at the moment, which would be ok for 99% of people.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
HI,cakeslob Thank you very much for your help, I have tried the relevant content of octopus pro 429 and it works well.new Skr2 with stm32f429vgt works with octopus pro 429 firmware and regular skr2 config , so same old skr2 but with 180mhz
i set up uart pins for octopus to use tft connector same as skr2 for consistency
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.