New ypweb version

Added new version of ypweb (Literate Programming tool): 1.1a. This is the bugfix of 1.0a version. See http://code.google.com/p/ypweb/. Plans are to:

• add options to command (last pie "..; -h")
• add command line option -h, -h N -- show only N lines of source in doc
• add command ";; ..." -- means hide other lines of source in doc until next "..."
• add option to prev. command ";; ...; -l 10" - hide after 10 lines
• add jumping to tag definition (use ctags) (apart processing doc/src?)
• add unittests

LM3S9B92 and FreeRTOS example

Usual all developers starts with example of Web-server on FreeRTOS for this board. But always it does not work: Ethernet link is lost. How to cure it?

First, download last version of FreeRTOS (I tryed FreeRTOSv7.0.2.exe archive). Then unpack it. You can cut unnecessary folders from Demo folder: all except "Common" and "CORTEX_LM3Sxxxx_Eclipse".

Then download Yagarto GNU toolchain (I used yagarto-bu-2.21_gcc-4.6.0-c-c++_nl-1.19.0_gdb-7.2_eabi_20110429) and install it.

Then open main.c in "Demo\CORTEX_LM3Sxxxx_Eclipse\RTOSDemo" and change prvSetupHardware() function to:

void prvSetupHardware(void)
{
 SysCtlClockSet(SYSCTL_SYSDIV_4 | SYSCTL_USE_PLL | SYSCTL_OSC_MAIN | SYSCTL_XTAL_16MHZ);
 SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOF);
 GPIODirModeSet(GPIO_PORTF_BASE, (GPIO_PIN_2 | GPIO_PIN_3), GPIO_DIR_MODE_HW);
 GPIOPadConfigSet(GPIO_PORTF_BASE, (GPIO_PIN_2 | GPIO_PIN_3 ), GPIO_STRENGTH_2MA, GPIO_PIN_TYPE_STD);
 vParTestInitialise();
}

After it call make in console (Makefile is near main.c :). And now program RTOSDemo.bin into your chip with LM Flash Programmer tool. MAC address of the device should be set. Now reboot MCU and try to ping it - default IP address is 172.25.218.19. You can set static IP of your PC to 172.25.218.10/255.255.0.0 for this reason. And don't forget to disconnect your WiFi :)

There are pong packets! Now try to open in the Web browser http://172.25.218.19 - page will be refresh after 1 second and tasks will be shown.
Thanks to yingxin huang and it's help here.

Hanged LM3S9B92 board

After trying FreeRTOS example for LM3S9B92 my board seems "hanged" (dead) - no response over Ethernet, no adventure game :) And I get message "Error to initializing target".
Last was cured by several turning on/off USB connector. But no game... :) And Finder can not find my board's IP...
After opening Putty on virtual COM port (created after installation of FTDI drivers - I'm talking about Windows:) with baudrate 115200 and reseting board by button on the board, I see message:

Colossal Cave Adventure
-----------------------
Connect to either the USB virtual COM port or
telnet into the Ethernet port in order to play.

MAC Address Not Programmed!

Aha! I ran LM Flash Programmer and on "Other Utilities" tab and:

1. Reset device by "Debug port unlock" feature (select "Tempest Class", click "Unlock" and follow instructions on message boxes)
2. Switch to "MAC Address Mode" and programmed MAC address (it's possible to use FF-...-FF).
3. Re-program device by original firmware (always save original firmwares!)

After this reseting device show in Putty session:

Colossal Cave Adventure
-----------------------
Connect to either the USB virtual COM port or
telnet into the Ethernet port in order to play.

IP: 169.254.3.0
Netmask: 255.255.0.0
Gateway: 0.0.0.0

...after "Wait..." and obtaining IP address. Finder found this IP address, and colossal game is working... over Ethernet :)

ypweb literate programming tool

After I tried LP technique, I decided that it help me to understand my code better and cuts many possible errors. But I need easier tool, lesser verbose... I implemented very lightweight Python 3 tool (about 20Kb) and called it ypweb. It's hosted on Google.
Main differences with other LP tools are:

• produces only reStructuredText output
• very lightweight (only one Python 3 file) about 20Kb
• doesn't need comment line symbols for document strings (like #!) and code-chunks: only plain text
• document and code context are switched by special line with short variants
• generated index contains used by user (not predefined) classifiers
• doesn't allow code-chunks "placeholders" (defining in one place/inserting in another)
• supports any input and output charsets (see -h)

Short example:

  1 | Some definitions (macroses) used in COM module:
  2 | ;; x.h; defs; COM definitions
  3 | ;; Port number
  4 | #define PORT 1
  5 | ;; Baudrate
  6 | #define BAUD 9600
  7 | ;; funs; open()
  8 | int open(char *name, char *mode);
  9 | ;;
 10 | Another doc strings...
 11 | ;; x.c; funs; open()
 12 | code of open function here...
 13 | ;; x.h; defs; XXX
 14 | #define XXX
 15 | ;;
 16 | docs strings again...

Line 1 is the document chunk (file may starts with any chunk: doc or code). Line 2 is the special kind of line which switch context to code and begins with special marker (;;) and consists of 3 parts (may be lesser) splited by ;. Both symbols (;; and ;) may be changed to another in command line. It "says": next chunk is code, generates x.h file with some definitions ("defs" but may be any word preferred by user) and is the "COM definitions". These fields will be used also in index generating.

Line 3 is short form of switch-context-line (only caption, no file name or classifier). Line 4 is code and will be saved in the source file. Line 4 is like line 3, next is source line again...

Line 7 is short switch-context-line too and consists of classifier and caption, no filename, so will be saved in the same file - x.h.

Line 9 is empty switch-context-line, so it ends code chunk, nothing else. Next is always doc chunk.
Line 11 is switch-context-line which starts new source file: x.c. Line 13 begins code chunk for early created x.h file. Well, switch-context-line switch into code chunk and defines what is the code if not empty, empty - switches into doc chunk.

It's very clean and simple format. And is the reStructuredText too. So, you can use in it any kind of usual reSt markup!

After processing this file, .rst file and x.h, x.c will be generated. Also .rst file will have index section in the end with references to definitions of the code chunks.