Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added firmware version to local UI #35 #43

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

keerats7
Copy link

@keerats7 keerats7 commented Aug 25, 2023

There might be a better way to organize these changes, let me know any suggestions!

@keerats7
Copy link
Author

I also updated the README.md based on my experience setting up.

  1. It appears to me that to get to flashing mode, I have to specifically release the reset button before the boot button, not at the same time or the other way around. Can others confirm this is true?
  2. I specified that lights turn off when in flashing mode. Combined with the problem from 1, a few times I thought I was in flashing mode when really I wasn't.
  3. I specified that the device name is variable and how to find it. I was confused because I didn't see "/dev/ttyACM0" in my output.

@@ -43,6 +45,7 @@
CONFIG_GOLIOTH_USER,
CONFIG_GOLIOTH_PASSWORD,
CONFIG_GOLIOTH_OTA_ENABLED,
CONFIG_GOLIOTH_FIRMWARE_VERSION,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this makes sense as a config key. These are meant for things that can be set from the outside.

Maybe add the version to /api/sensors instead?

Copy link
Author

@keerats7 keerats7 Aug 28, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @damz , that makes more sense. I pushed that change.

@@ -57,13 +57,18 @@ $ make build

Connect the esp32 board to your computer using the USBC connection port on the esp32 and a cable that will connect to your computer.

Press and hold the "boot" button then press the "reset" button and release both at the same time (shown below). This puts the esp32 into a flashing mode.
Press and hold the "boot" button, then press and release the "reset" button, then release the "boot" button (shown below). This puts the esp32 into a flashing mode. If done correctly, the lights should turn off.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That last part is not technically true. I have the same experience that the CHG LED tends to flicker in normal mode, and to be solid off in DFU mode, but it is not actually designed to do that.

The CHG LED flickers because it has no battery connected to it. It is not clear why it stops when entering DFU mode, but in any case, with a charged battery connected it would be off in both cases.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah ok. Is there any other reliable indicator of when it's in DFU mode?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @keerats7 ! As it mentions above, you will see the sensor power lights turn off. The device will also enumerate differently to the system. Something like ttymodem etc instead of frogsensor.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @keenanjohnson , based on @damz comment it seems the CHG LED on the ESP32 may turn off, but that's unrelated to it being in DFU mode. Are you saying the green sensor lights will always turn off when in DFU mode? If so I can add that distinction that specifically the sensor lights will turn off.

@damz
Copy link
Contributor

damz commented Aug 25, 2023

It appears to me that to get to flashing mode, I have to specifically release the reset button before the boot button, not at the same time or the other way around. Can others confirm this is true?

This is correct. You need the boot button to be pressed when you release the reset button. So the safest process is what you describe: press reset, press boot, release reset, release boot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants