Undocumented: adl_main, wm_apmCustomStackSize

[awneil]

In the old days, before “multitasking” was introduced, an Open-AT application had a single entry point - adl_main() - and a single stack-size variable - wm_apmCustomStackSize

See: viewtopic.php?f=78&t=4351&p=17411&hilit=adl_main#p17411

Since “multitasking” was introduced, these are undocumented although they are still supported and, in fact, required for a single-task application in the “classic” style.

Many of the samples still use them.

The documentation of these needs to be reistated in the ADL User Guide - and it needs to be made clear how the system decides whether to use an adl_InitTasks Table or an adl_main() function for its entry point(s).

See: viewtopic.php?f=3&t=3567&p=13610&hilit=adl_main+adl_InitTasks#p13610

[awneil]

@awneil

Many of the samples still use them.

They still do.

Single-Task (“Classic”) samples using IRQs define the following:

@DTMF Decode

const u16 wm_apmCustomStackSize = 4096*3;
const u32 wm_apmIRQLowLevelStackSize = 4096;
const u32 wm_apmIRQHighLevelStackSize = 4096;

But the ADL User Guide speaks only of

adl_InitIRQLowLevelStackSize
adl_InitIRQHighLevelStackSize

Also, adl_main() in a “Classic”, single-task application takes the InitType as a parameter, but task entry points in a multi-task application take no parameters.

This really needs to be properly explained

See also: viewtopic.php?f=108&t=4943&start=0