forked from nuttx/nuttx-update
f66c4a0733
I think the guy who wants to port NuttX is expected to understand NuttX kernel code and related configurations, but the getting enough knowledge needs to read the kernel codes deeply. To reduce the time for NuttX beginner who wants to port, I tried to make the guide (how to port) based on my porting journey.
59 lines
No EOL
1.2 KiB
ReStructuredText
59 lines
No EOL
1.2 KiB
ReStructuredText
.. todo::
|
|
Create "tutorial" type documentation for specific subjects not to be covered in more general terms.
|
|
|
|
======
|
|
Guides
|
|
======
|
|
|
|
.. toctree::
|
|
nfs.rst
|
|
usbtrace.rst
|
|
simulator.rst
|
|
qemugdb.rst
|
|
rndis.rst
|
|
drivers.rst
|
|
tasktrace.rst
|
|
cpp_cmake.rst
|
|
pysimcoder.rst
|
|
customboards.rst
|
|
customapps.rst
|
|
citests.rst
|
|
zerolatencyinterrupts.rst
|
|
kasan.rst
|
|
nestedinterrupts.rst
|
|
cortexmhardfaults.rst
|
|
coredump.rst
|
|
coresight.rst
|
|
gdbserver.rst
|
|
gdbwithpython.rst
|
|
ofloader.rst
|
|
testingtcpip.rst
|
|
automounter.rst
|
|
stm32nullpointer.rst
|
|
stm32ccm.rst
|
|
stackrecord.rst
|
|
etcromfs.rst
|
|
thread_local_storage.rst
|
|
devicetree.rst
|
|
debuggingflash_nuttxonarm.rst
|
|
changing_systemclockconfig.rst
|
|
usingkernelthreads.rst
|
|
armv7m_runtimestackcheck.rst
|
|
disabling_stackdumpdebug.rst
|
|
include_files_board_h.rst
|
|
specialstuff_in_nuttxheaderfiles.rst
|
|
kernel_threads_with_custom_stacks.rst
|
|
versioning_and_task_names.rst
|
|
logging_rambuffer.rst
|
|
mte.rst
|
|
ipv6.rst
|
|
integrate_newlib.rst
|
|
protected_build.rst
|
|
platform_directories.rst
|
|
port_drivers_to_stm32f7.rst
|
|
semihosting.rst
|
|
renode.rst
|
|
signal_events_interrupt_handlers.rst
|
|
signaling_sem_priority_inheritance.rst
|
|
smaller_vector_tables.rst
|
|
port.rst |