There are a few flags that currently don't have proper error checking. The ones I found are -gc, -scheduler and -size. Using the wrong value will lead to no or unexpected errors.

I think the best way to handle it is to add a new method to compileopts.Config that checks whether there are any faulty flags, which is then called from the main function.

Hello,

I would like to know where I can find (apart from reading the headers), if possible, any documentation on how to use the stlink library ?

Thank you very much in advance.

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 .

If you grab the header here:

It will scale down to the center of the monitor, and the cursor stays where you grabbed it, but AvalonStudio won't be at the cursor:

Expected

Hello! In my current project, I use ESP32 and display with ILI9341. I would like to use your library, but - as a beginner - I have a lot of trouble with that. Is there somewhere documentation that describes the operation of all library functions? Eg: tft.drawString (.....) has four parameters, but what? What is the text datum? ...
Of course, I will laboriously find explanations in the examp

packBEAM should be also implemented in Erlang, so it can be integrated into existing Erlang and Elixir tooling in a easier way.

In the file dps-model.h you mention:
you can see real ADC value in CLI mode's stat:

Is the documentation on how to use it available anywhere specifically for this firmware?

uint16_t readChannel(Channel channel)

According to docs.modm.io

typedef uint8_t 	Channel
// this type may also be an enum or enum class 

the call readChannel(1) should be legal, but: error: cannot convert 'int' to 'modm::platform::Adc1::Channel'.

We should up

add extra command line option parsing to add/remove/show routes.

The pages of the reference targets in the knowledge base are missing a lot of details, such as:

• what nF APIs are available in the pre-built images (this is already mentioned in the home page)
• what is exposed/configured (ADC, PWM, etc)
• floating point support
• memory available: heap for managed apps and deploy area size

These are linked from [here](http://docs.nanoframework.net/articl