summaryrefslogtreecommitdiffstats
path: root/nuttx/Documentation/NuttX.html
blob: 8fd164b88ab591279906dfc19db6a7e05cd64788 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
<html>
<head>
<title>NuttX</title>
</head>
<body background="backgd.gif">
<hr><hr>
<table width ="100%">
  <tr align="center" bgcolor="#e4e4e4">
    <td>
      <h1><big><font color="#3c34ec"><i>NuttX RTOS</i></font></big></h1>
      <p>Last Updated: August 25, 2012</p>
    </td>
  </tr>
</table>
<hr><hr>
<table width ="100%">
  <tr bgcolor="#e4e4e4">
    <td>
  <h1>Table of Contents</h1>
    </td>
  </tr>
</table>

<center><table width ="80%">
<tr>
<td>
<table>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#overview">Overview</a>.<br>
    What is NuttX?  Look at all those files and features... How can it be a tiny OS?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#group">NuttX Discussion Group</a>.<br>
    Do you want to talk about NuttX features?  Do you need some help?  Problems?  Bugs?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#downloads">Downloads</a>.<br>
    Where can I get NuttX?  What is the current development status?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#platforms">Supported Platforms</a>.<br>
    What target platforms has NuttX been ported to?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#environments">Development Environments</a>.<br>
    What kinds of host cross-development platforms can be used with NuttX?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#footprint">Memory Footprint</a>.<br>
    Just how big is it?  Do I have enough memory to use NuttX?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#licensing">Licensing</a>.<br>
    Are there any licensing restrictions for the use of NuttX? (Almost none)
    Will there be problems if I link my proprietary code with NuttX? (No)
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#history">Release History</a><br>
    What has changed in the last release of NuttX?
    What unreleased changes are pending in SVN?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#TODO">Bugs, Issues, <i>Things-To-Do</i></a>.<br>
    Software is never finished nor ever tested well enough.
    (Do you want to help develop NuttX?  If so, send me an email).
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#documentation">Other Documentation</a>.<br>
    What other NuttX documentation is available?
  </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td>
    <a href="#trademarks">Trademarks</a>.<br>
    Some of the words used in this document belong to other people.
  </td>
</tr>
</table>
</td>
</tr>
</table></center>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="overview"><h1>Overview</h1></a>
  </td>
  </tr>
</table>

<p>
  <b>Goals</b>.
  NuttX is a real timed embedded operating system (RTOS).
  Its goals are:
<p>
<center><table width="90%">
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Small Footprint</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Usable in all but the tightest micro-controller environments,
      The focus is on the tiny-to-small, deeply embedded environment.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Rich Feature OS Set</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      The goal is to provide implementations of most standard POSIX OS interfaces
      to support a rich, multi-threaded development environment for deeply embedded
      processors.
    </p>
      NON-GOALS: (1) It is not a goal to provide the level of OS features like those provided by Linux.
      In order to work with smaller MCUs, small footprint must be more important than an extensive feature set.
      But standard compliance is more important than small footprint.
      Surely a smaller RTOS could be produced by ignoring standards.
      Think of NuttX is a tiny Linux work-alike with a much reduced feature set.
      (2) There is no MMU-based support for processes.
      At present, NuttX assumes a flat address space.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Highly Scalable</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Fully scalable from tiny (8-bit) to moderate embedded (32-bit).
      Scalability with rich feature set is accomplished with:
      Many tiny source files, link from static libraries, highly configurable, use of
      weak symbols when available.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Standards Compliance</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      NuttX strives to achieve a high degree of standards compliance.
      The primary governing standards are POSIX and ANSI standards.
      Additional standard APIs from Unix and other common RTOS's are
      adopted for functionality not available under these standards
      or for functionality that is not appropriate for the deeply-embedded
      RTOS (such as <code>fork()</code>).
    </p>
    <p>
      Because of this standards conformance, software developed under other
      standard OSs (such as Linux) should port easily to NuttX.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Real-Time</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Fully pre-emptible, fixed priority and round-robin scheduling.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Totally Open</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Non-restrictive BSD license.
    </p>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>GNU Toolchains</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Compatible GNU toolchains based on <a href="http://buildroot.uclibc.org/">buildroot</a>
      available for
      <a href="https://sourceforge.net/project/showfiles.php?group_id=189573&package_id=224585">download</a>
      to provide a complete development environment for many architectures.
    </p>
</tr>
</table></center>

<p>
  <b>Feature Set</b>.
  Key features of NuttX include:
<p>
<center><table width="90%">

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Standards Compliant Core Task Management</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Fully pre-emptible.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Naturally scalable.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Highly configurable.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        Easily extensible to new processor architectures, SoC architecture, or board architectures.
        A <a href="NuttXPortingGuide.html">Porting Guide</a> is available.
      </li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>FIFO and round-robin scheduling.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Realtime, deterministic, with support for priority inheritance</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>POSIX/ANSI-like task controls, named message queues, counting semaphores, clocks/timers, signals, pthreads, environment variables, filesystem.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>VxWorks-like task management and watchdog timers.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>BSD socket interface.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Extensions to manage pre-emption.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Inheritable &quot;controlling terminals&quot; and I/O re-direction.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>On-demand paging.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <li>System logging.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>May be built either as an open, flat embedded RTOS or as a separtely built, secure micro-kernel with a system call interface.</li>
    </p>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Well documented in the NuttX <a href="NuttXUserGuide.html">User Guide</a>.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>File system</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Tiny, in-memory, root pseudo-file-system.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Virtual file system supports drivers and mountpoints.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        Mount-able volumes.  Bind mountpoint, filesystem, and block device driver.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Generic system logging (SYSLOG) support.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        FAT12/16/32 filesystem support with optional FAT long file name support<small><sup>1</sup></small>.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        NFS Client. Client side support for a Network File System (NFS, version 3, UDP).
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        NXFFS. The tiny NuttX wear-leveling FLASH file system.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>ROMFS filesystem support.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li><a href="NuttXNxFlat.html">NXFLAT</a>.
      A new binary format call NXFLAT that can be used to 
      execute separately linked programs in place in a file system.
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p><small>
      <sup>1</sup>
      FAT long file name support may be subject to certain Microsoft patent restrictions if enabled.
      See the top-level <code>COPYING</code> file for details.
    </small></p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Device Drivers</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>Supports character and block drivers as well as specialized driver interfaces.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        Network, USB (host), USB (device), serial, CAN, ADC, DAC, PWM, Quadrature Encoder, and watchdog timer driver architectures.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        RAMDISK, pipes, FIFO, <code>/dev/null</code>, <code>/dev/zero</code>, and loop drivers.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Generic driver for SPI-based or SDIO-based MMC/SD/SDH cards.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li><a href="NuttXPortingGuide.html#pwrmgmt">Power management</a> sub-system.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>ModBus support provided by built-in <a href="http://freemodbus.berlios.de/">FreeModBus</a> version 1.5.0.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>C Library</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Fully integrated into the OS.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Networking</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>TCP/IP, UDP, ICMP, IGMPv2 (client) stacks.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>SLIP</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Small footprint (based on uIP).</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>BSD compatible socket layer.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Networking utilities (DHCP server and client, SMTP client, TELNET client, FTP server and client, TFTP client, HTTP server and client).  Inheritable TELNET sessions (as &quot;controlling terminal&quot;)</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        NFS Client. Client side support for a Network File System (NFS, version 3, UDP).
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
        A NuttX port of Jeff Poskanzer's <a href="http://acme.com/software/thttpd">THTTPD</a> HTTP server
        integrated with <a href="NuttXNxFlat.html">NXFLAT</a> to provide true, embedded CGI.
      </li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>FLASH Support</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li><i>MTD</i>-inspired interface for <i>M</i>emory <i>T</i>echnology <i>D</i>evices.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li><i>FTL</i>.  Simple <i>F</i>lash <i>T</i>ranslation <i>L</i>ayer support file systems on FLASH.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>NXFFS. the NuttX wear-leveling FLASH file system.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Support for SPI-based FLASH and FRAM devices.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>USB Host Support</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>USB host architecture for USB host controller drivers and device-dependent USB class drivers.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>USB host controller drivers available for the NXP LPC17xx.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Device-dependent USB class drivers available for USB mass storage and HID keyboard.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>USB Device Support</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li><i>Gadget</i>-like architecture for USB device controller drivers and device-dependent USB class drivers.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>USB device controller drivers available for the PIC32, NXP LPC17xx, LPC214x, LPC313x, LPC43xx, STMicro STM32 and TI DM320.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Device-dependent USB class drivers available for USB serial (CDC/ACM and a PL2303 emulation), for USB mass storage, and for a composite CDC/ACM and mass storage device.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Built-in <a href="UsbTrace.html">USB trace</a> functionality for USB debug.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Graphics Support</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Framebuffer drivers.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>LCD drivers for both parallel and SPI LCDs and OLEDs.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
         NX: A graphics library, tiny windowing system and tiny font support that works with either framebuffer or LCD drivers.
         Documented in the <a href="NXGraphicsSubsystem.html">NX Graphics Subsystem</a>
         manual.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Font management sub-system.</li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
         <a href="NxWidgets.html">NxWidgets</a>: NXWidgets is library of graphic objects, or &quot;widgets,&quot (labels, buttons, text boxes, images, sliders, progress bars, etc.). NXWidgets is written in C++ and integrates seamlessly with the NuttX NX graphics and font management subsystems.
      </li>
    </p>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>
         <a href="NxWidgets.html">NxWM</a>: NxWM is the tiny NuttX window manager based on NX and NxWidgets.
      </li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Input Devices</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Touchscreen, USB keyboard, GPIO-based buttons and keypads. </li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Analog Devices</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Support for Analog-to-Digital conversion (ADC), Digital-to-Analog conversion (DAC), multiplexers, and amplifiers.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Motor Control</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <li>Pulse width modulation (PWM) / Pulse count modulation.</li>
    </p>
</tr>
</table></center>

<p>
  <b>NuttX Add-Ons</b>.
  The following packages are available to extend the basic NuttX feature set:
</p>
<center><table width="90%">

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>NuttShell (NSH)</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>A small, scalable, bash-like shell for NuttX with rich feature set and small footprint.
        See the <a href="NuttShell.html">NuttShell User Guide</a>.</li>
    </p>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Pascal Compiler with NuttX runtime P-Code interpreter add-on</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      <li>The Pascal add-on is available for download from the
        <a href="http://sourceforge.net/project/showfiles.php?group_id=189573">SourceForge</a>
        website.</li>
    </p>
  </td>
</tr>
</table></center>

<p>
  <b>Look at all those files and features... How can it be a tiny OS?</b>.
  The NuttX feature list (above) is fairly long and if you look at the NuttX
  source tree, you will see that there are hundreds of source files comprising
  NuttX.  How can NuttX be a tiny OS with all of that?
</p>
<center><table width="90%">

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Lots of Features -- More can be smaller!</b>
  </td>
</tr>

<tr>
  <td><br></td>
  <td>
    <p>
      The philosophy behind that NuttX is that lots of features are great... <i>BUT</i>
      also that if you don't use those features, then you should not have to pay a penalty
      for the unused features.
      And, with NuttX, you don't!  If you don't use a feature, it will not
      be included in the final executable binary.
      You only have to pay the penalty of increased footprint for the features
      that you actually use.
    </p>
    <p>
      Using a variety of technologies, NuttX can scale from the very tiny to
      the moderate-size system.  I have executed NuttX with some simple applications
      in as little as 32K <i>total</i> memory (code and data).
      On the other hand, typical, richly featured NuttX builds require more like 64K
      (and if all of the features are used, this can push 100K).
    </p>
  </td>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Many, many files -- More really is smaller!</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      One may be intimidated by the size NuttX source tree.  There are hundreds of source files!
      How can that be a tiny OS?
      Actually, the large number of files is one of the tricks to keep NuttX small and
      as scalable as possible.
      Most files contain only a single function. 
      Sometimes just one tiny function with only a few lines of code.
      Why?
    </p>
    <ul>
      <li>
        <b>Static Libraries</b>.
        Because in the NuttX build processed, objects are compiled and saved into
        <i>static libraries</i> (<i>archives</i>).
        Then, when the file executable is linked, only the object files that are needed
        are extracted from the archive and added to the final executable.
        By having many, many tiny source files, you can assure that no code that you do
        not execute is ever included in the link.
        And by having many, tiny source files you have better granularity --
        if you don't use that tiny function of even just a few lines of code, it will
        not be included in the binary.
      </li>
    </ul>
  </td>
</tr>

<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Other Tricks</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      As mentioned above, the use of many, tiny source files and linking from static
      libraries keeps the size of NuttX down.
      Other tricks used in NuttX include:
    </p>
    <ul>
      <li>
         <b>Configuration Files</b>.
         Before you build NuttX, you must provide a configuration file that specifies
         what features you plan to use and which features you do not.
         This configuration file contains a long list of settings that control
         what is built into NuttX and what is not.
         There are hundreds of such settings
         (see the <a href="NuttXPortingGuide.html#apndxconfigs">NuttX Porting Guide</a>
         for a partial list that excludes platform specific settings).
         These many, many configuration options allow NuttX to be highly tuned to
         meet size requirements.
         The downside to all of these configuration options is that it greatly
         complicates the maintenance of NuttX -- but that is my problem, not yours.
      </li>
      <li>
         <b>Weak Symbols</b>
         The GNU toolchain supports <i>weak</i> symbols and these also help to keep
         the size of NuttX down.
         Weak symbols prevent object files from being drawn into the link even if they
         are accessed from source code.
         Careful use of weak symbols is another trick for keep unused code out of the
         final binary.
      </li>
    </ul>
  </td>
