Currently comment on runout sensor configuration says:

• By default the firmware assumes HIGH=FILAMENT PRESENT.

which is quite confusing and not very informative for regular user. As we test filament sensor status by M119 command It should clearly say when filament present on M119 we should see either "open" or "TRIGGERED" status and we can flip FIL_RUNOUT_INVERTING otherwise. Nobody really

Expected behavior

During firmware configuration
Should be easy to select the value for LUA_FLASH_STORE in user_config.h
Options and/or units should be clearly documented so that the setting can be used.

Actual behavior

current default setting is:
//#define LUA_FLASH_STORE 0x10000

Comments

0x10000 corresponds to 64kb in hex, What are the other possibl

Solutions

1. Convert INO files to CPP

2. Manual prototype declaration

#ifdef DO_NOT_USE
typedef int32_t delaytype;
void thisShouldNotAppearInTheBinary(delaytype timer); // aded manually
void thisShouldNotAppearInTheBinary(delaytype timer) {
  delay(timer);
}
#endif

Is your feature request related to a problem? Please describe.

ref #1864 , there needs to be a concise way to check that utility functions (brightness calculation, channel setting, value conversion etc.) work without problems with some set of expected inputs and outputs.

Describe the solution you'd like

• special build option to replace application code with bunch of assert calls. i

• I'm submitting a ...

  • Bug report
  • Feature request
  • Translation

• Do you want to request a feature or report a bug?

  • Feature

• What is the current behavior?
  Doesn't have this feature as far as i know.

• What is the expected behavior?
  I request a function of the Ralim firmware that enables either at start-up or through a menu opti

Minor bug, but in the RT-AC3100 on the Dual WAN page here: http://192.168.1.1/Advanced_WANPort_Content.asp

The link is dead for Dual WAN FAQ, it leads here: https://www.asus.com/support/FAQ/1011718

The correct link should be: https://www.asus.com/support/FAQ/1011719/

Mongoose OS only currently supports running ESP32 on single core, basically leaving the second core completely unused.

Yes i've seen the thread at:
https://forum.mongoose-os.com/index.php?p=/discussion/comment/2356/#Comment_2356

And ticket #253

I opened this issue as technically this is an issue that only single core devices are supported, and multi-core devices that are supported .

The .rtf files in BaseTools/UserManuals in the edk2 tree still tell users to "Report bugs to edk2-buildtools-devel@lists.sourceforge.net". Since we no longer use the sourceforge mailing lists we should update those files.

Due to the revamp of the runtime in libtock-rs to use futures, we are currently pinned at an old version of libtock-rs (https://github.com/tock/libtock-rs/tree/ab2c945184b98ecae3e70ac678e9f5231deef73b).

However, the core part of libtock-rs has now been split out of the drivers: https://github.com/tock/libtock-rs/tree/master/core. We can update to depend on that to keep in sync with upstream, wh

I am trying to add additional IEs to the beacon/probe resp frames on a PI 3B+ using nexmon. I'm having difficulty understanding how these frames get configured.

I gather the frames come in from hostapd into cfg80211.c, which pulls out selected IEs and passes them from the brcmfmac driver, using string commands like arp_ol and ndoe, across an interface (dbus?) to the firmware, which reassembles

If using timers while flying (rather than telemetry - battery usage etc.) you may need various timers for the various batteries you use. Sometimes, you might forget and use the wrong one (ask me how I know :( ) It would be useful to be able to adjust the current value of the timer up or down.

model.incrementTimer(timer, value)
Increment/decrement model timer parameters

Parameters
tim

Hi all,

Sorry if my questions look too simple but there still things I do not understand:

GPG keys:
Is there any GPG keys compatibility list? Is the Nitrokey U2F compatible with heads?
Is specificaly this key: https://docs.puri.sm/PureBoot/Heads.html compatible?
Is there any limitation or keys that are know not working with heads?

OTP apps:
Is there only google code app how

• Enable page programming/ sector erase option.
• Under reset vs. normal connection
• Check for multiple rom and ram regions.
• Board ids (dynamically changing, by script or by code).
• Auto-reset and other rom settings.

OS: Ubuntu 18.04.02 LTS

The error occures because on line 86 rsync fails to expand the asterisk. Works as intended on Debian 10.

An attempt to port LinuxBoot to the Dell E7420 mentions that there are no guidelines for which DXE modules are necessary to retain, which can be discarded etc.

We should document that.

We should document the messaging protocol a bit better, with basics and a few example messages.
Also that it uses 8400 not 115... as the baud rate on both usarts.

EasyAVR has very poor developer documentation. We should at least comment the code.

I followed the steps shown here and I got the following error.

Maybe I did something wrong, but in this case there should be a proper error message telling me what I did wrong.