You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by "xiaoxiang781216 (via GitHub)" <gi...@apache.org> on 2026/03/23 15:28:25 UTC
[PR] boards/arm/tiva/lm3s6965-ek: fix qemu-protected and add board documentation [nuttx]
xiaoxiang781216 opened a new pull request, #18586:
URL: https://github.com/apache/nuttx/pull/18586
## Summary
* Fix several issues preventing the lm3s6965-ek qemu-protected build from booting in QEMU.
* Add board documentation for the Stellaris LM3S6965 Evaluation Kit.
**Commit 1: boards/arm/tiva/lm3s6965-ek: fix qemu-protected to boot in QEMU**
Fix several issues preventing the protected build from booting:
- memory.ld: Increase ksram from 16K to 20K to accommodate kernel BSS and idle thread stack. Rebalance usram to 20K and xsram to 24K accordingly.
- defconfig: Remove CONFIG_FS_TMPFS to reduce kernel binary size so it fits within the 128KB kflash partition.
- defconfig: Add CONFIG_TLS_LOG2_MAXSTACK=11 to reduce TLS stack alignment from 8K to 2K. The default 8K alignment caused memalign(8192, 2048) to request 18K (size + 2*alignment) from the user heap, failing the init task stack allocation.
**Commit 2: Documentation/platforms/arm/tiva: add lm3s6965-ek board documentation**
Add board documentation for the Stellaris LM3S6965 Evaluation Kit including available configurations (nsh, qemu-flat, qemu-protected, qemu-kostest, qemu-nxflat) and instructions for running and debugging with QEMU. Also add a Supported Boards toctree section to the Tiva platform index to automatically include board documentation.
## Impact
* Is new feature added? Is existing feature changed? NO. Bug fix and documentation addition.
* Impact on user (will user need to adapt to change)? NO.
* Impact on build (will build process change)? NO.
* Impact on hardware (will arch(s) / board(s) / driver(s) change)? YES - lm3s6965-ek board defconfig and linker script updated.
* Impact on documentation (is update required / provided)? YES - board documentation added in this PR.
* Impact on security (any sort of implications)? NO.
* Impact on compatibility (backward/forward/interoperability)? NO.
## Testing
I confirm that changes are verified on local setup and works as intended:
* Build Host(s): Linux, x86_64, GCC
* Target(s): arm, lm3s6965-ek:qemu-protected (QEMU)
Testing logs after change:
```
$ ./tools/configure.sh lm3s6965-ek:qemu-protected
$ make -j$(nproc)
$ qemu-system-arm -M lm3s6965evb -device loader,file=nuttx/nuttx.bin -nographic
NuttShell (NSH) NuttX-12.8.0
nsh>
```
## PR verification Self-Check
* [x] This PR introduces only one functional change.
* [x] I have updated all required description fields above.
* [x] My PR adheres to Contributing [Guidelines](https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md) and [Documentation](https://nuttx.apache.org/docs/latest/contributing/index.html) (git commit title and message, coding standard, etc).
* [ ] My PR is still work in progress (not ready for review).
* [x] My PR is ready for review and can be safely merged into a codebase.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] boards/arm/tiva/lm3s6965-ek: fix qemu-protected and add board documentation [nuttx]
Posted by "raiden00pl (via GitHub)" <gi...@apache.org>.
raiden00pl commented on PR #18586:
URL: https://github.com/apache/nuttx/pull/18586#issuecomment-4137655119
Creating applications with NuttX and AI is the coolest thing I've come across lately. You throw NuttX running on the host into the AI loop, implement all the hardware mocks, add integration tests (for example with NTFC), and you have a powerful setup for autonomously creating things. The next step, a bit more funny and difficult to implement, is adding real hardware into the AI loop.
AI as an auxiliary tool for programmers exists, works quite well and will probably not disappear. Like any disruptive technology (I think we can call it that), it comes with pros and cons and plenty of moralizing on both sides.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] boards/arm/tiva/lm3s6965-ek: fix qemu-protected and add board documentation [nuttx]
Posted by "acassis (via GitHub)" <gi...@apache.org>.
acassis commented on PR #18586:
URL: https://github.com/apache/nuttx/pull/18586#issuecomment-4117929230
> > I think if used with responsibility (and you understand the generated code) of use of AI is ok. In this PR is way used mostly to write Documentation and fix the linker script, and the generated test was tested.
> > The problem is when AI generates Slop and someone that used it has not idea what to generated
>
> For now anyways; we still have not come to a conclusion on NuttX's AI policy, and this should probably be revisited.
True, we need to defined if it is acceptable to receive code generated by AI and if so, what should be accepted and what shouldn't be accepted.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] boards/arm/tiva/lm3s6965-ek: fix qemu-protected and add board documentation [nuttx]
Posted by "linguini1 (via GitHub)" <gi...@apache.org>.
linguini1 commented on PR #18586:
URL: https://github.com/apache/nuttx/pull/18586#issuecomment-4117866895
> I think if used with responsibility (and you understand the generated code) of use of AI is ok. In this PR is way used mostly to write Documentation and fix the linker script, and the generated test was tested.
>
> The problem is when AI generates Slop and someone that used it has not idea what to generated
For now anyways; we still have not come to a conclusion on NuttX's AI policy, and this should probably be revisited.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] boards/arm/tiva/lm3s6965-ek: fix qemu-protected and add board documentation [nuttx]
Posted by "acassis (via GitHub)" <gi...@apache.org>.
acassis commented on PR #18586:
URL: https://github.com/apache/nuttx/pull/18586#issuecomment-4117319019
> > I'm curious whether this was written by AI or by yourself.
>
> I guide AI to write the code. It's time to change how the programmer do the coding everyday.
I think if used with responsibility (and you understand the generated code) of use of AI is ok. In this PR is way used mostly to write Documentation and fix the linker script, and the generated test was tested.
The problem is when AI generates Slop and someone that used it has not idea what to generated
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] boards/arm/tiva/lm3s6965-ek: fix qemu-protected and add board documentation [nuttx]
Posted by "linguini1 (via GitHub)" <gi...@apache.org>.
linguini1 commented on code in PR #18586:
URL: https://github.com/apache/nuttx/pull/18586#discussion_r2981205620
##########
boards/arm/tiva/lm3s6965-ek/scripts/memory.ld:
##########
@@ -34,7 +34,7 @@ MEMORY
/* 64Kb of contiguous SRAM */
- ksram (rwx) : ORIGIN = 0x20000000, LENGTH = 16K
- usram (rwx) : ORIGIN = 0x20004000, LENGTH = 16K
- xsram (rwx) : ORIGIN = 0x20008000, LENGTH = 32K
+ ksram (rwx) : ORIGIN = 0x20000000, LENGTH = 20K
+ usram (rwx) : ORIGIN = 0x20005000, LENGTH = 20K
+ xsram (rwx) : ORIGIN = 0x2000a000, LENGTH = 24K
Review Comment:
Would shrinking xsram break any other configurations?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] boards/arm/tiva/lm3s6965-ek: fix qemu-protected and add board documentation [nuttx]
Posted by "linguini1 (via GitHub)" <gi...@apache.org>.
linguini1 commented on code in PR #18586:
URL: https://github.com/apache/nuttx/pull/18586#discussion_r2981200275
##########
Documentation/platforms/arm/tiva/boards/lm3s6965-ek/index.rst:
##########
@@ -0,0 +1,169 @@
+===========
+lm3s6965-ek
+===========
+
+The `Stellaris LM3S6965 Evaluation Kit
+<https://www.ti.com/tool/EK-LM3S6965>`_ is an ARM Cortex-M3 based
+development board featuring the LM3S6965 microcontroller with an
+integrated 10/100 Ethernet controller. NuttX can run on this board
+both on real hardware and under QEMU emulation
+(``qemu-system-arm -M lm3s6965evb``).
+
+Features of the LM3S6965 Evaluation Kit:
+
+* LM3S6965 microcontroller (ARM Cortex-M3, 50 MHz)
+* 256 KB flash, 64 KB SRAM
+* Integrated 10/100 Ethernet MAC and PHY
+* OLED graphics display (128 x 96 pixel)
+* MicroSD card slot
+* USB interface for debugging and power supply
+* Standard ARM 20-pin JTAG debug connector
+
+Configurations
+==============
+
+Each configuration is maintained in a sub-directory and can be selected
+as follows::
+
+ $ ./tools/configure.sh lm3s6965-ek:<subdir>
+
+Where ``<subdir>`` is one of the following:
+
+discover
+--------
+
+A network discovery configuration::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:discover
+ $ make
Review Comment:
I think you can remove this for all configurations, since you already show how to configure above.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] boards/arm/tiva/lm3s6965-ek: fix qemu-protected and add board documentation [nuttx]
Posted by "linguini1 (via GitHub)" <gi...@apache.org>.
linguini1 commented on PR #18586:
URL: https://github.com/apache/nuttx/pull/18586#issuecomment-4127608362
> The community maintains a robust review mechanism, especially with @linguini1 , @michallenc , and @acassis continuing to review code.
That's very kind of you! And we highly benefit from your reviews (and patches) as well!
> AI poses no threat to the merging workflow or code quality; on the contrary, it will accelerate the development of the community.
I strongly disagree. There has been a large influx of low quality of AI PRs and issues in recent months. I do agree with you that in many of those cases, this is just due to inexperienced developers being able to easily submit code that they haven't verified, or developers not taking their due diligence. I'm not accusing Xiang or this PR of this, nor do I think this applies to all users of AI tools by any means!
> Finally please refrain from questioning the use of AI in any developer's PR (unless the quality of AI-generated content is severely subpar). If a discussion on AI strategy is needed, it should take place in an issue or another dedicated thread, rather than targeting individual developers and contributors.
There was an ongoing discussion on the mailing list about this and I agree that's the best place for this discussion. However, sometimes discussions happen on relevant PRs (for instance, this copilot review feature is quite new and has caused some discussion). I think people should be able to discuss in the relevant locations while we're still learning about this. I also think it's totally fair game to question the use of AI generated content even if the quality doesn't look subpar. AI often hallucinates information in a way that doesn't look immediately obvious. There are also copyright issues and license incompatibility.
> @linguini1 @michallenc @acassis I would even recommend that you try using Claude Code to implement a small feature module as a trial—you’ll be pleasantly surprised by the results it delivers.
No thanks! These LLMs have been trained using content stolen from open source developers, artists, scientists, authors, etc. There are lots of copyright battles going on right now regarding this issue, and LLMs have been shown to be able to directly reproduce copyrighted works with very little prompting. LLMs are also contributing to the spread of misinformation and they are the reason for the rapid increase in spam and fake content everywhere on the internet. They are also actively ruining initiatives run by other open source projects, like bug bounties, and have contributed to skyrocketing hardware prices. I have tried using generative AI and I am incredibly underwhelmed by the results. I study in a lab that explores applications of generative (and non-generative) AI. Not to mention I am actively watching them ruin education for my peers. The effects of LLM usage on productivity are currently still being studied, and the results are not looking positive so far. You may find Anth
ropic's recent paper an interesting read.
I want to stress: if it works for your workflow that's fine, and the community absolutely has to decide it's own policy for it's use (I accept that many people disagree with my stance and I certainly cannot ban AI from use in NuttX). There currently is no NuttX policy and so obviously it's not up to me to ban AI generated content, but I will continue to be skeptical of generative a
AI output due to my own experiences using it, and I absolutely refuse to use it myself, as is my choice.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] boards/arm/tiva/lm3s6965-ek: fix qemu-protected and add board documentation [nuttx]
Posted by "anchao (via GitHub)" <gi...@apache.org>.
anchao commented on PR #18586:
URL: https://github.com/apache/nuttx/pull/18586#issuecomment-4123919083
> > > I think if used with responsibility (and you understand the generated code) of use of AI is ok. In this PR is way used mostly to write Documentation and fix the linker script, and the generated test was tested.
> > > The problem is when AI generates Slop and someone that used it has not idea what to generated
> >
> >
> > For now anyways; we still have not come to a conclusion on NuttX's AI policy, and this should probably be revisited.
>
> True, we need to defined if it is acceptable to receive code generated by AI and if so, what should be accepted and what shouldn't be accepted.
I would like to clarify why I asked whether this PR was implemented via AI or manually.
My concern stemmed from my impression that @xiaoxiang781216 does not typically proactively supplement documentation. It was therefore a pleasant surprise to see the relevant sections added via AI in this commit.
AI is a tool, it depends on how we utilize it, rather than rejecting AI-generated code outright.
The modifications in this PR are minor in nature. Every change was personally reviewed by @xiaoxiang781216 , and I also participated in the review process. The content is entirely correct and unproblematic.
The community maintains a robust review mechanism, especially with @linguini1 , @michallenc , and @acassis continuing to review code. AI poses no threat to the merging workflow or code quality; on the contrary, it will accelerate the development of the community.
If you insist on completely abstaining from AI, then NuttX should not even be hosted on GitHub, considering that the GitHub interface you interact with daily is largely AI-generated.
Finally please refrain from questioning the use of AI in any developer's PR (unless the quality of AI-generated content is severely subpar). If a discussion on AI strategy is needed, it should take place in an issue or another dedicated thread, rather than targeting individual developers and contributors.
@linguini1 @michallenc @acassis I would even recommend that you try using Claude Code to implement a small feature module as a trial—you’ll be pleasantly surprised by the results it delivers.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] boards/arm/tiva/lm3s6965-ek: fix qemu-protected and add board documentation [nuttx]
Posted by "xiaoxiang781216 (via GitHub)" <gi...@apache.org>.
xiaoxiang781216 commented on PR #18586:
URL: https://github.com/apache/nuttx/pull/18586#issuecomment-4116057762
> I'm curious whether this was written by AI or by yourself.
I guide AI to write the code. It's time to change how the programmer do the coding everyday.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] boards/arm/tiva/lm3s6965-ek: fix qemu-protected and add board documentation [nuttx]
Posted by "xiaoxiang781216 (via GitHub)" <gi...@apache.org>.
xiaoxiang781216 closed pull request #18586: boards/arm/tiva/lm3s6965-ek: fix qemu-protected and add board documentation
URL: https://github.com/apache/nuttx/pull/18586
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] boards/arm/tiva/lm3s6965-ek: fix qemu-protected and add board documentation [nuttx]
Posted by "Copilot (via GitHub)" <gi...@apache.org>.
Copilot commented on code in PR #18586:
URL: https://github.com/apache/nuttx/pull/18586#discussion_r2975831218
##########
Documentation/platforms/arm/tiva/boards/lm3s6965-ek/index.rst:
##########
@@ -0,0 +1,153 @@
+===========
+lm3s6965-ek
+===========
+
+The `Stellaris LM3S6965 Evaluation Kit
+<https://www.ti.com/tool/EK-LM3S6965>`_ is an ARM Cortex-M3 based
+development board featuring the LM3S6965 microcontroller with an
+integrated 10/100 Ethernet controller. NuttX can run on this board
+both on real hardware and under QEMU emulation
+(``qemu-system-arm -M lm3s6965evb``).
+
+Features of the LM3S6965 Evaluation Kit:
+
+* LM3S6965 microcontroller (ARM Cortex-M3, 50 MHz)
+* 256 KB flash, 64 KB SRAM
+* Integrated 10/100 Ethernet MAC and PHY
+* OLED graphics display (128 x 96 pixel)
+* MicroSD card slot
+* USB interface for debugging and power supply
+* Standard ARM 20-pin JTAG debug connector
+
+Configurations
+==============
+
+Each configuration is maintained in a sub-directory and can be selected
+as follows::
+
+ $ ./tools/configure.sh lm3s6965-ek:<subdir>
+
+Where ``<subdir>`` is one of the following:
+
+discover
+--------
+
+A network discovery configuration::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:discover
+ $ make
+
+nsh
+---
+
+Configures the NuttShell (NSH) with serial and telnet interfaces::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:nsh
+ $ make
+
+nx
+--
+
+An NX graphics configuration::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:nx
+ $ make
+
+qemu-flat
+---------
+
+A FLAT memory model configuration for running under QEMU::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:qemu-flat
+ $ make
+
+qemu-protected
+--------------
+
+A PROTECTED memory model configuration for running under QEMU::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:qemu-protected
+ $ make
+
+qemu-kostest
+-------------
+
+A PROTECTED memory model configuration with kernel ostest for running
+under QEMU::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:qemu-kostest
+ $ make
+
+qemu-nxflat
+------------
+
+A FLAT memory model configuration with NXFLAT binary support for running
+under QEMU::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:qemu-nxflat
+ $ make
+
+tcpecho
+-------
+
+A TCP echo server configuration::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:tcpecho
+ $ make
+
+Running with QEMU
+=================
+
+FLAT build (qemu-flat)
+----------------------
+
+::
+
+ $ qemu-system-arm -M lm3s6965evb -nographic \
+ -kernel nuttx.bin
+
+PROTECTED build (qemu-protected, qemu-kostest)
+-----------------------------------------------
+
+The PROTECTED build produces separate kernel and user binaries.
+Use ``-device loader`` to load the user binary at its link address::
+
+ $ qemu-system-arm -M lm3s6965evb -nographic \
+ -kernel nuttx.bin \
+ -device loader,file=nuttx_user.bin,addr=0x20000
+
+With networking (qemu-flat, qemu-protected)
+-------------------------------------------
+
+To enable networking with the host, add the ``-netdev`` and ``-nic``
+options::
+
+ $ qemu-system-arm -M lm3s6965evb -nographic \
+ -kernel nuttx.bin \
+ -netdev user,id=user0 \
+ -nic user,id=user0
+
+To exit QEMU, press ``Ctrl-A`` then ``X``.
+
+Debugging with QEMU
+====================
+
+1. To debug the NuttX ELF with symbols, make sure the following change
+ has been applied to defconfig::
+
+ +CONFIG_DEBUG_SYMBOLS=y
+
+2. Run QEMU at shell terminal 1 with GDB server enabled::
+
+ $ qemu-system-arm -M lm3s6965evb -nographic \
+ -kernel nuttx.bin -S -s
+
Review Comment:
Debugging instructions are internally inconsistent for this config: `CONFIG_DEBUG_SYMBOLS=y` is already enabled in the lm3s6965-ek:qemu-protected defconfig, so Step 1 reads like a required change when it isn't. Also, if the intent is to debug a PROTECTED build end-to-end, the QEMU command in Step 2 should mention loading the userspace binary as well (or clarify that this is kernel-only debugging).
```suggestion
1. To debug the NuttX ELF with symbols, ensure that the following
configuration option is enabled in your defconfig (it is already
set in the ``lm3s6965-ek:qemu-protected`` defconfig)::
CONFIG_DEBUG_SYMBOLS=y
2. Run QEMU at shell terminal 1 with GDB server enabled (kernel-only
debugging)::
$ qemu-system-arm -M lm3s6965evb -nographic \
-kernel nuttx.bin -S -s
For a PROTECTED build, to debug end-to-end including the userspace
binary, also add the loader option described above, for example::
$ qemu-system-arm -M lm3s6965evb -nographic \
-kernel nuttx.bin \
-device loader,file=nuttx_user.bin,addr=0x20000 -S -s
```
##########
Documentation/platforms/arm/tiva/boards/lm3s6965-ek/index.rst:
##########
@@ -0,0 +1,153 @@
+===========
+lm3s6965-ek
+===========
+
+The `Stellaris LM3S6965 Evaluation Kit
+<https://www.ti.com/tool/EK-LM3S6965>`_ is an ARM Cortex-M3 based
+development board featuring the LM3S6965 microcontroller with an
+integrated 10/100 Ethernet controller. NuttX can run on this board
+both on real hardware and under QEMU emulation
+(``qemu-system-arm -M lm3s6965evb``).
+
+Features of the LM3S6965 Evaluation Kit:
+
+* LM3S6965 microcontroller (ARM Cortex-M3, 50 MHz)
+* 256 KB flash, 64 KB SRAM
+* Integrated 10/100 Ethernet MAC and PHY
+* OLED graphics display (128 x 96 pixel)
+* MicroSD card slot
+* USB interface for debugging and power supply
+* Standard ARM 20-pin JTAG debug connector
+
+Configurations
+==============
+
+Each configuration is maintained in a sub-directory and can be selected
+as follows::
+
+ $ ./tools/configure.sh lm3s6965-ek:<subdir>
+
+Where ``<subdir>`` is one of the following:
+
+discover
+--------
+
+A network discovery configuration::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:discover
+ $ make
+
+nsh
+---
+
+Configures the NuttShell (NSH) with serial and telnet interfaces::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:nsh
+ $ make
+
+nx
+--
+
+An NX graphics configuration::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:nx
+ $ make
+
+qemu-flat
+---------
+
+A FLAT memory model configuration for running under QEMU::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:qemu-flat
+ $ make
+
+qemu-protected
+--------------
+
+A PROTECTED memory model configuration for running under QEMU::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:qemu-protected
+ $ make
+
+qemu-kostest
+-------------
+
+A PROTECTED memory model configuration with kernel ostest for running
+under QEMU::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:qemu-kostest
+ $ make
+
+qemu-nxflat
+------------
+
+A FLAT memory model configuration with NXFLAT binary support for running
+under QEMU::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:qemu-nxflat
+ $ make
+
+tcpecho
+-------
+
+A TCP echo server configuration::
+
+ $ ./tools/configure.sh -l lm3s6965-ek:tcpecho
+ $ make
+
+Running with QEMU
+=================
+
+FLAT build (qemu-flat)
+----------------------
+
+::
+
+ $ qemu-system-arm -M lm3s6965evb -nographic \
+ -kernel nuttx.bin
+
+PROTECTED build (qemu-protected, qemu-kostest)
+-----------------------------------------------
+
+The PROTECTED build produces separate kernel and user binaries.
+Use ``-device loader`` to load the user binary at its link address::
+
+ $ qemu-system-arm -M lm3s6965evb -nographic \
+ -kernel nuttx.bin \
+ -device loader,file=nuttx_user.bin,addr=0x20000
+
+With networking (qemu-flat, qemu-protected)
+-------------------------------------------
+
+To enable networking with the host, add the ``-netdev`` and ``-nic``
+options::
+
+ $ qemu-system-arm -M lm3s6965evb -nographic \
+ -kernel nuttx.bin \
+ -netdev user,id=user0 \
+ -nic user,id=user0
Review Comment:
The "With networking (qemu-flat, qemu-protected)" example command does not load `nuttx_user.bin`. For PROTECTED builds this will not run user-space, contradicting the section title and the earlier note that protected builds produce separate kernel/user binaries. Update the command (or narrow the heading) so the qemu-protected case includes loading the user binary at the userspace link address.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org