</tr>

</table></center>


<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="group"><h1>NuttX Discussion Group</h1></a>
  </td>
  </tr>
</table>

<p>
  Most NuttX-related discussion occurs on the <a href="http://tech.groups.yahoo.com/group/nuttx/" target="_top"><i>Yahoo!</i> NuttX group</a>.
  You are cordially invited to <a href="http://groups.yahoo.com/group/nuttx/join" target="_top">join</a>.
  I make a special effort to answer any questions and provide any help that I can.
</p>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="downloads"><h1>Downloads</h1></a>
  </td>
  </tr>
</table>

<h2>NuttX-6.21 Release Notes</h2>
<p>
  The 88<sup>th</sup> release of NuttX, Version 6.21, was made on August 25, 2012, and is available for download from the
  <a href="http://sourceforge.net/projects/nuttx/files/">SourceForge</a> website.
  Note that the release consists of two tarballs:  <code>nuttx-6.21.tar.gz</code> and <code>apps-6.21.tar.gz</code>.
  Both may be needed (see the top-level <code>nuttx/README.txt</code> file for build information)
  The change log associated with the release is available <a href="#currentrelease">here</a>.
  Unreleased changes after this release are available in SVN.
  These unreleased changes are also listed <a href="#pendingchanges">here</a>.
</p>
<p>
  This release corresponds with SVN release number: r5052
</p>
<p>
  <b>Additional new features and extended functionality</b>
</p>
<ul>
  <li><b>Core</b>
    <ul>
      <li>
        Add support for multiple registered <code>atexit()</code> functions.
      </li>
      <li>
        Syslog extended: 
        Now any character driver may be used for the debug logging device.
        Mountpoint traversal logic.
      </li>
      </ul>
  </li>
  <li><b>Common Drivers</b>
    <ul>
      <li>
        Added support for the TI PGA112-7 amplifier/multiplexor.
      </li>
    </ul>
  </li>
  <li><b>NXP LPC43XX</b>
    <ul>
      <li>
        Added clock ramp-up logic to run at 204 MHz.
      </li>
    </ul>
  </li>
  <li><b>NXP LPC43XX Drivers</b>
    <ul>
      <li>
        SPIFI block driver
      </li>
      <li>
        RS-485 support
      </li>
      <li>
        Minimal termios support
      </li>
      <li>
        Framework for USB0 device controller driver.
      </li>
    </ul>
  </li>
  <li><b>NXP LPC17XX Drivers</b>
    <ul>
      <li>
        Minimal termios support
      </li>
    </ul>
  </li>
  <li><b>STM32</b>
    <ul>
      <li>
        Support for STM32 F1 &quot;Value Line&quot; (contributed by Mike Smith).
      </li>
      <li>
        Add support for STM32 F107 &quot;Connectivity Line&quot; (contributed by Max Holtzberg).
      </li>
      <li>
        Clock restart logic needed for recovery from low power modes.
      </li>
    </ul>
  </li>
  <li><b>STM32 Drivers</b>
    <ul>
      <li>
        RTC alarm support. Usable for wakeup from sleep mode.
      </li>
      <li>
        Minimal serial termios support.
      </li>
      <li>
        USB OTG FS host driver (alpha).
      </li>
    </ul>
  </li>
  <li><b>STM32 Boards</b>
    <ul>
      <li>
        Add power management hooks for the STM32F4Discovery
      </li>
      <li>
        Add support for the Olimex STM32-P107 (contributed by Max Holtzberg)
      </li>
    </ul>
  </li>
  <li><b>PIC32</b>
    <ul>
      <li>
        Add support for the Pinguino MIPS toolchain
      </li>
    </ul>
  </li>
  <li><b>PIC32 Drivers</b>
    <ul>
      <li>
        GPIO driver now supports F1 analog regiaters (ANSEL)
       </li>
    </ul>
  </li>
  <li><b>PIC32 Boards</b>
    <ul>
      <li>
        Add support for the PGA117 on the Mirtoo module
      </li>
    </ul>
  </li>
  <li><b>Calypso</b>
    <ul>
      <li>
        Add support for the SSD1783 LCD on the Compal E99
      </li>
    </ul>
  </li>

  <li><b>Library</b>
    <ul>
      <li>
        <code>cfsetispeed()</code>, <code>cfsetospeed()</code>, <code>tcflush()</code>, <code>memchr()</code>, and <code>memccpy()</code>.
      </li>
    </ul>
  </li>
  <li><b>Applications</b>
    <ul>
      <li>
        Port of freemodbus-v1.5.0.
      </li>
      <li>
        Add support for testing devices with multiple ADC, PWM, and QE devices.  
      </li>
      <li>
        NSH <code>mount</code> command (with no arguments) will now show mounted volumes.
      </li>
      <li>
        Added new NSH <code>df</code> command to show file system usage.
      </li>
      <li>
        Extended NSH 'help' support.
      </li>
      <li>
        NSH now catches the return value from spawned applications (provided by Mike Smith).
      </li>
    </ul>
  </li>
  <li><b>Build System</b>
    <ul>
      <li>
        <code>mkconfig</code> will not define <code>CONFIG_DRAM_END</code>.
      </li>
      <li>
        A lot of  progress has been made on the automated NuttX configuration logic (Thanks go to Richard Cochran).
      </li>
    </ul>
  </li>
  <li><b>Documentation</b>
    <ul>
      <li>
       Document ways to customize the behavior of NSH
      </li>
    </ul>
  </li>
</ul>

<p><b>Bugfixes</b> (see the change log for details):</p>
<ul>
  <li><b>Serial drivers (all)</b>
    <ul>
      <li>
      Fix <code>ioctl()</code> return value.
      </li>
      <li>
      Common &quot;upper half&quot; serial driver will now return with <code>EINTR</code> if a serial wait is interrupted by a signal.
      </li>
    </ul>
  </li>
  <li><b>FAT</b>
    <ul>
      <li>
        Fix statfs() file name length
      </li>
    </ul>
  </li>
  <li><b>NXP LPC43xx</b>
    <ul>
      <li>
        Clock configuration
      </li>
    </ul>
  </li>
  <li><b>STM32</b>
    <ul>
      <li>
      Pinmap fixes
      </li>
      <li>
      SPI driver re-initialization
      </li>
    </ul>
  </li>
  <li><b>STM32 Boards</b>
    <ul>
      <li>
         Correct and lower SDIO frequency for F2 and f4 boards
      </li>
    </ul>
  </li>
  <li><b>AVR</b>
    <ul>
      <li>
        C++ build issues
      </li>
    </ul>
  </li>
  <li><b>Power Management (PM)</b>
    <ul>
      <li>
        Fix a place where interrupts were not be re-enabled
      </li>
    </ul>
  </li>
  <li><b>Applications</b>
    <ul>
      <li>
        Fix NSH application start-up race condition
      </li>
    </ul>
  </li>
  <li><b>Library</b>
    <ul>
      <li>
        Fieldwidth and justification for <code>%s</code> format.
      </li>
      <li>
        Fixed several issues with presenting floating point numbers.
      </li>
      <li>
        NULL definition for C++
      </li>
    </ul>
  </li>
</ul>
<p>
  See the <a href="#currentrelease">ChangeLog</a> for additional, detailed changes.
</p>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="platforms"><h1>Supported Platforms</h1></a>
  </td>
  </tr>
</table>

<p>
  The short story (Number of ports follow in parentheses).
  The state of the various ports vary from board-to-board.
  Follow the links for the details:
</p>
<center><table width="90%">
<ul>
  <tr>
  <td bgcolor="#e4e4e4" valign="top">
  <li><a href="#linuxusermode">Linux user mode simulation</a> (1)</li>
  <li>ARM
    <ul>
      <li><a href="#arm7tdmi">ARM7TDMI</b></a> (5)</li>
      <li><a href="#arm920t">ARM920T</a> (1) </li>
      <li><a href="#arm926ejs">ARM926EJS</a> (3) </li>
      <li><a href="#armcortexm3">ARM Cortex-M3</a> (16)</li>
      <li><a href="#armcortexm4">ARM Cortex-M4</a> (5)</li>
    </ul>
  <li>Atmel AVR
    <ul>
      <li><a href="#atmelavr">Atmel 8-bit AVR</a> (3) </li>
      <li><a href="#atmelavr32">Atmel AVR32</a> (1) </li>
    </ul>
  </li>
  </td>
  <td bgcolor="#e4e4e4" valign="top">
  <li>Freescale <a href="#m68hcs12">M68HCS12</a> (2) </li>
  <li>Intel
    <ul>
      <li><a href="#8052">Intel 8052 Microcontroller</a> (1)</li>
      <li><a href="#80x86">Intel 80x86</a> (2)</li>
    </ul>
  </li>
  <li>MicroChip <a href="#pic32mips">PIC32MX</a> (MIPS) (4)</li>
  <li>Renesas/Hitachi:
    <ul>
        <li><a href="#superh">Renesas/Hitachi SuperH</a> (1/2)</li>
        <li><a href="#m16c">Renesas M16C/26</a> (1/2)</li>
    </ul>
  </li>
  </td>
  <td bgcolor="#e4e4e4" valign="top">
  <li>Zilog
    <ul>
        <li><a href="#zilogz16f">Zilog Z16F</a> (1)</li>
        <li><a href="#zilogez80acclaim">Zilog eZ80 Acclaim!</a> (1)</li>
        <li><a href="#zilogz8encore">Zilog Z8Encore!</a> (2)</li>
        <li><a href="#zilogz80">Zilog Z80</a> (2)</li>
    </ul>
  </li>
</ul>
  </tr>
</table></center>

<p>The details, caveats and fine print follow:</p>

