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

Update comments and README

Browse Source
This commit is contained in:
Gregory Nutt 2015-04-05 07:22:46 -06:00
parent 23d4d23958
commit 0d361dc4be
3 changed files with 53 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
configs/samv71-xult/README.txt
View File

@ -111,6 +111,18 @@ The BASIC nsh configuration is fully function (as desribed below under
sample code and study of the data sheet, but I have not found the key to
solving this.
6. Partial support for the maXTouch Xplained Pro LCD is in place. The
ILI9488-based LCD is working well with a SMC DMA-based interface. Very
nice performance.
However, the maXTouch touchscreen driver is not working. I tried re-
using the maXTouch driver that was used with the SAMA5D4-EK TM7000
LCD, but the maXTouch Xplained Pro has a different maXTouch part.
The driver claims that all operations are success, but there are no
interrupts signalling touch event. I assume that the different
maXTouch part is not being configured correctly but there is no
avaiable technical documentation or sample code to debug with.
Serial Console
==============
@ -1134,9 +1146,23 @@ Configuration sub-directories
CP2100CP programmable PLL, and 0x57 and 0x5f are the addresses of
the AT2 EEPROM. I am not sure what the other address, 0x37, is).
8. Support for the touchscreen test is enabled (see apps/examples/touchscreen),
however, the maXTouch is not yet working (see STATUS below).
STATUS:
2015-03-30: Currently contains on a touchscreen test. The touchscreen
does not yet work.
2015-04-05: Partial support for the maXTouch Xplained Pro LCD is in
place. The ILI9488-based LCD is working well with a SMC DMA-based
interface. Very nice performance.
However, the maXTouch touchscreen driver is not working. I tried
re-using the maXTouch driver that was used with the SAMA5D4-EK
TM7000 LCD, but the maXTouch Xplained Pro has a different maXTouch
part. The driver claims that all operations are success, but
there are no interrupts signalling touch event. I assume that the
different maXTouch part is not being configured correctly but there
is no available technical documentation or sample code to debug
with.
netnsh:

38
configs/samv71-xult/src/sam_boot.c
View File

@ -1,4 +1,4 @@
/************************************************************************************
/****************************************************************************
* configs/samv71-xult/src/sam_boot.c
*
* Copyright (C) 2015 Gregory Nutt. All rights reserved.
@ -31,11 +31,11 @@
* ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
* POSSIBILITY OF SUCH DAMAGE.
*
************************************************************************************/
****************************************************************************/
/************************************************************************************
/****************************************************************************
* Included Files
************************************************************************************/
****************************************************************************/
#include <nuttx/config.h>
@ -45,35 +45,37 @@
#include <arch/board/board.h>
#include "up_arch.h"
#include "sam_start.h"
#include "samv71-xult.h"
/************************************************************************************
/****************************************************************************
* Pre-processor Definitions
************************************************************************************/
****************************************************************************/
/************************************************************************************
/****************************************************************************
* Private Functions
************************************************************************************/
****************************************************************************/
/************************************************************************************
/****************************************************************************
* Public Functions
************************************************************************************/
****************************************************************************/
/************************************************************************************
/****************************************************************************
* Name: sam_boardinitialize
*
* Description:
* All SAM3U architectures must provide the following entry point. This entry point
* is called early in the initialization -- after all memory has been configured
* and mapped but before any devices have been initialized.
* All SAMV7 architectures must provide the following entry point. This
* entry point is called early in the initialization -- after clocking and
* memory have been configured but before caches have been enabled and
* before any devices have been initialized.
*
************************************************************************************/
****************************************************************************/
void sam_boardinitialize(void)
{
#ifdef CONFIG_SAMV7_SDRAMC
/* Configure SDRAM if it has been enabled in the NuttX configuration. Here we
* assume, of course, that we are not running out SDRAM.
/* Configure SDRAM if it has been enabled in the NuttX configuration.
* Here we assume, of course, that we are not running out SDRAM.
*/
sam_sdram_config();
@ -113,7 +115,7 @@ void sam_boardinitialize(void)
* If CONFIG_BOARD_INITIALIZE is selected, then an additional
* initialization call will be performed in the boot-up sequence to a
* function called board_initialize(). board_initialize() will be
* called immediately after up_intiialize() is called and just before the
* called immediately after up_intitialize() is called and just before the
* initial application is started. This additional initialization phase
* may be used, for example, to initialize board-specific device drivers.
*

8
configs/samv71-xult/src/sam_sdram.c
View File

@ -90,9 +90,11 @@
* None
*
* Assumptions:
* The DDR memory regions is configured as strongly ordered memory. When
* we complete initialization of SDRAM and it is ready for use, we will
* make DRAM into normal, cached memory.
* This test runs early in initialization before I- and D-caches are
* enabled.
*
* NOTE: Since the delay loop is calibrate with caches in enabled, the
* calls to up_udelay() are wrong ty orders of magnitude.
*
****************************************************************************/