Hello, all files in src/rtos are sparse in comments and were are checked in as nearly complete files into git. This hides their evolution. I can't find an API definition for the needed functions in struct rtos_type or a definition of the meaning of the return values neither, beside deciphering that 0 probably mean success.
This makes it hard to start adding NutOs as another microcontroller OS (www.ethernut.de). I have experience with the STM32 part there, but the inner working of the thread management I need to decipher together with what OpenOcd needs to know about NutOs to recognise as Os What about providing a minimal set of src/rtos files for some dummy OS, providing empty functions to start with, but working in the context of openocd? Do I miss some docs? Anybody willing to enhance the docs with me? Thanks -- Uwe Bonnes b...@elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ---------- ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