<center><table width="90%">
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="linuxusermode"><b>Linux User Mode</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      A user-mode port of NuttX to the x86 Linux/Cygwin platform is available.
      The purpose of this port is primarily to support OS feature development.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        Does not support interrupts but is otherwise fully functional.
      </p>
    </ul>
   </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="arm7tdmi"><b>ARM7TDMI</b></a>.
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>TI TMS320C5471</b> (also called <b>C5471</b> or <b>TMS320DA180</b> or <b>DA180</b>).
      NuttX operates on the ARM7 of this dual core processor.
      This port uses the <a href="http://www.spectrumdigital.com/">Spectrum Digital</a>
      evaluation board with a GNU arm-elf toolchain* under Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        This port is complete, verified, and included in the initial NuttX release.
      </p>
    </ul>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>TI Calypso</b>.
      This port supports the TI &quot;Calypso&quot; MCU used in various cell phones (and, in particular,
      by the <a href="http://bb.osmocom.org/trac/">Osmocom-bb project</a>).
      Like the c5471, NuttX operates on the  ARM7 of this dual core processor.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        This port was contributed by  Denis Carilki and includes the work of Denis, Alan Carvalho de Assis, and Stefan Richter.
        Calypso support first appeared in NuttX-6.17.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>NXP LPC214x</b>.
      Support is provided for the NXP LPC214x family of processors.  In particular,
      support is provided for the mcu123.com lpc214x evaluation board (LPC2148).
      This port also used the GNU arm-elf toolchain* under Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        This port boots and passes the OS test (apps/examples/ostest).
        The port is complete and verified.  As of NuttX 0.3.17, the port includes:
        timer interrupts, serial console, USB driver, and SPI-based MMC/SD card
        support.  A verified NuttShell (<a href="NuttShell.html">NSH</a>)
        configuration is also available.
      </p>
      <p>
        <b>Development Environments:</b>
        1) Linux with native Linux GNU toolchain, 2) Cygwin with Cygwin GNU toolchain, or 3) Cygwin
        with Windows native toolchain (CodeSourcery or devkitARM).  A DIY toolchain for Linux
        or Cygwin is provided by the NuttX
        <a href="http://sourceforge.net/project/showfiles.php?group_id=189573&package_id=224585">buildroot</a>
        package.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>NXP LPC2378</b>.
      Support is provided for the NXP LPC2378 MCU.  In particular,
      support is provided for the Olimex-LPC2378 development board.
      This port was contributed by Rommel Marcelo is was first released in NuttX-5.3.
      This port also used the GNU arm-elf toolchain* under Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        This port boots and passes the OS test (apps/examples/ostest) and includes a
        working implementation of the NuttShell (<a href="NuttShell.html">NSH</a>).
        The port is complete and verified.
        As of NuttX 5.3, the port includes only basic timer interrupts and serial console support.
      </p>
      <p>
        <b>Development Environments:</b> (Same as for the NXP LPC214x).
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STR71x</b>.
      Support is provided for the STMicro STR71x family of processors.  In particular,
      support is provided for the Olimex STR-P711 evaluation board.
      This port also used the GNU arm-elf toolchain* under Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        Integration is complete on the basic port (boot logic, system time, serial console).
        Two configurations have been verified: (1) The board boots and passes the OS test
        with console output visible on UART0, and the NuttShell (<a href="NuttShell.html">NSH</a>)
        is fully functional with interrupt driven serial console.  An SPI driver is available
        but only partially tested.  Additional features are needed: USB driver, MMC integration,
        to name two (the slot on the board appears to accept on MMC card dimensions; I have only
        SD cards).
        An SPI-based ENC29J60 Ethernet driver for add-on hardware is under development and
        should be available in the NuttX 5.5 release.
      </p>
      <p>
        <b>Development Environments:</b>
        1) Linux with native Linux GNU toolchain, 2) Cygwin with Cygwin GNU toolchain, or 3) Cygwin
        with Windows native toolchain (CodeSourcery or devkitARM).  A DIY toolchain for Linux
        or Cygwin is provided by the NuttX
        <a href="http://sourceforge.net/project/showfiles.php?group_id=189573&package_id=224585">buildroot</a>
        package.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="arm920t"><b>ARM920T</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Freescale MC9328MX1</b> or <b>i.MX1</b>.
      This port uses the Freescale MX1ADS development board with a GNU arm-elf toolchain*
      under either Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          This port has stalled due to development tool issues.
          Coding is complete on the basic port (timer, serial console, SPI).
      </p>
    </ul>
   </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="arm926ejs"><b>ARM926EJS</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>TI TMS320DM320</b> (also called <b>DM320</b>).
      NuttX operates on the ARM9 of this dual core processor.
      This port uses the
      <a href="http://wiki.neurostechnology.com/index.php/Developer_Welcome">Neuros OSD</a>
      with a GNU arm-elf toolchain* under Linux or Cygwin.
      The port was performed using the OSD v1.0, development board.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          The basic port (timer interrupts, serial ports, network, framebuffer, etc.) is complete.
          All implemented features have been verified with the exception of the USB device-side
          driver; that implementation is complete but untested.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <b>NXP <a href="http://ics.nxp.com/products/lpc3000/lpc313x.lpc314x.lpc315x/">LPC3131</a></b>.
    The port for the NXP LPC3131 on the <a href="http://www.embeddedartists.com/products/kits/lpc3131_kit.php">Embedded Artists EA3131</a> 
    development board was first released in NuttX-5.1 with a GNU arm-elf or arm-eabi toolchain* under Linux or Cygwin
    (but was not functional until NuttX-5.2).
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          The basic EA3131 port is complete and verified in NuttX-5.2 
          This basic port includes basic boot-up, serial console, and timer interrupts.
          This port was extended in NuttX 5.3 with a USB high speed driver contributed by David Hewson.
          David also contributed I2C and SPI drivers plus several important LPC313x USB bug fixes
          that appear in the NuttX 5.6 release.
          This port has been verified using the NuttX OS test, USB serial and mass storage
          tests and includes a working implementation of the NuttShell (<a href="NuttShell.html">NSH</a>).
      </p>
      <p>
          Support for <a href="NuttXDemandPaging.html">on-demand paging</a> has been developed for the EA3131.
      That support would all execute of a program in SPI FLASH by paging code sections out of SPI flash as needed.
      However, as of this writing, I have not had the opportunity to verify this new feature.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <b>NXP <a href="http://ics.nxp.com/products/lpc3000/lpc313x.lpc314x.lpc315x/">LPC315x</a></b>.
    Support for the NXP LPC315x family has been incorporated into the code base as of NuttX-6.4.
    Support has added for the Embedded Artists EA3152 board in NuttX-6.11.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          Basic support is in place for both the LPC3152 MCU and the EA3152 board.
          Verification of the port was deferred due to tool issues
          However, because of the high degree of compatibility between the LPC313x and LPC315x family, it
          is very likely that the support is in place (or at least very close).
          At this point, verification of the EA3152 port has been overcome by events and
          may never happen.
          However, the port is available for anyone who may want to use it.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="armcortexm3"><b>ARM Cortex-M3</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>TI Stellaris LM3S6432</b>.
      This is a port of NuttX to the Stellaris RDK-S2E Reference Design Kit and the MDL-S2E Ethernet to Serial module
      (contributed by Mike Smith).
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Luminary/TI Stellaris LM3S6918</b>.
      This port uses the <a href=" http://www.micromint.com/">Micromint</a> Eagle-100 development
      board with a GNU arm-elf toolchain* under either Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          The initial, release of this port was included in NuttX  version 0.4.6.
          The current port includes timer, serial console, Ethernet, SSI, and microSD support.
          There are working configurations the NuttX OS test, to run the <a href="NuttShell.html">NuttShell
          (NSH)</a>, the NuttX networking test, and the uIP web server.
      </p>
      <p>
        <b>Development Environments:</b>
        1) Linux with native Linux GNU toolchain, 2) Cygwin with Cygwin GNU toolchain, or 3) Cygwin
        with Windows native toolchain (CodeSourcery or devkitARM).  A DIY toolchain for Linux
        or Cygwin is provided by the NuttX
        <a href="http://sourceforge.net/project/showfiles.php?group_id=189573&package_id=224585">buildroot</a>
        package.
      </p>
     </ul>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Luminary/TI Stellaris LM3S6965</b>.
      This port uses the Stellaris LM3S6965 Ethernet Evalution Kit with a GNU arm-elf toolchain*
      under either Linux or Cygwin.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          This port was released in NuttX 5.5.  
          Features are the same as with the Eagle-100 LM3S6918 described above.
          The apps/examples/ostest configuration has been successfully verified and an
          NSH configuration with Telnet support is available.
          MMC/SD and Networking support was not been thoroughly verified:
          Current development efforts are focused on porting the NuttX window system (NX)
          to work with the Evaluation Kits OLED display.
      </p>
      <p><small>
         <b>NOTE</b>: As it is configured now, you MUST have a network connected.
         Otherwise, the NSH prompt will not come up because the Ethernet
         driver is waiting for the network to come up.
      </small></p>
      <p>
        <b>Development Environments:</b> See the Eagle-100 LM3S6918 above.
      </p>
     </ul>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Luminary/TI Stellaris LM3S8962</b>.
      This port uses the Stellaris EKC-LM3S8962 Ethernet+CAN Evalution Kit with a GNU arm-elf toolchain*
      under either Linux or Cygwin.
      Contributed by Larry Arnold.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          This port was released in NuttX 5.10. 
          Features are the same as with the Eagle-100 LM3S6918 described above.
      </p>
     </ul>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Luminary/TI Stellaris LM3S9B96</b>.
      Header file support was contributed by Tiago Maluta for this part.
      Jose Pablo Rojas V. is currently using those header file changes to port NuttX to the TI/Stellaris EKK-LM3S9B96.
      With any luck, that port should be working and available in the NuttX-6.20 release.
    </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>TI Stellaris LM3S6432S2E</b>.
      This port uses Serial-to-Ethernet Reference Design Kit (<a href="http://www.ti.com/tool/rdk-s2e">RDK-S2E</a>)
      and has similar support as for the other Stellaris family members.
      Configurations are available for the OS test and for the NuttShell (NSH)
      (see the <a href="http://nuttx.sourceforge.net/NuttShell.html">NSH User Guide</a>).
      The NSH configuration including networking support with a Telnet NSH console.
      This port was contributed by Mike Smith.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
          This port was will be released in NuttX 6.14. 
      </p>
     </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F100x</b>.
      Chip support for these STM32 &quot;Value Line&quot; family was contributed by Mike Smith and users have reported that they have successful brought up NuttX on there proprietary boards using this logic.
      However, there is <i>no</i> specific board support for this chip families in the NuttX source tree.
    </p>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F103x</b>.
      Support for four MCUs and three board configurations are available.
      MCU support includes: STM32F103ZET6, STM32F103RET6, and STM32F103VCT.
      Boards supported include:
    </p>
    <ol>
      <li>
        A port for the <a href=" http://www.st.com/">STMicro</a> STM3210E-EVAL development board that
        features the STM32F103ZET6 MCU.
      </li>
      <li>
        The ISOTEL NetClamps VSN V1.2 ready2go sensor network platform based on the
        STMicro STM32F103RET6.  Contributed by Uros Platise.
      </li>
      <li>
        A port for the HY-Mini STM32v board.  This board is based on the
        STM32F103VCT chip.  Contributed by Laurent Latil.
      </li>
    </ol>
    <p>
      These ports uses a GNU arm-elf toolchain* under either Linux or Cygwin (with native Windows GNU
      tools or Cygwin-based GNU tools).
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
      </p>
      <ul>
        <li>
          The basic STM32 port was released in NuttX version 0.4.12. The basic port includes boot-up
          logic, interrupt driven serial console, and system timer interrupts.
          The 0.4.13 release added support for SPI, serial FLASH, and USB device.;
          The 4.14 release added support for buttons and SDIO-based MMC/SD and verifed DMA support.
          Verified configurations are available for NuttX OS test, the NuttShell (NSH) example,
          the USB serial device class, and the USB mass storage device class example.
        </li>
        <li>
          Support for the NetClamps VSN was included in version 5.18 of NuttX.
          Uros Platise added support for timers, RTC, I2C, FLASH, extended power management
          and other features.
        </li>
        <li>
          Additional drivers and configurations were added in NuttX 6.13 and later releases for the STM32 F1 and F4.
          F1 compatible drivers include an Ethernet driver, ADC driver, DAC driver, PWM driver, IWDG, WWDG, and CAN drivers.
        </li>
      </ul>
      <p>
        <b>Development Environments:</b>
        1) Linux with native Linux GNU toolchain, 2) Cygwin with Cygwin GNU toolchain, or 3) Cygwin
        with Windows native toolchain (RIDE7, CodeSourcery or devkitARM).  A DIY toolchain for Linux
        or Cygwin is provided by the NuttX
        <a href="http://sourceforge.net/project/showfiles.php?group_id=189573&package_id=224585">buildroot</a>
        package.
      </p>
     </ul>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F107x</b>.
      Chip support for the STM32 F1 &quot;Connectivity Line&quot; family has been present in NuttX and users have reported that they have successful brought up NuttX on there proprietary boards using this logic.
      Support for the <a href="https://www.olimex.com/dev/stm32-p107.html">Olimex STM32-P107</a> was contributed by Max Holtzberg and first appeared in NuttX-6.21.
    <ul>
      <b>STATUS:</b>
      Configurations for the basic OS test and NSH are available and verified.
    </ul>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F207IG</b>.
      Support for the STMicro STM3220G-EVAL development board was contributed by Gary Teravskis and first released in NuttX-6.16.
    </p>
    <ul>
      <b>STATUS:</b>
      The peripherals of the STM32 F2 family are compatible with the STM32 F4 family.
      See discussion of the STM3240G-EVAL board below for further information.
      </ul>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Atmel AT91SAM3U</b>.
      This port uses the <a href="http://www.atmel.com/">Atmel</a> SAM3U-EK
      development board that features the AT91SAM3U4E MCU.
      This port uses a GNU arm-elf or arm-eabi toolchain* under either Linux or Cygwin (with native Windows GNU
      tools or Cygwin-based GNU tools).
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        The basic SAM3U-EK port was released in NuttX version 5.1. The basic port includes boot-up
        logic, interrupt driven serial console, and system timer interrupts.
        That release passes the NuttX OS test and is proven to have a valid OS implementation.
        A configuration to support the NuttShell is also included.
        NuttX version 5.4 adds support for the HX8347 LCD on the SAM3U-EK board.
        This LCD support includes an example using the
        <a href=" http://nuttx.sourceforge.net/NXGraphicsSubsystem.html">NX graphics system</a>.
        NuttX version 6.10 adds SPI support.
      </p>
      <p>
        Subsequent NuttX releases will extend this port and add support for SDIO-based SD cards and
        USB device (and possible LCD support).
        These extensions may or may not happen soon as my plate is kind of full now.
      </p>
      <p>
        <b>Development Environments:</b>
        1) Linux with native Linux GNU toolchain, 2) Cygwin with Cygwin GNU toolchain, or 3) Cygwin
        with Windows native toolchain (CodeSourcery or devkitARM).  A DIY toolchain for Linux
        or Cygwin is provided by the NuttX
        <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a>
        package.
      </p>
     </ul>
   </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>NXP LPC1766, LPC1768, and LPC1769</b>.
      Drivers are available for CAN, DAC, Ethernet, GPIO, GPIO interrupts, I2C, UARTs, SPI, SSP, USB host, and USB device.
      Verified LPC17xx onfigurations are available for three boards.
      <ul>
        <li>
          The Nucleus 2G board from <a href="http://www.2g-eng.com/">2G Engineering</a> (LPC1768),
        </li>
        <li>
          The mbed board from <a href="http://mbed.org">mbed.org</a> (LPC1768, Contributed by Dave Marples), and
        </li>
        <li>
          The LPC1766-STK board from <a href="http://www.olimex.com/">Olimex</a> (LPC1766).
        </li>
        <li>
          The Embedded Artists base board with NXP LPCXpresso LPC1768.
        </li>
        <li>
          The <a href="http://micromint.com/">Micromint</a> Lincoln60 board with an NXP LPC1769.
        </li>
      </ul>
    </p>
    <p>
      The Nucleus 2G board, the mbed board, and the LPCXpresso all feature the NXP LPC1768 MCU;
      the Olimex LPC1766-STK board features an LPC1766.
      All use a GNU arm-elf or arm-eabi toolchain* under either Linux or Cygwin (with native Windows GNU tools or Cygwin-based GNU tools).
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        The following summarizes the features that has been developed and verified on individual LPC17xx-based boards.
        These features should, however, be common and available for all LPC17xx-based boards.
      </p>
      <ol>
        <li>
        <p><b>Nucleus2G LPC1768</b></p>
        <ul>
          <li>
            Some initial files for the LPC17xx family were released in NuttX 5.6, but
          </li>
          <li>
            The first functional release for the NXP LPC1768/Nucleus2G occured with NuttX 5.7 with
            Some additional enhancements through NuttX-5.9.
          </li>
        </ul>
      </p>
      <p>
        That initial, 5.6, basic release included <i>timer</i> interrupts and a <i>serial console</i> and was
        verified using the NuttX OS test (<code>apps/examples/ostest</code>).
        Configurations available include include a verified NuttShell (NSH) configuration
        (see the <a href="http://nuttx.sourceforge.net/NuttShell.html">NSH User Guide</a>).
        The NSH configuration supports the Nucleus2G's microSD slot and additional configurations
        are available to exercise the the USB serial and USB mass storage devices.
        However, due to some technical reasons, neither the SPI nor the USB device drivers are fully verified.
        (Although they have since been verfiied on other platforms; this needs to be revisited on the Nucleus2G).
      </p>
      </li>
      <li>
        <p><b>mbed LPC1768</b></p>
        <ul>
          <li>
            Support for the mbed board was contributed by Dave Marples and released in NuttX-5.11.
          </li>
        </ul>
      </p>
      <p>
        This port includes a NuttX OS test configuration (see <code>apps/examples/ostest</code>).
      </p>
      </li>
      <li>
        <p><b>Olimex LPC1766-STK</b></p>
        <ul>
          <li>
            Support for that Olimex-LPC1766-STK board was added to NuttX 5.13.
          </li>
          <li>
            The NuttX-5.14 release extended that support with an <i>Ethernet driver</i>.
          </li>
          <li>
            The NuttX-5.15 release further extended the support with a functional <i>USB device driver</i> and <i>SPI-based micro-SD</i>.
          </li>
          <li>
            The NuttX-5.16 release added a functional <i>USB host controller driver</i> and <i>USB host mass storage class driver</i>.
          </li>
          <li>
            The NuttX-5.17 released added support for low-speed USB devicers, interrupt endpoints, and a <i>USB host HID keyboard class driver</i>.
          </li>
        </ul>
      </p>
      <p>
        Verified configurations are now available for the NuttX OS test,
        for the NuttShell with networking and microSD support(NSH, see the <a href="ttp://nuttx.sourceforge.net/NuttShell.html">NSH User Guide</a>),
        for the NuttX network test, for the <a href="http://acme.com/software/thttpd">THTTPD</a> webserver,
        for USB serial deive and USB storage devices examples, and for the USB host HID keyboard driver.
        Support for the USB host mass storage device can optionally be configured for the NSH example.
        A driver for the <i>Nokia 6100 LCD</i> and an NX graphics configuration for the Olimex LPC1766-STK have been added.
        However, neither the LCD driver nor the NX configuration have been verified as of the the NuttX-5.17 release.
      </p>
      </li>
      <li>
        <p><b>Embedded Artists base board with NXP LPCXpresso LPC1768</b></p>
        <p>
           An fully verified board configuration is included in NuttX-6.2.
           The Code Red toolchain is supported under either Linux or Windows.
           Verifed configurations include DHCPD, the NuttShell (NSH), NuttX graphis (NX), the NuttX OS test, THTTPD, and USB mass storage device.
        </p>
      </li>
      <li>
        <p><b>Micromint Lincoln60 board with an NXP LPC1769</b></p>
        <p>
           This board configuration was contributed and made available in NuttX-6.20.
           As contributed board support, I am unsure of what all has been verfied and what has not.
           See the Microment website for more information about the <a href="http://micromint.com/Products/lincoln60.html">Lincoln60</a> board.
           More to come.
        </p>
      </li>
      </ol>
      <p>
        <b>Development Environments:</b>
        1) Linux with native Linux GNU toolchain, 2) Cygwin with Cygwin GNU toolchain, or 3) Cygwin
        with Windows native toolchain (CodeSourcery devkitARM or Code Red).  A DIY toolchain for Linux
        or Cygwin is provided by the NuttX
        <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a>
        package.
      </p>
   </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="armcortexm4"><b>ARM Cortex-M4</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>FreeScale Kinetis K40</b>.
      This port uses the Freescale Kinetis KwikStik K40.
      Refer to the <a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=KWIKSTIK-K40">Freescale web site</a> for further information about this board.
      The Kwikstik is used with the FreeScale Tower System (mostly just to provide a simple UART connection)
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        The unverified KwikStik K40 first appeared in NuttX-6.8
        As of this writing, the basic port is complete but I accidentally locked my board during the initial bringup.
        Further development is stalled unless I learn how to unlock the device (or until I get another K40).
        Additional work remaining includes, among other things: (1) complete the basic bring-up,
        (2) bring up the NuttShell NSH, (3) develop support for the SDHC-based SD card,
        (4) develop support for USB host and device, and (2) develop an LCD driver.
        NOTE: Some of these remaining tasks are shared with the K60 work described below.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>FreeScale Kinetis K60</b>.
      This port uses the Freescale Kinetis TWR-K60N512 tower system.
      Refer to the <a href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=TWR-K60N512-KIT">Freescale web site</a> for further information about this board.
      The TWR-K60N51 includes with the FreeScale Tower System which provides (among other things) a DBP UART connection.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        As of this writing, the basic port is complete and passes the NuttX OS test.
        An additional, validated configuration exists for the NuttShell (NSH, see the
        <a href="http://nuttx.sourceforge.net/NuttShell.html">NSH User Guide</a>).
        This basic TWR-K60N512 first appeared in NuttX-6.8.
        Ethernet and SD card (SDHC) drivers also exist:
        The SDHC driver is partially integrated in to the NSH configuration but has some outstanding issues;
        the Ethernet driver is completely untested.
        Additional work remaining includes: (1) integrate the Ethernet and SDHC drivers, and (2) develop support for USB host and device.
        NOTE: Most of these remaining tasks (excluding the Ethernet driver) are the same as the pending K40 tasks described above.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM3240G-EVAL</b>.
      This port uses the STMicro STM3240G-EVAL board featuring the STM32F407IGH6 MCU.
      Refer to the <a href="http://www.st.com/internet/evalboard/product/252216.jsp">STMicro web site</a> for further information about this board.
    </p>
    <p>
      <b>STATUS:</b>
      <ul>
        <li><b>NuttX-6.12</b>
          The basic port is complete and first appeared in NuttX-6.12.
          The initial port passes the NuttX OS test and includes a validated configuration for the NuttShell (NSH, see the
          <a href="http://nuttx.sourceforge.net/NuttShell.html">NSH User Guide</a>) as well as several other configurations.
        </li>
        <li><b>NuttX-6.13-6.16</b>
          Additional drivers and configurations were added in NuttX 6.13-6.16.
          Drivers include an Ethernet driver, ADC driver, DAC driver, PWM driver, CAN driver, F4 RTC driver, Quadrature Encoder, DMA, SDIO with DMA
          (these should all be compatible with the STM32 F2 family and many should also be compatible with the STM32 F1 family as well).
        </li>
        <li><b>NuttX-6.16</b>
          The NuttX 6.16 release also includes and logic for saving/restoring F4 FPU registers in context switches.
          Networking intensions include support for Telnet NSH sessions and new configurations for DHPCD and the networking test (nettest).
        </li>
        <li><b>NuttX-6.17</b>
          The USB OTG device controller driver, and LCD driver and a function I2C driver were added in NuttX 6.17.
        </li>
        <li><b>NuttX-6.18</b>
          STM32 IWDG and WWDG watchdog timer drivers were added in NuttX 6.18 (should be compatible with F1 and F2).
          An LCD driver and a touchscreen driver for the STM3240G-EVAL based on the STMPE811 I/O expander were also added in NuttX 6.18.
        </li>
        <li><b>NuttX-6.21</b>
          A USB OTG host controller driver was added in NuttX 6.21.
        </li>
      </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>STMicro STM32F4-Discovery</b>.
      This port uses the STMicro STM32F4-Discovery board featuring the STM32F407VGT6 MCU.
      Refer to the <a href="http://www.st.com/internet/evalboard/product/252419.jsp">STMicro web site</a> for further information about this board.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        The basic port for the STM32F4-Discovery was contributed by Mike Smith and was first released in NuttX-6.14.
        Drivers listed for the STM3240G-EVAL may be usable on this plaform as well.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>NXG Technologies LPC4330-Xplorer</b>.
      This NuttX port is for the LPC4330-Xplorer board from NGX Technologies featuring the NXP LPC4330FET100 MCU.
      See the <a href="http://shop.ngxtechnologies.com/product_info.php?cPath=21_37&products_id=104">NXG website</a> for further information about this board.
    </p>
    <p>
      <b>STATUS:</b>
    </p>
    <ul>
      <li>
        <p><b>NuttX-6.20</b>
          The basic port is complete.
          The OS test configuration and the basic NSH configurations are present and fully verified.
          This includes verified support for:  SYSTICK system time,  pin and GPIO configuration, and a serial console.
        </p>
        <p>
          Several drivers have been copied from the related LPC17xx port but require integration into the LPC43xx:  ADC, DAC, GPDMA, I2C, SPI, and SSP.
          The registers for these blocks are the same in both the LPC43xx and the LPC17xx and they should integrate into the LPC43xx very easily by simply adapting the clocking and pin configuration logic.
        </p>
        <p>
          Other LPC17xx drivers were not brought into the LPC43xx port because these peripherals have been completely redesigned:  CAN, Ethernet, USB device, and USB host.
        </p>
        <p>
          So then there is no support for the following LPC43xx peripherals: SD/MMC, EMC, USB0,USB1, Ethernet, LCD, SCT, Timers 0-3, MCPWM, QEI, Alarm timer, WWDT, RTC, Event monitor, and CAN.
        </p>
        <p>
          Some of these can be leveraged from other MCUs that appear to support the same peripheral IP:
          <ul>
            <li>
              The LPC43xx USB0 peripheral appears to be the same as the USB OTG peripheral for the LPC31xx.
              The LPC31xx USB0 device-side driver has been copied from the LPC31xx port but also integration into the LPC43xx (clocking and pin configuration).
              It should be possible to complete poriting of this LPC31xx driver with a small porting effort.
            </li>
            <li>
              The Ethernet block looks to be based on the same IP as the STM32 Ethernet and, as a result, it should be possible to leverage the NuttX STM32 Ethernet driver with a little more effort.
            </li>
          </ul>
        </p>
      </li>
      <li>
        <p><b>NuttX-6.21</b>
        Added support for a SPIFI block driver and for RS-485 option to the serial driver.
      </li>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
  <p>
    <b>Development Environments:</b>
    1) Linux with native Linux GNU toolchain, 2) Cygwin with Cygwin GNU Cortex-M3 or 4toolchain, or 3) Cygwin with Windows native GNU Cortex-M3 or M4 toolchain (CodeSourcery or devkitARM).  A DIY toolchain for Linux or Cygwin is provided by the NuttX
    <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a> package.
    I use FreeScale's <i>CodeWarrior</i> IDE only to work with the JTAG debugger built into the Kinetis boards.
    I use the <i>Code Red</i> IDE with the some of the NXP parts and the <i>Atollic</i> toolchain with some of the STMicroelectronics parts.
  </p>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="atmelavr"><b>Atmel AVR</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>SoC Robotics ATMega128</b>.
      This port of NuttX to the Amber Web Server from <a href="http://www.soc-robotics.com/index.htm">SoC Robotics</a>
      is partially completed.
      The Amber Web Server is based on an Atmel ATMega128.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         Work on this port has stalled due to toolchain issues.  Complete, but untested
         code for this port appears in the NuttX 6.5 release.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Micropendous 3 AT90USB64x</b> and <b>AT90USB6128x</b>.
      This port of NuttX to the Opendous Micropendous 3 board. The Micropendous3 is
      may be populated with an AT90USB646, 647, 1286, or 1287.  I have only the AT90USB647
      version for testing.  This version have very limited memory resources: 64K of
      FLASH and 4K of SRAM.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         The basic port was released in NuttX-6.5.  This basic port consists only of
         a &quot;Hello, World!!&quot; example that demonstrates initialization of the OS,
         creation of a simple task, and serial console output.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>PJRC Teensy++ 2.0 AT90USB1286</b>.
      This is a port of NuttX to the PJRC Teensy++ 2.0 board.
      This board was developed by <a href="http://pjrc.com/teensy/">PJRC</a>.
      The Teensy++ 2.0 is based on an Atmel AT90USB1286 MCU.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         The basic port was released in NuttX-6.5.  This basic port consists of
         a &quot;Hello, World!!&quot; example that demonstrates initialization of the OS,
         creation of a simple task, and serial console output as well as a somewhat
         simplified NuttShell (NSH) configuration (see the
         <a href="http://nuttx.sourceforge.net/NuttShell.html">NSH User Guide</a>).
      </p>
      <p>
         An SPI driver and a USB device driver exist for the AT90USB as well
         as a USB mass storage configureation.  However, this configuration is not
         fully debugged as of the NuttX-6.5 release.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p><b>AVR-Specific Issues</b>.
      The basic AVR port is solid and biggest issue for using AVR is its tiny SRAM memory and its Harvard architecture.
      Because of the Harvard architecture, constant data that resides to flash is inaccessible using &quot;normal&quot; memory reads and writes (only SRAM data can be accessed &quot;normally&quot;).
      Special AVR instructions are available for accessing data in FLASH, but these have not been integrated into the normal, general purpose OS.
    </p>
    <p>
      Most NuttX test applications are console-oriented with lots of strings used for printf and debug output.
      These strings are all stored in SRAM now due to these data accessing issues and even the smallest console-oriented applications can quickly fill a 4-8K memory.
      So, in order for the AVR port to be useful, one of two things would need to be done:
    </p>
    <ol>
      <li>
        Don't use console applications that required lots of strings.
        The basic AVR port is solid and your typical deeply embedded application should work fine.
        Or,
      </li>
      <li>
        Create a special version of printf that knows how to access strings that reside in FLASH (or EEPROM).
      </li>
    </ol>
