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

Update README files

Browse Source
This commit is contained in:
Gregory Nutt 2014-09-19 10:12:03 -06:00
parent 942aaf6c31
commit ae7b19921d
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
configs/sama5d4-ek/README.txt
View File

@ -4831,8 +4831,8 @@ To-Do List
a) With a logic analyzer I can see that the I2C writes to the WM8904
device look good. This is the same setup that was used in the working
SAMA5D3x-EK nxplayer configuration and so should be correct (you cannot
even get this far on the Rev C board).
SAMA5D3x-EK nxplayer configuration and so should be correct (you
cannot even get this far on the Rev C board).
b) I2C readback of the WM8904 registers (via CONFIG_WM8904_REGDUMP) does
not, however, show proper registers contents. Groups of extra bits
(apparently 0x01fd) appear to be set in many registers on reading.
@ -4842,9 +4842,9 @@ To-Do List
before anything has been written to it.
c) Also with the logic analyzer, I can that the 12MHz MCLK input is
being provided to the WM8904.
d) However, not bit clock (BLCK) is being generated by the WM8904. This
should appear on both AUDIO_TK0_PB27 and AUDIO_RK0_PB28, but I see
nothing.
d) However, no bit clock (BLCK) is being generated by the WM8904. This
should appear on both AUDIO_TK0_PB27 and AUDIO_RK0_PB28, but I do not
see a clock on these pins.
e) With no BCLK, I would expect the SSC0 DMA transfers to hang... they do
not. No errors of any kind are detected by the firmware; it believes
that it is successfully playing .WAV files. This leads to believe

4
configs/stm3240g-eval/README.txt
View File

@ -995,11 +995,11 @@ Where <subdir> is one of the following:
CONFIG_ARMV7M_TOOLCHAIN_CODESOURCERYW=y : CodeSourcery under Windows
CONFIG_CXX_NEWLONG=n : size_t is unsigned int (maybe?)
3. In addition to the the kernel mode build, this NxWM configuration
3. In addition to the protected mode build, this NxWM configuration
differences from the nxwm configuration in that:
a. Networking is disabled. There are issues with some of the network-
related NSH commands and with Telnet in the kernel build (see the
related NSH commands and with Telnet in the protected build (see the
top-level TODO file). Without these NSH commands, there is no use
for networking in this configuration.