Modify the Firmware Configuration

Oct 13, 2025 by wbrum.org 131 views

Introduction

The SPI Add-On (ADS1256) is an experimental feature in the web configuration of a microcontroller board. However, users have reported that the Add-On does not stay enabled after a refresh or reboot of the page. This article aims to investigate the issue and provide a solution.

Expected Behavior

When turning on the ADS1256 Add-On in the web config, it should stay enabled after a reboot or a refresh. This is the expected behavior, and it is essential to understand how the Add-On should function.

Current Behavior

The ADS1256 Add-On will disable itself upon refreshing or rebooting the page. This is the current behavior, and it is the problem that needs to be addressed.

Context

The issue has been tested on both a Pico(clone) and a waveshare rp2040-zero. The user has tried to identify the cause of the problem by examining the data storage and the firmware configuration. However, the issue persists, and the user is seeking a solution.

Possible Causes

The user has considered several possible causes for the issue:

Data Storage: The user has examined the data storage mechanism and believes it may be related to the problem.
Firmware Configuration: The user has tried recompiling the firmware to force the Add-On to be enabled by default in the BoardConfig.h file. However, this approach has resulted in the Pico no longer booting.
SPI Implementation: The user has questioned the SPI implementation, wondering if it may be the cause of the issue.
WWW Stuff: The user has also considered the WWW implementation, but the browser console shows the data correctly when hitting save.

Steps to Reproduce

To reproduce the issue, follow these steps:

Go into Web Config
Make sure SPI is enabled
Enable ADS1256 Add-On and Save
Refresh page or Reboot
Add one will have now disabled itself

Screenshots & Files

The user has provided several screenshots and files to illustrate the issue:

Solution

To solve the issue, we need to identify the root cause of the problem. Based on the user's investigation, it appears that the issue may be related to the SPI implementation. However, further investigation is required to confirm this.

Possible Solutions

Here are some possible solutions to the issue:

Re-examine the SPI Implementation: The user should re-examine the SPI implementation to ensure it is correct and functioning as expected.
Modify the Firmware Configuration: The user may need to modify the firmware configuration to force the Add-On to be enabled by default.
Update the WWW Implementation: The user may need to update the WWW implementation to ensure it is correctly handling the data storage and retrieval.

Conclusion

The SPI Add-On (ADS1256) does not stay enabled upon refresh or reboot. The user has investigated the issue and considered several possible causes, including data storage, firmware configuration, SPI implementation, and WWW stuff. To solve the issue, we need to identify the root cause of the problem and implement a solution. Possible solutions include re-examining the SPI implementation, modifying the firmware configuration, and updating the WWW implementation.

Future Work

To further investigate the issue, the user should:

Re-examine the SPI Implementation: The user should re-examine the SPI implementation to ensure it is correct and functioning as expected.
Modify the Firmware Configuration: The user may need to modify the firmware configuration to force the Add-On to be enabled by default.
Update the WWW Implementation: The user may need to update the WWW implementation to ensure it is correctly handling the data storage and retrieval.

Introduction

Q: What is the expected behavior of the SPI Add-On (ADS1256)?

A: The expected behavior of the SPI Add-On (ADS1256) is that it should stay enabled after a reboot or a refresh of the page.

Q: What is the current behavior of the SPI Add-On (ADS1256)?

A: The current behavior of the SPI Add-On (ADS1256) is that it disables itself upon refreshing or rebooting the page.

Q: What are the possible causes of the issue?

A: The possible causes of the issue include:

Data Storage: The user has examined the data storage mechanism and believes it may be related to the problem.
Firmware Configuration: The user has tried recompiling the firmware to force the Add-On to be enabled by default in the BoardConfig.h file. However, this approach has resulted in the Pico no longer booting.
SPI Implementation: The user has questioned the SPI implementation, wondering if it may be the cause of the issue.
WWW Stuff: The user has also considered the WWW implementation, but the browser console shows the data correctly when hitting save.

Q: How can I reproduce the issue?

A: To reproduce the issue, follow these steps:

Go into Web Config
Make sure SPI is enabled
Enable ADS1256 Add-On and Save
Refresh page or Reboot
Add one will have now disabled itself

Q: What are the possible solutions to the issue?

A: The possible solutions to the issue include:

Re-examine the SPI Implementation: The user should re-examine the SPI implementation to ensure it is correct and functioning as expected.
Modify the Firmware Configuration: The user may need to modify the firmware configuration to force the Add-On to be enabled by default.
Update the WWW Implementation: The user may need to update the WWW implementation to ensure it is correctly handling the data storage and retrieval.

Q: How can I further investigate the issue?

A: To further investigate the issue, the user should:

Re-examine the SPI Implementation: The user should re-examine the SPI implementation to ensure it is correct and functioning as expected.
Modify the Firmware Configuration: The user may need to modify the firmware configuration to force the Add-On to be enabled by default.
Update the WWW Implementation: The user may need to update the WWW implementation to ensure it is correctly handling the data storage and retrieval.

Q: What are the next steps to resolve the issue?

A: The next steps to resolve the issue are to:

Identify the root cause of the problem: The user should identify the root cause of the problem and implement a solution.
Test the solution: The user should test the solution to ensure it resolves the issue.
Verify the solution: The user should verify the solution to ensure it is working as expected.

By following these steps, the user should be able to identify the root cause of the issue and implement a solution to enable the SPI Add-On (ADS1256) to stay enabled upon refresh or reboot.