</tr>
<tr>
  <td><br></td>
  <td>
      <p>
        <b>Development Environments:</b>
        1) Linux with native Linux GNU toolchain, 2) Cygwin with Cygwin GNU toolchain, or 3) Cygwin with Windows native toolchain. 
        All testing, however, has been performed using the NuttX DIY toolchain for Linux  or Cygwin is provided by the NuttX
        <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a> package.
        As a result, that toolchain is recommended.
      </p>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><br></td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="atmelavr32"><b>Atmel AVR32</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>AV32DEV1</b>.
      This port uses the www.mcuzone.com AVRDEV1 board based on the Atmel AT32UC3B0256 MCU.
      This port requires a special GNU avr32 toolchain available from atmel.com website.
      This is a windows native toolchain and so can be used only under Cygwin on Windows.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         This port is has completed all basic development, but there is more that needs to be done.
         All code is complete for the basic NuttX port including header files for all AT32UC3* peripherals.
         The untested AVR32 code was present in the 5.12 release of NuttX.
         Since then, the basic RTOS port has solidified:
      </p>
      <ul>
        <li>
          The port successfully passes the NuttX OS test (apps/examples/ostest).
        </li>
        <li>
          A NuttShell (NSH) configuration is in place (see the <a href="http://nuttx.sourceforge.net/NuttShell.html">NSH User Guide</a>).
          Testing of that configuration has been postponed (because it got bumped by the Olimex LPC1766-STK port).
          Current Status: I think I have a hardware problem with my serial port setup.
          There is a good chance that the NSH port is complete and functional, but I am not yet able to demonstrate that.
          At present, I get nothing coming in the serial RXD line (probably because the pins are configured wrong or I have the MAX232 connected wrong).
        </li>
      </ul>
      <p>
        The basic, port (including the verified apps/examples/ostest configuration) was be released in NuttX-5.13.
        A complete port will include drivers for additional AVR32 UC3 devices -- like SPI and USB --- and will be available in a later release,
        time permitting.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="m68hcs12"><b>Freescale M68HCS12</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>MC9S12NE64</b>.
      Support for the MC9S12NE64 MCU and two boards are included:
    </p>
    <ul>
      <li>
        The Freescale DEMO9S12NE64 Evaluation Board, and
      </li>
      <li>
        The Future Electronics Group NE64 /PoE Badge board.
      </li>
    </ul>
    <p>
      Both use a GNU arm-elf toolchain* under Linux or Cygwin.
      The NuttX <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a> provides a properly patched GCC 3.4.4 toolchain that is highly optimized for the m9s12x family.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         Coding is complete for the MC9S12NE64 and for the NE64 Badge board.
         However, testing has not yet begun due to issues with BDMs, Code Warrior, and
         the paging in the build process.
         Progress is slow, but I hope to see a fully verified MC9S12NE64 port in the near future.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="8052"><b>Intel 8052 Microcontroller</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>PJRC 87C52 Development Board</b>.
      This port uses the <a href="http://www.pjrc.com/">PJRC</a> 87C52 development system
      and the <a href="http://sdcc.sourceforge.net/">SDCC</a> toolchain under Linux or Cygwin.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
        This port is complete but not stable with timer interrupts enabled.
        There seems to be some issue when the stack pointer enters into the indirect IRAM
        address space during interrupt handling.
        This architecture has not been built in some time will likely have some compilation
        problems because of SDCC compiler differences.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="80x86"><b>Intel 80x86</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>QEMU/Bifferboard i486</b>.
      This port uses the <a href="http://wiki.qemu.org/Main_Page">QEMU</a> i486 and the native
      Linux, Cywgin, MinGW the GCC toolchain under Linux or Cygwin.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         The basic port was code-complete in NuttX-5.19 and verifed in NuttX-6.0.
         The port was verified using the OS and NuttShell (NSH) examples under QEMU.
         The port is reported to be functional on the <a href="http://bifferos.bizhat.com">Bifferboard</a> as well.
         This is a great, stable starting point for anyone interest in fleshing out the x86 port!
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>RGMP</b>.
      RGMP stands for RTOS and GPOS on Multi-Processor.
      RGMP is a project for  running GPOS and RTOS simultaneously on multi-processor platforms
      You can port your favorite RTOS to RGMP together with an unmodified Linux to form a hybrid operating system.
      This makes your application able to use both RTOS and GPOS features.
    </p>
    <p>
      See the <a href="http://rgmp.sourceforge.net/wiki/index.php/Main_Page">RGMP Wiki</a> for further information about RGMP.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
         This initial port of NuttX to RGMP was provided in NuttX-6.3.
         This initial RGP port provides only minimal driver support and does not use the native NuttX interrupt system.
         This is a great, stable starting point for anyone interest in working with NuttX under RGMP!
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="pic32mips"><b>MicroChip PIC32 (MIPS)</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p><b>PIC32MX250F128D</b>.
      A port is in progress from the DTX1-4000L &quot;Mirtoo&quot; module from <a href="http://www.dimitech.com/" >Dimitech</a>.
      This module uses MicroChip PIC32MX250F128D and the Dimitech DTX1-4000L EV-kit1 V2.
      See the <a href="http://www.dimitech.com/">Dimitech</a> website for further information.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        The basic port is code complete.
        Two configurations are available:
        (1) An OS test configuration and a (2) configuration that support the NuttShell (NSH).
        The OS test configuration is fully functional and proves that we have a basically healthy NuttX port to the Mirtoo.
        The NSH configuration includes support for a serial console and for the SST25 serial FLASH and the PGA117 amplifier/multiplexer on board the module.
        The NSH configuration is set up to use the NuttX wear-leveling FLASH file system (NXFFS).
        The PGA117, however, is not yet fully integrated to support ADC sampling.
        See the <a href="http://nuttx.sourceforge.net/NuttShell.html">NSH User Guide</a> for further information about NSH.
        The first verified port to the Mirtoo module was available with the NuttX 6.20 release.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
   <p><b>PIC32MX460F512L</b>.  There one two board ports using this chip:</p>
   <ul>
    <li><b>PIC32MX Board from PCB Logic Design Co</b>.
      This port is for the PIC32MX board from PCB Logic Design Co. and used the PIC32MX460F512L.
      The board is a very simple -- little more than a carrier for the PIC32 MCU plus voltage regulation, debug interface, and an OTG connector.
    </li>
    <p>
      <b>STATUS:</b>
      The basic port is code complete and fully verified in NuttX 6.13.
      Available configurations include the OS test and the NuttShell (NSH - see the <a href="http://nuttx.sourceforge.net/NuttShell.html">NSH User Guide</a>).
    </p>
    <li><b>UBW32 Board from Sparkfun</b>
      This is the port to the Sparkfun UBW32 board.
      This port uses the <a href="http://www.sparkfun.com/products/8971">original v2.5</a> board which is based on the MicroChip PIC32MX460F512L.
      This older version has been replaced with this <a href="http://www.sparkfun.com/products/9713">newer board</a>.
      See also the <a href="http://www.schmalzhaus.com/UBW32/">UBW32</a> web site.
    </li>
    <p>
      <b>STATUS:</b>
      The basic port is code complete and fully verified in NuttX 6.18.
      Available configurations include the OS test and the NuttShell (NSH - see the <a href="http://nuttx.sourceforge.net/NuttShell.html">NSH User Guide</a>).
      USB has not yet been fully tested but on first pass appears to be functional.
    </p>
  </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>PIC32MX440F512H</b>.
        This port uses the &quot;Advanced USB Storage Demo Board,&quot; Model DB-DP11215, from <a href="http://www.sureelectronics.net">Sure Electronics</a>.
        This board features the MicroChip PIC32MX440F512H.
        See the <a href="http://www.sureelectronics.net/goods.php?id=1168">Sure website</a> for further information about the DB-DP11215 board.
        (I believe that that the DB-DP11215 may be obsoleted now but replaced with the very similar, DB-DP11212.
        The DB-DP11212 board differs, I believe, only in its serial port configuration.)
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
       This NuttX port is code complete and has considerable test testing.
       The port for this board was completed in NuttX 6.11, but still required a few bug fixes before it will be ready for prime time.
       The fully verified port first appeared in NuttX 6.13.
       Available configurations include the OS test and the NuttShell (NSH - see the <a href="http://nuttx.sourceforge.net/NuttShell.html">NSH User Guide</a>).
       An untested USB device-side driver is available in the source tree.
       A more complete port would include support of the USB OTG port and of the LCD display on this board.
       Those drivers are not yet available as of this writing.
       </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>PIC32MX795F512L</b>.
        There one two board ports using this chip:
    </p>
    <ul>
      <li><b>Microchip PIC32 Ethernet Starter Kit</b>.
         This port uses the Microchip PIC32 Ethernet Starter Kit (DM320004) with the Expansion I/O board.
         See the <a href="http://ww.microchip.com">Microchip website</a> for further information.
      </li>
      <p>
       <b>STATUS:</b>
         This port was started and then shelved for some time until I received the Expansion I/O board.
         The basic Starter Kit (even with the Multimedia Expansion Board, MEB, DM320005)) has no serial port and most NuttX test configurations depend heavily on console output.
      </p>
      <p>
         Verified configurations for the OS test and the NuttShel (NSH) appeared in NuttX-6.16.
         Board support includes a verified USB (device-side) driver.
         Also included are a a verified Ethernet driver, a partially verified USB device controller driver, and an unverifed SPI driver.
         Stay tuned for updates.
      </p>
     <li><b>Mikroelektronika PIC32MX7 Mulitmedia Board (MMB)</b>.
        A port has been completed for the  Mikroelektronika PIC32MX7 Multimedia Board (MMB).
        See http://www.mikroe.com/ for further information about this board.
      </li>
      <p>
       <b>STATUS:</b>
         Two verified configurations are available:
         (1) The basic OS test configuration that verfies the correctness port of NuttX, and (2) an extensive <a href="NuttShell.html">NuttShell (NSH)</a> configuration.
         The NSH configuration includes:
         (1) Full network support,
         (2) Verified SPI driver,
         (3) SPI-based SD Card support,
         (4) USB device support (including configuration options for the USB mass storage device and the CDC/ACM serial class), and
         (5) Support for the MIO873QT2 LCD on the PIC32MX7 MMB.
       </p>
       </p>
         The PIC32MX7 MMB's touchscreen is connected directly to the MCU via ADC pins.
         A touchscreen driver has been developed using the PIC32's ADC capabilities and can be enabled in the NSH configuration.
         However, additional verification and tuning of this driver is required.
         Further display/touchscreen verification would require C++ support (for NxWidgets and NxWM).
         Since I there is no PIC32 C++ is the free version of the MPLAB C32 toolchain, further graphics development is stalled.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Development Environment:</b>
      These ports uses either:
    </p>
    <ol>
      <li>
        The <i>LITE</i> version of the PIC32MX toolchain available
        for download from the <a href="http://www.microchip.com">MicroChip</a> website, or
      </li>
      <li>
        The Pinguino MIPS ELF toolchain avaiable from the Pinquino <a href="http://code.google.com/p/pinguino32/downloads/list">website</a>.
      </li>
    </ol>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><br></td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="superh"><b>Renesas/Hitachi SuperH</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>SH-1 SH7032</b>.
      This port uses the Hitachi SH-1 Low-Cost Evaluation Board (SH1_LCEVB1), US7032EVB,
      with a GNU ELF toolchain* under Linux or Cygwin.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
        This port is available as of release 0.3.18 of NuttX.  The port is basically complete
        and many examples run correctly.  However, there are remaining instabilities that
        make the port un-usable.  The nature of these is not understood; the behavior is
        that certain SH-1 instructions stop working as advertised.  This could be a silicon
        problem, some pipeline issue that is not handled properly by the gcc 3.4.5 toolchain
        (which has very limit SH-1 support to begin with), or perhaps with the CMON debugger.
        At any rate, I have exhausted all of the energy that I am willing to put into this cool
        old processor for the time being.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="m16c"><b>Renesas M16C/26</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Renesas M16C/26 Microncontroller</b>.
      This port uses the Renesas SKP16C26 Starter kit and the GNU M32C toolchain. 
      The development environment is either Linux or Cygwin under WinXP.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        Initial source files released in nuttx-0.4.2.
        At this point, the port has not been integrated;    the target cannot be built
        because the GNU <code>m16c-elf-ld</code> link fails with  the following message:
      </p>
      <ul>
      <code>m32c-elf-ld: BFD (GNU Binutils) 2.19 assertion fail /home/Owner/projects/nuttx/buildroot/toolchain_build_m32c/binutils-2.19/bfd/elf32-m32c.c:482</code>
      </ul>
      <p>Where the reference line is:</p>
      <ul><pre>
