sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update some README files.

Browse Source
This commit is contained in:
Gregory Nutt 2017-11-13 15:49:38 -06:00
parent f3cac38ed6
commit 13b742236d
3 changed files with 23 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Documentation/README.html
View File

@ -8,7 +8,7 @@
<tr align="center" bgcolor="#e4e4e4">
<td>
<h1><big><font color="#3c34ec"><i>NuttX README Files</i></font></big></h1>
<p>Last Updated: November 6, 2017</p>
<p>Last Updated: November 13, 2017</p>
</td>
</tr>
</table>
@ -285,6 +285,7 @@ nuttx/
| |- stm32f411e-disco/
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f411e-disco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm32f429i-disco/
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f429i-disco/fb/README.txt" target="_blank"><b><i>fb/README.txt</i></b></a>
| | |- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f429i-disco/ide/ltcd/uvision/README.txt" target="_blank"><b><i>ide/ltcd/uvision/README.txt</i></b></a>
| | `- <a href="https://bitbucket.org/nuttx/nuttx/src/master/configs/stm32f429i-disco/README.txt" target="_blank"><b><i>README.txt</i></b></a>
| |- stm32f746g-disco/

1
README.txt
View File

@ -1827,6 +1827,7 @@ nuttx/
| |- stm32f411e-disco/
| | `- README.txt
| |- stm32f429i-disco/
| | |- fb/README.txt
| | |- ide/ltcd/uvision/README.txt
| | `- README.txt
| |- stm32f746g-disco/

36
configs/stm32f429i-disco/fb/README.txt
View File

@ -4,23 +4,25 @@ README.txt
STM32F429I-DISCO LTDC Framebuffer demo example
Configure and build
-----------------------------------------------
-------------------
cd tools
./configure -a <appdir> stm32f429i-disco/ltdc
./configure -a <appdir> stm32f429i-disco/fb
cd ..
make
Note!
In the current implementation the DMA2D driver only supports clut pixel format
if the LTDC driver it does. Otherwise it will not be compatible with the nx
framework. If CONFIG_FB_CMAP is configured, nx expects that any pixel format
if the LTDC driver it does. Otherwise it will not be compatible with the NX
framework. If CONFIG_FB_CMAP is configured, NX expects that any pixel format
supports color lookup tables. This is also the case for non CLUT formats e.g.
FB_FMT_RGB16_565. This may result in wrong color representation by nx if the
FB_FMT_RGB16_565. This may result in wrong color representation by NX if the
pixel format is unequal to FB_FMT_RGB8.
On the other hand layers with CLUT pixel format are not supported by the DMA2D
controller, in the case they will be used as destination layer for the following
operations:
- blit
- blend
- fillarea
@ -29,21 +31,23 @@ To enable clut support in both LTDC and DMA2D driver the following
configurations are valid:
1.
- Enable LTDC_INTERFACE and LAYER1/LAYER2
- Layer1 FB_FMT_RGB8
- Layer2 any non clut format
But Layer2 can only be used as destination layer for dma2d operations above.
This configuration is not compatibly to nx because LAYER2 will be referenced
This configuration is not compatibly to NX because LAYER2 will be referenced
by up_fbgetvplane and is an invalid CLUT pixel format.
2.
- Enable LTDC_INTERFACE and LAYER1/LAYER2
- Layer2 FB_FMT_RGB8
- Layer1 any non clut format
But Layer1 can only be used as destination layer for dma2d operations above.
This configuration should be compatibly to nx because LAYER2 will be referenced
This configuration should be compatibly to NX because LAYER2 will be referenced
by up_fbgetvplane and is an valid CLUT pixel format.
All other non clut configuration work fine.
@ -54,17 +58,17 @@ specific configuration.
Loading
-----------------------------------------------
-------
st-flash write nuttx.bin 0x8000000
Executing
-----------------------------------------------
The ltdc is initialized during boot up.
Interaction with NSH is via the serial console at 115200 8N1 baud.
From the nsh comandline execute one (or both) of the examples:
- nx (default nx example)
- ltdc (trivial ltdc interface test)
---------
Note! The ltdc example ends in an infinite loop. To get control of the nsh
start this example in the background with 'ltdc &'.
The ltdc is initialized during boot up. Interaction with NSH is via the serial
console at 115200 8N1 baud. From the nsh comandline execute the fb example:
nsh> fb
The test will put a pattern of concentric squares in the framebuffer and terminate.