Task tables and the application entry point

IoT Modules Development tools
1

The UART sample uses the tasks defininition table in accordance with the adl User Guide, which is great because I have been able to read and understand the sample as intended.

But many samples seem to have an implicit entry point of adl_main and no task table definitions, which I cannot find documented anywhere (adl user guide). In fact the documentation states that if no tasks are declared then the Firmware will refuse to launch the application, which doesn’t appear to be the case in practice. Since I am nervous about using undocumented features, can anyone shed any light on this ? Am I looking at the wrong documents ?

2

That was, in fact, the original way that Open-AT worked before they introduced the “Multitasking” stuff.

That’s becuase it is not documented! :angry:

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

As the old saying goes, there are only 3 things wrong with Open-AT:

  1. Documentation;
  2. Documentation;
  3. Documentation.

:unamused:

3

Thanks awneil, a very interesting and informative link. Everything I needed to know. Apologies for missing it in my first pass through the forum.

J