/* If the symbol is out of range for a 16-bit address,
   we must have allocated a plt entry.  */
BFD_ASSERT (*plt_offset != (bfd_vma) -1);
</pre></ul>
      <p>
        No workaround is known at this time.  This is a show stopper for M16C for
        the time being.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="zilogz16f"><b>Zilog Z16F</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Zilog z16f Microncontroller</b>.
      This port use the Zilog z16f2800100zcog development kit and the Zilog
      ZDS-II Windows command line tools.
      The development environment is Cygwin under WinXP.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        The initial release of support for the z16f was made available in NuttX version 0.3.7.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="zilogez80acclaim"><b>Zilog eZ80 Acclaim!</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Zilog eZ80Acclaim! Microncontroller</b>.
      There are two eZ80Acclaim! ports:
    </p>
    <ul>
      <li>One uses the ZiLOG ez80f0910200kitg development kit, and
      <li>The other uses the ZiLOG ez80f0910200zcog-d development kit.
    </ul>
    <p>
      Both boards are based on the eZ80F091 part and both use the Zilog ZDS-II
      Windows command line tools.
      The development environment is Cygwin under WinXP.
    </p>
    <ul>
      <p>
        <b>STATUS:</b>
        Integration and testing of NuttX on the  ZiLOG ez80f0910200zcog-d is complete.
        The first integrated version was released in NuttX version 0.4.2 (with important early bugfixes
        in 0.4.3 and 0.4.4).
        As of this writing, that port provides basic board support with a serial console, SPI, and eZ80F91 EMAC driver.
      </p>
    </ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="zilogz8encore"><b>Zilog Z8Encore!</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Zilog Z8Encore! Microncontroller</b>.
      This port uses the either:
    </p>
    <ul>
      <li>Zilog z8encore000zco development kit, Z8F6403 part, or</li>
      <li>Zilog z8f64200100kit development kit, Z8F6423 part</li>
    </ul>
    <p>
      and the Zilog ZDS-II Windows command line tools.
      The development environment is Cygwin under WinXP.
    </p>
    <ul>
       <p>
         <b>STATUS:</b>
         This release has been verified only on the ZiLOG ZDS-II Z8Encore! chip simulation
         as of nuttx-0.3.9.
       </p>
     <ul>
  </td>
