Mirrors_Framework/nuttx
1
0
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2026-06-06 00:14:22 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Update README

Browse Source
This commit is contained in:
Gregory Nutt
2016-07-14 10:10:37 -06:00
parent 76f12b1f69
commit e42e3bd58c
1 changed files with 14 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
configs/freedom-k64f/README.txt
+14 -5
View File
@@ -911,9 +911,14 @@ Status
2016-07-11: Received hardware today and the board came up on the very 2016-07-11: Received hardware today and the board came up on the very
first try. That does not happen often. At this point, the very basic first try. That does not happen often. At this point, the very basic
NSH configuration is working and LEDs are working. The only odd NSH configuration is working and LEDs are working.
behavior that I see is that pressing SW3 causes an unexpected interrupt
error. The only odd behavior that I see is that pressing SW3 causes an NMI
interrupt (followed by a crash):
kinetis_nmi: PANIC!!! NMI received
I don't yet understand why this is.
2016-07-12: Added support for the KSZ8081 PHY and added the netnsh 2016-07-12: Added support for the KSZ8081 PHY and added the netnsh
configuration. The network is basically functional. More testing is configuration. The network is basically functional. More testing is
@@ -929,6 +934,10 @@ Status
yet work. The basic problem seems to be that it does not sense the yet work. The basic problem seems to be that it does not sense the
presence of the SD card on PTE6. No interrupts are generated when the presence of the SD card on PTE6. No interrupts are generated when the
SD card is inserted or removed. You might want to disable SDHC and SD card is inserted or removed. You might want to disable SDHC and
MMC/SD if you are using MMC/SD if you are using this configuration.
this configuration.
The nsh configuration now builds successfully with USB device enabled.
USB device, however, has not yet been tested. I have not yet looked
into 48MHz clocking requirements.