Skip to content
This repository has been archived by the owner on Jan 28, 2022. It is now read-only.

Add a developer operation mode #231

Closed
wayfarer003 opened this issue Aug 22, 2019 · 9 comments
Closed

Add a developer operation mode #231

wayfarer003 opened this issue Aug 22, 2019 · 9 comments
Labels
enhancement New feature or request feature request Feature request

Comments

@wayfarer003
Copy link

On the physical hardware a couple of issues came up when running with partial hardware

  • Without a battery at 0 charge the battery charge screen can not be dismissed
  • With a battery but running on a bench power supply the 100% charge screen can not be dismissed. This requires turning off the bench supply in order to use the remote (forces battery usage)

A developer mode could have the follow features

  • disabled the battery charging screen to allow for partial HW configurations and bench power
  • Always enable WiFi to allow for uploading code, system access
  • console logging to LCD panel
  • remote serial logging
  • Other "things" that would not normally be used by a typical user
@martonborzak martonborzak added enhancement New feature or request feature request Feature request labels Aug 22, 2019
@zehnm
Copy link
Member

zehnm commented Oct 14, 2019

This is on my TODO list as well :-)
Any preferences or ideas on how to activate developer mode? My thoughts so far:

  • control file on /boot partition (Fat partition, mountable on any OS)
  • switching config.txt and cmdline.txt on /boot partition (required to disable DPI display and use HDMI)
  • configuration file
  • specific button presses on boot enters developer mode

@martonborzak
Copy link
Member

Thanks @zehnm ! :)

I think the developer mode is more useful when you're running the app on your PC or Mac.
You can run the code from Qt on the actual hardware and see all the console output on your host machine.

@martonborzak
Copy link
Member

I think an option could be to select the dev mode on the remote and then it reboots into it. It's hard to detect button presses at boot, because you have to wait for the driver to load.

@martonborzak martonborzak added this to Backlog in YIO Remote software via automation Nov 26, 2019
@martonborzak
Copy link
Member

I think this will be solved with #346. What do you think @zehnm ?

@zehnm
Copy link
Member

zehnm commented Jan 3, 2020

The hardware abstraction is not related to a developer mode. Certain things might be easier to reconfigure though.

@martonborzak
Copy link
Member

Is there still a need for this mode? What do you think @zehnm ?
We have mock hardware things, so the app can run on any device without getting error messages for battery gauge, etc.

@wayfarer003
Copy link
Author

After checking back into the project after some time. If it is fairly simple to change modes / behavior without this feature then it would be ok in my mind to close or back burner this request.

@zehnm
Copy link
Member

zehnm commented Jun 4, 2020

@martonborzak I think we can close this issue, especially with all the new configuration options.
The "real developer image" is covered in YIO-Remote/remote-os#11 which will add USB, other displays (e.g. Pimoroni Hyperpixel) and whatever seems required to play around with remote-software on a regular RPi.

@martonborzak
Copy link
Member

Great, I'm closing this issue then.

YIO Remote software automation moved this from Backlog to Done Jun 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request feature request Feature request
Projects
No open projects
Development

No branches or pull requests

3 participants