</tr>
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <a name="zilogz80"><b>Zilog Z80</b>.</a>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Z80 Instruction Set Simulator</b>.
      This port uses the <a href="http://sdcc.sourceforge.net/">SDCC</a> toolchain
      under Linux or Cygwin (verified using version 2.6.0).
      This port has been verified using only a Z80 instruction simulator.
      That simulator can be found in the NuttX SVN
      <a href="http://nuttx.svn.sourceforge.net/viewvc/nuttx/trunk/misc/sims/z80sim/">here</a>.
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
        This port is complete and stable to the extent that it can be tested
        using an instruction set simulator.
      </p>
    <ul>
  </td>
</tr>
<tr>
  <td><br></td>
  <td><hr></td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>XTRS: TRS-80 Model I/III/4/4P Emulator for Unix</b>.
      A very similar Z80 port is available for <a href="http://www.tim-mann.org/xtrs.html">XTRS</a>,
      the TRS-80 Model I/III/4/4P Emulator for Unix.
      That port also uses the <a href="http://sdcc.sourceforge.net/">SDCC</a> toolchain
      under Linux or Cygwin (verified using version 2.6.0).
    </p>
    <ul>
      <p>
       <b>STATUS:</b>
       Basically the same as for the Z80 instruction set simulator.
       This port was contributed by Jacques Pelletier.
      </p>
    <ul>
  </td>
</tr>
</table></center>

<blockquote>* A highly modified <a href="http://buildroot.uclibc.org/">buildroot</a>
is available that may be used to build a NuttX-compatible ELF toolchain under
Linux or Cygwin.  Configurations are available in that buildroot to support ARM, Cortex-M3,
avr, m68k, m68hc11, m68hc12, m9s12, blackfin, m32c, h8, and SuperH ports.</blockquote>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="environments"><h1>Development Environments</h1></a>
  </td>
  </tr>
</table>

<center><table width="90%">
<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Linux + GNU <code>make</code> + GCC/binutils</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      The is the most natural development environment for NuttX.
      Any version of the GCC/binutils toolchain may be used.
      There is a  highly modified <a href="http://buildroot.uclibc.org/">buildroot</a>
      available for download from the
      <a href="http://sourceforge.net/project/showfiles.php?group_id=189573">NuttX SourceForge</a>
      page.
      This download may be used to build a NuttX-compatible ELF toolchain under Linux or Cygwin.
      That toolchain will support ARM, m68k, m68hc11, m68hc12, and SuperH ports.
      The buildroot SVN may be accessed in the 
      <a href="http://nuttx.svn.sourceforge.net/viewvc/nuttx/trunk/misc/buildroot/">NuttX SVN</a>.
    </p>
   </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Linux + GNU <code>make</code> + SDCC</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      Also very usable is the Linux environment using the 
      <a href="http://sdcc.sourceforge.net/">SDCC</a> compiler.
      The SDCC compiler provides support for the 8051/2, z80, hc08, and other microcontrollers.
      The SDCC-based logic is less well exercised and you will likely find some compilation
      issues if you use parts of NuttX with SDCC that have not been well-tested.
    </p>
   </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Cygwin + GNU <code>make</code> + GCC/binutils</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      This combination works well too.
      It works just as well as the native Linux environment except
      that compilation and build times are a little longer.
      The custom NuttX <a href="http://sourceforge.net/projects/nuttx/files/buildroot/">buildroot</a> referenced above may be build in
      the Cygwin environment as well.
    </p>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Cygwin + GNU <code>make</code> + SDCC</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
       I have never tried this combination, but it would probably work just fine.
    </p>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Cygwin + GNU <code>make</code> + Windows Native Toolchain</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      This is a tougher environment.
      In this case, the Windows native toolchain is unaware of the
      Cygwin <i>sandbox</i> and, instead, operates in the native Windows environment.
      The primary difficulties with this are:
    </p>
    <ul>
      <li>
        <b>Paths</b>.
        Full paths for the native toolchain must follow Windows standards.
        For example, the path <code>/home/my\ name/nuttx/include</code> my have to be
        converted to something like <code>'C:\cygwin\home\my name\nuttx\include'</code>
        to be usable by the toolchain.
      </li>
      <p>
        Fortunately, this conversion is done simply using the <code>cygpath</code> utility.
      </p>
      <li>
        <b>Symbolic Links</b>
        NuttX depends on symbolic links to install platform-specific directories in the build system.
        On Linux, true symbolic links are used.
        On Cygwin, emulated symbolic links are used.
        Unfortunately, for native Windows applications that operate outside of the
        Cygwin <i>sandbox</i>, these symbolic links cannot be used.
      </li>
      <p>
        The NuttX make system works around this limitation by copying the platform
        specific directories in place.
        These copied directories make work a little more complex, but otherwise work well.
      </p>
      <p><small>
        NOTE: In this environment, it should be possible to use the NTFS <code>mklink</code> command to create links.
        This should only require a minor modification to the build scripts (see <code>tools/winlink.sh</code> script).
      </small></p>
      <li>
        <b>Dependencies</b>
        NuttX uses the GCC compiler's <code>-M</code> option to generate make dependencies.  These
        dependencies are retained in files called <code>Make.deps</code> throughout the system.
        For compilers other than GCC, there is no support for making dependencies in this way.
        For Windows native GCC compilers, the generated dependencies are windows paths and not
        directly usable in the Cygwin make.  By default, dependencies are surpressed for these
        compilers as well.
      </li>
      <p><small>
        NOTE: dependencies are suppress by setting the make variable <code>MKDEPS</code> to point
        to the do-nothing dependency script, <code>tools/mknulldeps.sh</code>.
        Dependencies can be enabled for the Windows native GCC compilers by setting
        <code>MKDEPS</code> to point to <code>$(TOPDIR)/tools/mkdeps.sh --winpaths $(TOPDIR)</code>.
      </small></p>
    </ul>
    <p>
      <b>Supported Windows Native Toolchains</b>.
      At present, only the Zilog Z16F, z8Encore, and eZ80Acclaim ports use a non-GCC native Windows
      toolchain(the Zilog ZDS-II toolchain).
      Support for Windows native GCC toolchains (CodeSourcery and devkitARM) is currently implemented
      for the NXP LPC214x, STMicro STR71x, and Luminary LMS6918 ARM ports.
      (but could easily be extended to any other GCC-based platform with a small effort).
    </p>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Wine + GNU <code>make</code> + Windows Native Toolchain</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      I've never tried this one, but I off the following reported by an ez80 user using the ZiLOG ZDS-II Windows-native toolchain:
    </p>
    <blockquote>
      <p>
         &quot;I've installed ZDS-II 5.1.1 (IDE for ez80-based boards) on wine (windows emulator for UNIX) and to my surprise, not many changes were needed to make SVN snapshot of NuttX buildable...
         I've tried nsh profile and build process completed successfully.
         One remark is necessary: NuttX makefiles for ez80 are referencing <code>cygpath</code> utility.
         Wine provides similar thing called <code>winepath</code> which is compatible and offers compatible syntax.
         To use that, <code>winepath</code> (which itself is a shell script) has to be copied as <code>cygpath</code> somewhere in <code>$PATH</code>, and edited as in following patch:
       </p>
       <ul><pre>
# diff -u `which winepath` `which cygpath`
--- /usr/bin/winepath 2011-05-02 16:00:40.000000000 +0200
+++ /usr/bin/cygpath 2011-06-22 20:57:27.199351255 +0200
@@ -20,7 +20,7 @@
#

# determine the app Winelib library name
-appname=`basename "$0" .exe`.exe
+appname=winepath.exe

# first try explicit WINELOADER
if [ -x "$WINELOADER" ]; then exec "$WINELOADER" "$appname" "$@"; fi
</pre></ul>
      <p>
        &quot;Better solution would be replacing all <code>cygpath</code> references in  <code>Makefiles </code> with  <code>$(CONVPATH)</code> (or  <code>${CONVPATH}</code> in shell scripts) and setting <code>CONVPATH</code> to  <code>cygpath</code> or  <code>winepath</code> regarding to currently used environment.
      </p>
    </blockquote>
  </td>
</tr>

<tr>
  <td valign="top"><img height="20" width="20" src="favicon.ico"></td>
  <td bgcolor="#5eaee1">
    <b>Other Environments?
    Windows Native <code>make</code> + Windows Native Toolchain?</b>
  </td>
</tr>
<tr>
  <td><br></td>
  <td>
    <p>
      <b>Environment Dependencies</b>.
      The primary environmental dependency of NuttX are (1) GNU make,
      (2) bash scripting, and (3) Linux utilities (such as cat, sed, etc.).
      If you have other platforms that support GNU make or make
      utilities that are compatible with GNU make, then it is very
      likely that NuttX would work in that environment as well (with some
      porting effort). If GNU make is not supported, then some significant
      modification of the Make system would be required.
    </p>
    <p>
     <b>GNUWin32</b>.
      For example, with suitable make system changes, it should be possible to
      use native GNU tools (such as those from
      <a href="http://sourceforge.net/projects/gnuwin32/">GNUWin32</a>)
      to build NuttX.
      However, that environment has not been used as of this writing.
   </p>
      <p><small>
        NOTE: One of the members on the <a href="http://tech.groups.yahoo.com/group/nuttx/">NuttX forum</a>
        reported that they successful built NuttX using such a GNUWin32-based, Windows native environment.
        They reported that the only necessary change was to the use the NTFS mklink command to create links
        (see <code>tools/winlink.sh</code> script).
      </small></p>
  </td>
</tr>
</table></center>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="footprint"><h1>Memory Footprint</h1></a>
  </td>
  </tr>
</table>

<ul>
<p><b>C5471 (ARM7)</b>
  The build for this ARM7 target that includes most of the OS features and
  a broad range of OS tests.  The size of this executable as given by the
  Linux <tt>size</tt> command is (3/9/07):
</p>
<pre>
   text    data     bss     dec     hex filename
  53272     428    3568   57268    dfb4 nuttx
</pre>
<p><b>DM320 (ARM9)</b>
  This build for the ARM9 target includes a significant subset of OS
  features, a filesystem, Ethernet driver, full TCP/IP, UDP and (minimal)
  ICMP stacks (via uIP) and a small network test application: (11/8/07,
  configuration netconfig, apps/examples/nettest)
</p>
<pre>
   text    data     bss     dec     hex filename
  49472     296    3972   53740    d1ec nuttx
</pre>
<p>
  Another build for the ARM9 target includes a minimal OS feature
  set, Ethernet driver, full TCP/IP and (minimal) ICMP stacks, and
  a small webserver: (11/20/07, configuration uipconfig, apps/examples/uip)
</p>
<pre>
   text    data     bss     dec     hex filename
  52040      72    4148   56260    dbc4 nuttx
</pre>
<p><b>87C52</b>
  A reduced functionality OS test for the 8052 target requires only
  about 18-19K:
</p>
<pre>
Stack starts at: 0x21 (sp set to 0x20) with 223 bytes available.

Other memory:
   Name             Start    End      Size     Max
   ---------------- -------- -------- -------- --------
   PAGED EXT. RAM                         0      256
   EXTERNAL RAM     0x0100   0x02fd     510     7936
   ROM/EPROM/FLASH  0x2100   0x6e55   19798    24384
</pre>
</ul>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="licensing"><h1>Licensing</h1></a>
  </td>
  </tr>
</table>

<ul>
<p>
  NuttX is available under the highly permissive
  <a href="http://en.wikipedia.org/wiki/BSD_license">BSD license</a>.
  Other than some fine print that you agree to respect the copyright
  you should feel absolutely free to use NuttX in any environment and
  without any concern for jeopardizing any proprietary software that
  you may link with it.
</p>
</ul>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="history"><h1>Release History</h1></a>
  </td>
  </tr>
</table>

<ul>
<p>
   ChangeLog snapshots associated with the previous, current, and future release are available below.
</p>
</ul>

<center><table width ="80%">
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
   <td>
      <a href="ChangeLog.txt">Change logs for previous NuttX releases</a><br>
   </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
   <td>
      <a href="#currentrelease">ChangeLog for the current NuttX releases</a><br>
   </td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
   <td>
      <a href="#pendingchanges">Unreleased changes</a>
   </td>
</tr>
</table></center>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="currentrelease">ChangeLog for the Current Release</a>
  </td>
  </tr>
</table>

<ul><pre>
nuttx-6.21 2012-08-25 Gregory Nutt &lt;gnutt@nuttx.org&gt;

    * configs/lpc4330-xplorer/up_nsh.c:  Add support for a basic SPIFI block
      driver for use by NSH.  Does not work!  Crashes on first SPIFI write.
    * configs/lpc4330-xplorer/*/defconfig: Calibrate delay loops (this is
      based on the current &quot;slow&quot; 72MHz M4 clock and will need to be
      re-calibrated when this is increased).
    * configs/stm3220g-eval/include/board.h and configs/stm3240g-eval/include/board.h:
      The SDIOCLK frequency in the F2 and F4 derives for PLL48CLK and not HCLK
      so that the SDIOCLK input frequency should always be 48MHz.
    * sched/os_internal.h, sched_setupidlefiles.c, sched_setuptaskfiles.c, and
      sched_setupidlefiles.c:  Detangle some conditional compilation.  Allow for
      a perverse configuration that has socket descriptors and streams but no file
      descriptors (sure, why not?).
    * sched/: Stylistic clean-up of all files.  Some of these files are pretty old
      and do not follow current NuttX coding standards in detail.
    * fs/: More stylistic file clean-up.
    * mm/: More stylistic file clean-up.
    * drivers/ and drivers/serial/: More stylistic file clean-up.
    * arch/arm/src/lpc43xx/lpc43_clockconfig.c:  Fix PLL1 bit manipulation logic.
      Critical bugfix! This would often cause the LPC43xx to fail to boot.
    * arch/arm/src/lpc43xx/lpc43_rgu.c:  The soft reset logic called from the
      beginning of __start seems cause problems.  A magic delay seems to improve
      the logic some.  But I suspect that real fix is to get rid of all of the
      soft reset logic.  This would also be a critical bugfix if I believed
      that it really fixed all of the issues.
    * arch/arm/src/lpc43xx/chip/lpc43_cgu.h:  Fix a bit mask in the PLL1
      control register.  Critical bugfix.
    * arch/arm/src/lpc43xx/lpc43_clockconfig.c and configs/lpc4330-xplorer/include/board.h:
      Implement PLL1 ramp-up logic; Now the LPC43xx is running at 204MHz.
    * configs/lpc4330-xplorer/*/defconfig:  Re-calibrated delay loops using
      the 204MHz clock.  The LPC43xx ripping rips!  This calibration was performed
      with symbols enabled and all optimization disabled.  It will need to be
      better recalibrated again down the road.
    * arch/arm/src/stm32/stm32_exti.c:  Renamed to rch/arm/src/stm32/stm32_exti_gpio.c
      to make a little room in the file name space.
    * arch/arm/src/stm32/stm32_exti_alarm.c:  Add initial logic to attached the
      RTC alarm EXTI interrupt.  This is work be performed mostly by Diego Sanchez.
    * include/: More stylistic file clean-up.
    * arch/arm/src/lpc43xx/lpc43_spifi.c, lpc43_spifi.h, and chip/lpc43_spifi.h:  Add
      logic to configure and initialize the SPIFI device (does not yet work).
    * configs/lpc4330-xplorer/include/board.h:  Reduce SPI SCLK value.
    * arch/arm/src/lpc43xx/lpc43_spifi.c, lpc43_spifi.h, and chip/lpc43_spifi.h:
      Logic completely redesigned.  It now creates an MTD driver to access SPIFI...
      but the driver still does not work.
    * arch/arm/src/stm32 and arch/arm/include/stm32: Make name of RTC ALARM interrupt
      common on STM32 F1,2,4
    * arch/arm/src/stm32 and arch/arm/include/stm32: Add support for the
      STM32F100x &quot;Value Line&quot; devices. This includes changes to stm32F10xx_rcc.c that
      add the ability to run the chip off the internal oscillator.  There is no open
      board configuration for this part yet (the STM32VLDiscovery would be a candidate).
      Contributed by Mike Smith.
    * arch/arm/src/stm32: Fixed typos in conditional compilation in the CAN and DMA
      and some pin configuration.  This would have caused problems for STM32 F107xx.
      Typos noted by Mike Smith.
    * arch/arm/src/lpc43xx/lpc43_serial.c:  Add support for certain RS-485 features
    * lib/termios/lib_cfsetispeed.c, lib_cfsetospeed.c, lib_tcflush.c:  Add
      simple implementations of cfsetispeed(), cfsetospeed(), and tcflush().
    * include/sys/str_tty.h, lib/lib_setspeed.c, lib_getspeed.c, and lib_resetspeed.c:
      Add APIs to support setting non-standard BAUD values not supported by POSIX
      termios.  These are non-standard interfaces but have a precedence:  There are
      similar interfaces in AIX.
    * include/sys/str_tty.h, lib/lib_setspeed.c, lib_getspeed.c, and lib_resetspeed.c:
      Sigh... removed.  We don't need any more almost standard interfaces!  (SVN
      revision 4968 if you want the short-lived code).
    * include/termios.h and lib/termios/*:  Open the existing, standard termios
      interfaces to permit some non-standard baud settings.  The new termios definitions
      still supports the POSIX standard except that it does not strictly enforce
      baud rate settings, permitting some non-portable, but useful baud rate settings
      (this is what the short-lived AIX-like interfaces would have accomplished as well).
    * include/termios.h and lib/termios/*:  Redesigned yet again (this is getting
      painful.  NuttX now supports the BOTHER baud setting just as Linux does.  termios
      Bxxx definitions are again encoded; cf[set|get][o|i]speed now deal with only the
      encoded values.  If the encoded baud is set to BOTHER, then the values in the (non-
      standard) c_ispeed and c_ospeed baud values may be accessed directly.
    * arch/arm/src/stm32/stm32_serial.c:  Add minimal termios support for the STM32
      (BOTHER style baud settings only).  Contributed by Mike Smith.
    * configs/lpc4343-xplorer/src:  Clean up SPIFI-library based build to that it
      actually works.
    * arch/arm/src/lpc43xx/lpc43_spifi.c:  Add support for verification to writes.
      Add debug option to dump buffers.  Several bugfixes... almost works.
    * include/termios.h, lib/termios/*, and arch/arm/src/stm32/stm32_serial.c: :
      BOTHER is gone again.
    * arch/arm/src/stm32/stm32_sdio.c and chip/stm32f20xx_pinmap.h:  STM32 F2 SDIO
      fixes from Gary Teravskis and Scott Rondestvedt.
    * include/termios.h and lib/termios/*:  Replace cfsetispeed and cfsetospeed with
      cfsetspeed (with definitions for the input/outputs in termios.h).
    * configs/stm32f4discovery/src and configs/stm32f4discovery/pm:  Add a power
      management configuration for the STM32F4Discovery and supporting logic.  This
      check-in also includes some fixes for the F4 RTC alarm logic.
    * drivers/input/pga11x.c and include/nuttx/input/pga11x.h:  Add support for the
      TI PGA112/3/6/7 amplifier/multiplexer parts.
    * configs/mirtoo/README.txt, nsh/defconfig, and nxffs/defconfig:  Add support
      for the PGA117 on the Mirtoo module.
    * drivers/analog/pga11x.c and include/nuttx/analog/pga11x.h:  These belong in
      the analog subdirectories, not input.
    * configs/compal_e99/src/ssd1783.c and /ssd1783.h:  Drivers for the SSD1783
      LCD found in the Motorola C155 telephone.  The driver is specific to the C155
      because it uses the uwire transport.  Contributed by Denis Carilki and
      Alan Carvalho de Assis.
    * drivers/power/pm_changestate.c.  Correct a case where interrupts were not
      being re-enabled.  Found by Diego Sanchez.
    * configs/mirtoo/nxffs/defconfig:  This Mirtoo NXFFS configuration now uses the
      open Pinguino toolchain by default.  This is necessary because the free C32
      toolchain does not support any optimization and the unoptimized NXFFS image
      hits the PIC32MX2 FLASH size (128K).  There is plenty of room to grow using
      the Pinguino toolchain with -O2 optimization.
    * configs/mirtoo/src/up_adc.c.  This is just a stub for now, but this is
      where Mirtoo ADC logic will eventually need to go.
    * arch/mips/src/pic32mx/pic32mx-gpio.c:  Now supports the PIC32MX1/2 ANSEL
      IOPORT register.
    * lib/string/lib_memchr.c:  Add support for memchr() (contributed by Mike Smith)
    * lib/string/lib_memccpy.c:  Add support for memccpy()
    * arch/arm/src/lpc17xx/lpc17_serial.c:  Now supports ioctl commands to change
      the baud using tcsetattr() (contributed by Chris Taglia).
    * arch/*/src/*_serial.c: Fix ioctl method return values.  These methods
      should return a negated errno value; they should not set the errno
      variable.
    * sched/on_exit.c, sched/task_exithook.c, and include/nuttx/sched.c:  Add
      support for multiple registered on_exit() functions if CONFIG_SCHED_ONEXIT_MAX
      is defined.
    * drivers/syslog/ramlog.c: Move the RAM SYSLOG device into drivers/syslog
      so that it will be in the same directory as some new SYSLOGing devices
      in the works.
    * include/nuttx/syslog.h and drivers/syslog/ramlog.c:  The SYSLOG putc function
      now has a common name that is independent of the device that provides the
      SYSLOG.
    * include/nuttx/syslog.h and drivers/syslog/syslog.c:  This is a new, generic
      SYSLOG device that can redirect debug output to any character device or file.
      So you can log debug output to a file or you can put the console on /dev/ttyS0
      and the debug output on /dev/ttyS1.
    * arch/arm/src/lpc43xxl/lpc43_spifi.c: Correct an addressing error in the LPC43
      SPIFI MTD driver
    * drivers/syslog/syslog.c and fs/fs_syslog.c:  Moved the generic syslog logic
      from drivers/syslog to fs/ where is belongs.  Especially after realizing that
      the syslog logic is going to have to some internal FS operations in order
      to realize a totally thread-independent SYSLOG interface.
    * arch/arm/src/stm32/stm32*_rcc.c and .h:  If CONFIG_PM is defined, add a
      function called stm32_clockenable() that can be used by PM logic to re-start
      the PLL after re-awakening from deep sleep modes.
    * fs/fs_foreachinode.c and fs/fs_foreachmountpoint.c:  Add logic to traverse
      inodes and mountpoints in the NuttX pseudo-file system.
    * fs/fat/fs_fat32.c: Max. filename length reported by statfs() was wrong
      if FAT long file names were enabled.
    * lib/stdio/lib_libvsprintf.c:  Fieldwidth and justification were not
      supported for the %s format.  As a result, %s, %12s, and %-12s all
      produced the same output.
    * lib/stdio/lib_libdtoa.c:  Fix several issues with presenting floating
      point numbers (conversions are fine, but presentation was bad).  This
      is a critical bug fix if you use printf or sprintf to deal with floating
      point numbers.
    * lib/stdio/lib_libdtoa.c and lib_libvsprintf.c:  Correct some floating
      point options.
    * arch/arm/lpc43xx/lpc32_usb0dev.c:  Add framework for development of
      an USB0, device-side driver for the LPC43XX.  The initial check-in,
      however, is simply for the LPC31xx driver with name changes.  The
      LPC31xx has the same USB IP, but will require some additional initialization
      (and lots of testing) before it can be used with the LPC43xx.
    * nuttx/Documentation/NuttShell.html:  Added a section covering ways to
      customize the behavior of NSH.
    * arch/arm/src/stm32/chip/stm32f1*_pinmap.h: STM32 CAN TX/RX pins reversed;
      inconsistent conditional compilation.  Reported by Max Holtzberg.
    * arch/arm/*/stm32:  Add support for STM32 F107 &quot;Connectivity Line&quot; 
      Ethernet (contributed by Max Holtzberg).
    * configs/olimex-stm32-p107:  Add board support for the Olimiex STM32-P107
       board (contributed by Max Holtzberg).
    * arch/arm/src/stm32/stm32f2xx_dma.c, stm32f4xx_dma.c, stm32_serial.c, and
      stm32_spic.c:  DMA priority was getting zeroed by STM32 F2/F4 DMA drivers
      so that all DMAs ran at the lowest priority.
    * configs/stm3240g-eval/include/board.h and configs/stm3220:  Drop SD card
      frequency from 24 to 16 MHz.  Apparently 24 MHz is too fast for the board.
      This (plus the change to the STM32 DMA (above) fixes SDIO DMA on the
      STM3240G-EVAL (and probably STM3220G-EVAL -- untested).
    * arch/arm/src/stm32/stm32f2xx_dma.c and stm32f4xx_dma.c: Backed out the
      DMA priority change just above.  The reduced SD card frequency was
      necessary and sufficient to resolve the problem.
    * drivers/serial/serial.c:  open, read, write, and poll methods may now
      abort return EINTR (or a short transfer size) if a signal is received
      while waiting to receive or send serial data.  This behavior is required
      by POSIX.
    * include/sys/types.h:  Define NULL to be (0) if __cplusplus is defined.
      (contributed by Mike Smith)
    * include/ctype.h: Remove a stray semi-colon in a definitions (Thanks
      Mike Smith).
    * configs/.../Make.defs.  Fix C++ include path set-up in Make.defs file
      for all 8-bit AVR platforms (Thanks Richard Cochran).
    * lib/stdio/lib_*stream.c:  Revised to handle new error return values from
      serial.c.
    * arch/arm/src/stm32/stm32_spi.c:  SPI driver can now service re-
      initialization (Mike Smith).
    * tools/mkconfig.c:  If CONFIG_DRAM_END is not specified, this tool
      will provide default definition of (CONFIG_DRAM_START + CONFIG_DRAM_SIZE)
    * arch/arm/src/stm32/stm32_otgfshost.c:  Renamed from stm32_usbhost.c.
      This is nearly code complete and, with any luck, will be available
      in NuttX-6.21.
    * configs/*/defconfig:  Update all defconfig files to remove syntax
      that is incompatible with the mconf configuration tool.
    * arch/arm/src/stm32/stm32_otgfshost.c:  This driver now appears to be
      functional (although more testing is necesary).

apps-6.21 2012-08-25 Gregory Nutt &lt;gnutt@nuttx.org&gt;

    * apps/include/: Stylistic clean-up of all header files.
    * apps/modbus and apps/include/modbus:  A port of freemodbus-v1.5.0
      has been added to the NuttX apps/ source tree.
    * apps/examples/modbus:  A port of the freemodbus-v1.5.0 &quot;demo&quot;
      program that will be used to verify the FreeModBus port
    * apps/modbus:  Don't use strerror().  It is just too big.
    * apps/modbus:  Add CONFIG_MB_TERMIOS.  If the driver doesn't support
      termios ioctls, then don't bother trying to configure the baud, parity
      etc.
    * apps/nshlib:  If waitpid() is supported, then NSH now catches the
      return value from spawned applications (provided by Mike Smith)
    * apps/nshlib:  Lock the scheduler while starting built-in applications
      in order to eliminate race conditions (also from Mike Smith).
    * apps/examples/adc, pwm, and qencoder:  Add support for testing
      devices with multiple ADC, PWM, and QE devices.
    * apps/nshlib/nsh_mntcmds.c:  Separated mount-related commands out of
      nsh_fscmds.c.  Extended to the mount command so that if no arguments
      are provided, then the current mountpoints are enumerated.
    * apps/nshlib/nsh_mntcmds.c:  Add an NSH df command to list the
      properties of mounted file systems.
    * apps/nshlib/nsh_parse.c:  Extend help command options.  'help' with
      no arguments outputs a short list of commands.  With -v lists all
      command line details.  A command name can be added to just get
      help on one command.
    * system/readline.c:  If character input/output is interrupted by a
      signal, then readline() will try the read/write again.
    * apps/*/Make.defs:  Numerous fixes needed to use the automated
      configuration (from Richard Cochran).

NxWidgets-1.2 2012-06-15 Gregory Nutt &lt;gnutt@nuttx.org&gt;

    * NXWidgets::CCallback: callback arguement is now type CCallback and not
      CWidgetControl;  Added a method to redirect keyboard contacts to either
      the widgets in the window (via CWidgetControl) or to an NxConsole (via
      nxcon_kbdin()).
    * NXWidgets::INxWindow, CBgWindow, CNxTkWindow, CNxToolbar, CNxWindow:
      Now pass the CCallback intances as the callback argument instead of
      the CWidgetControl instance.  New method redirectNxConsole() will
      support redirection of any window keyboard input to the NxConsole
      (via CCallback).
    * NxWM:CNxConsole:  Configures the NxConsole window to redirection keyboard
      input to the NxConsole; redirects standard input to the NxConsole
      device driver.
    * NxWM:CKeyboard:  Add a new class that implements a keyboard listener
      thread.  This thread reads from /dev/console and injects the keyboard
      input into NX.  NX will determine which window is at the top of the
      heirarchy and re-direct the keyboard input to only that top window.
      This solves an important problem with, for example, running multiple
      copies of the NxConsole:  On the copy of the NxConsole at the top of
      the heirarchy should get the keyboard input.
    * UnitTests/nxwm/main.cxx: Now starts the keyboard thread if
      CONFIG_NXWM_KEYBOARD is defined.
    * NxWM::CTaskbar:  After drawing the task bar, need to raise the
      application window otherwise the taskbar will be on the top and
      keyboard input will not be received by the top application.
    * NxWM::CTaskbar:  Bugfix... previous window should not be minimized
      when a new window is started.  It should stay in a maximized state
      so that it will re-appear with the window above it is closed or
      minimized.
    * NxWM::CHexCalculator:  Add a hexadecimal/decimal calculator
      example.
    * NXWidgets::CNxTkWindow:  Back out height adjustment in the getSize()
      method.  The code was correct as it was before.
    * NXWidgets::CButtonArray and NXWidgets::CGraphicsPort:  There is
      a kludge in there to handle the case where we cannot read the
      background data because the LCD does not support read operations.
      In that case, we just use the default background color.  However,
      that doesn't work either for the case where the background color
      changes when the widget is selected.  Then the background color
      in the font is wrong.  Fixed in CButtonArrary, but the problem
      probably exists in other places as well.
    * NxWM:  Increase default spacing of icons on the Start Window.
    * NxWM::CHexCalculator:  Fix some non-standard calculator behavior
      after = is pressed.  Use upper case hex.  Increase font size.
    * nxwm/Makefile:  Fix error that creapt in during some other
      recent check-ins.

pascal-3.0 2011-05-15 Gregory Nutt &lt;gnutt@nuttx.org&gt;

    * nuttx/:  The Pascal add-on module now installs and builds under the
      apps/interpreters directory.  This means that the pascal-2.1 module is
      incompatible with will all releases of NuttX prior to nuttx-6.0 where the 
      apps/ module was introduced.

buildroot-1.10 2011-05-06 &lt;gnutt@nuttx.org&gt;

    * Add patch submitted by Dimiter Georgiev to work around problems in building
      GDB 6.8 with versions of Cygwin &gt; 1.7.
    * configs/i486-defconfig-4.3.3 - Builds an i486 cross development toolchain
      using gcc 4.3.3.  Why wouldyou want such a thing?  On Linux, of course,
      such a thing is not needed because you can use the installed GCC to build
      i486 ELF binaries.  But that will not work under Cygwin!  The Cygwin
      toolchain (and probably MinGW), build DOS MZ format executables (i.e.,
      .exe files).  That is probably not usable for most NuttX targets.
      Instead, you should use this i486-elf-gcc to generate true ELF binaries
      under Cygwin.
    * Makefile - Alter copy arguments to avoid permissions problems when
      copying NuttX header files.
    * toolchain/nxflat/nxflat.mk and Makefile - Fix include paths.
    * toolchain/gcc/3.3.6 - Added a patch to fixed compilation error on Ubuntu
      9.10.
    * toolchain/nxflat/Makefile - Correct static library link order.
    * configs/arm920t-defconfig-4.3.3 - Enable support for NXFLAT tools.
    * toolchain/binutils/2.21 and toolchain/gcc/4.5.2 - Add support for GCC
      4.5.2 with binutils 2.21.
    * configs/arm920t-eabi-defconfig-4.5.2 - Add a configuration to build a
      GCC 4.5.2 EABI ARM toolchain for the ARM920t.
</pre></ul>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="pendingchanges">Unreleased Changes</a>
  </td>
  </tr>
</table>

<ul>
  <li><b>nuttx-6.18</b>.
    The ChangeLog for the not-yet-released version 6.18 is available at the bottom of the ChangeLog file that can viewed in the <a href="http://nuttx.svn.sourceforge.net/viewvc/nuttx/trunk/nuttx/ChangeLog?view=log">SourceForge SVN</a>.
  </li>
  <li><b>apps-6.18</b>.
    The ChangeLog for the not-yet-released version 6.18 is available at the bottom of the ChangeLog file that can viewed in the <a href="http://nuttx.svn.sourceforge.net/viewvc/nuttx/trunk/apps/ChangeLog.txt?view=log">SourceForge SVN</a>.
  </li>
  <li><b>NxWidgets-1.1</b>.
    The ChangeLog for the not-yet-released version 1.1 is available at the bottom of the ChangeLog file that can viewed in the <a href="http://nuttx.svn.sourceforge.net/viewvc/nuttx/trunk/NxWidgets/ChangeLog?view=log">SourceForge SVN</a>.
  </li>
  <li><b>pascal-1.1</b>.
    The ChangeLog for the not-yet-released version 1.1 is available at the bottom of the ChangeLog file that can viewed in the <a href="http://nuttx.svn.sourceforge.net/viewvc/nuttx/trunk/misc/pascal/ChangeLog?view=log">SourceForge SVN</a>.
  </li>
  <li><b>buildroot-1.11</b>.
    The ChangeLog for the not-yet-released version 1.11 is available at the bottom of the ChangeLog file that can viewed in the <a href="http://nuttx.svn.sourceforge.net/viewvc/nuttx/trunk/misc/buildroot/ChangeLog?view=log">SourceForge SVN</a>.
  </li>
</ul>

<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="TODO"><h1>Bugs, Issues, <i>Things-To-Do</i></h1></a>
  </td>
  </tr>
</table>

<ul>
<p>
   The current list of NuttX <i>Things-To-Do</i> in SVN <a href="http://nuttx.svn.sourceforge.net/viewvc/nuttx/trunk/nuttx/TODO?view=log">here</a>.
   A snapshot of the <i>To-Do</i> list associated with the current release are available <a href="TODO.txt">here</a>.
</p>
</ul>
<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="documentation"><h1>Other Documentation</h1></a>
  </td>
  </tr>
</table>

<ul><table>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttXGettingStarted.html">Getting Started</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttXUserGuide.html">User Guide</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttXPortingGuide.html">Porting Guide</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttShell.html">NuttShell (NSH)</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttXNxFlat.html">NXFLAT</a> Binary Format</td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NXGraphicsSubsystem.html">NX Graphics Subsystem</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NxWidgets.html">NxWidgets</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="NuttXDemandPaging.html">Demand Paging</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="README.html">NuttX README Files</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="ChangeLog.txt">Change Log</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="TODO.txt">To-Do List</a></td>
</tr>
<tr>
  <td valign="top" width="22"><img height="20" width="20" src="favicon.ico"></td>
  <td><a href="UsbTrace.html">USB Device Driver Tracing</a></td>
</tr>
</center></ul>

<small>
<table width ="100%">
  <tr bgcolor="#e4e4e4">
  <td>
    <a name="trademarks"><h1>Trademarks</h1></a>
  </td>
  </tr>
</table>
<ul>
  <li>ARM, ARM7 ARM7TDMI, ARM9, ARM920T, ARM926EJS Cortex-M3 are trademarks of Advanced RISC Machines, Limited.</li>
  <li>Cygwin is a trademark of Red Hat, Incorporated.</li>
  <li>Linux is a registered trademark of Linus Torvalds.</li>
  <li>Eagle-100 is a trademark of <a href=" http://www.micromint.com/">Micromint USA, LLC</a>.
  <li>LPC2148 is a trademark of NXP Semiconductors.</li>
  <li>TI is a tradename of Texas Instruments Incorporated.</li>
  <li>UNIX is a registered trademark of The Open Group.</li>
  <li>VxWorks is a registered trademark of Wind River Systems, Incorporated.</li>
  <li>ZDS, ZNEO, Z16F, Z80, and Zilog are a registered trademark of Zilog, Inc.</li>
</ul>
<p>
  NOTE: NuttX is <i>not</i> licensed to use the POSIX trademark.  NuttX uses the POSIX
  standard as a development guideline only.
</p>
</small>

</body>
</html>