Source-builder Qemu compiling / customizing

1/06/16/writing-a-custom-device-for-qemu/ So somewhere I need to change the submodule link to a version of qemu that I control. Sorry if this should have been posted to users. Still waiting on the verify email. -- Thanks, Sam Price ___ devel mailing list

[PATCH 1/1] rtems-tools: stty rename / spelling bug.

This patch fixes a spelling/rename mistake in rtems-tools. --- tester/rt/stty.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tester/rt/stty.py b/tester/rt/stty.py index 130318d..fca026a 100644 --- a/tester/rt/stty.py +++ b/tester/rt/stty.py @@ -558,7 +558,7 @@ class

Re: [PATCH 2/5] testsuites/libtests: Remove floats from libdl tests

Nevermind that would be done at the linker and not at compile time. On Mon, Aug 28, 2023 at 11:04 AM Sam Price wrote: > > Just curious instead of doing #ifdef __microblaze__ > could you do > #ifndef __extendsfdf2 > > Or something similar to determine if the floating point

Re: [PATCH 2/5] testsuites/libtests: Remove floats from libdl tests

t; + /* This is just here to link `__extendsfdf2` into the base image. */ > + { > +float f = 0.; > +printf("f: %f\n", f); > + } > +#endif /* __microblaze__ */ > + >te = rtems_tarfs_load("/", (void *)T

device tree loading from uboot.

,force-raw=true \ Does this seem reasonable or is there a way people are testing device tree support in qemu by setting the r5 register on startup? -- Sincerely, Sam Price ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo

[PATCH] int64 operation test.

on microblaze there is an operation that destroys the msr on interrupt task switches. (addi needs switched to addik). I was trying to add a single processor 78 test to detect this, could someone review? *** BEGIN OF TEST SP 78 *** *** TEST VERSION: 6.0.0.227fd7cbb84a286983ec2b4cea3a24b9836692cb

Re: [PATCH] build: Add RTEMS_QUALIFIED

ions of basically the same > code. This will eventually lead to inconsistencies. I understand the > intent may be to have a code base closer to what can be ultimately > qualified, but I see this as problematic from a long-term maintenance > perspective. > > What I see here is that certain APIs are being circumvented presumably > because they are not part of someone's qualified package. As far as I > know, the goal of pre-qual was never to create qualified packages, but > to make it easier for downstream users to make qualified packages of > their choosing. Pushing constraints back into rtems.git because of an > inability to qualify some parts of the code is opposite of the goal. > It is like a somewhat kinder form of stripping down RTEMS to what is > qualified and shipping that, which is what I understood to be the > previous methodology that should be avoided. > > I would also not like to see variations of the same files for > different "profiles" or qualified targets. > > Gedare > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel -- Sincerely, Sam Price ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

linkcmds.yml problems

you, Sam Price ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: linkcmds.yml problems

White wrote: > On Thu, Jul 7, 2022 at 10:31 AM Sam Price wrote: > > Is it possible i have a bad python instance ? > > I was able to reproduce the linker problem using the latest RTEMS upstream > code. > > It looks like it was broken by commit > a0aaa394b68727d20490

Re: Possible tls bug on arm / microblaze

At one point I believe a company tested the sptls tests, unsure if they did this on qemu or hardware. I'll try running those tests on a recent hash, and back when the company ran those tests. Where would the ti->offset member be updated / initialized at? Only the arm, and microblaze bsps have

Possible tls bug on arm / microblaze

-- Thank you, Sam Price ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: Possible tls bug on arm / microblaze

executing thread ID: 0x08a010001 executing thread name: UI1 On Tue, Jul 19, 2022 at 2:25 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 19/07/2022 20:10, Sam Price wrote: > > > > Where would the ti->offset member be updated / initialized at? >

Re: Re: Possible tls bug on arm / microblaze

. On Wed, Aug 24, 2022 at 11:17 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > I am on holidays until 2022-08-28. For RTEMS related topics please contact > Christian Mauderer if it is > urgent. > -- Sincerely, Sam Price ___

Re: docs not building to PDF

* Most of all, I will need to spend significant time to learn PlantUML > and to > > get the result in shape I will certainly need to do some trying and > fumbling > > around. > > Maybe an example would help: > > > https://git.rt

Re: docs not building to PDF

Yes https://github.com/mermaid-js/mermaid-cli There are command line tools so it can be integrated into pipelines. Convert Mermaid mmd Diagram File To SVG mmdc -i input.mmd -o output.svg Create

Re: docs not building to PDF

example

Re: docs not building to PDF

I forgot the loop backs. from close back to open. On Thu, Oct 13, 2022 at 1:12 AM Chris Johns wrote: > On 13/10/2022 4:06 pm, Sam Price wrote: > > example > > > > > h

Re: docs not building to PDF

d a bunch of others. > Then you only need one tool for it. > > Best regards, > > Jan > > > -Original Message- > > From: devel On Behalf Of Chris Johns > > Sent: Thursday, October 13, 2022 6:22 AM > > To: Sam Price > > Cc: Development > >

Binary CPU / Thread information.

, Sam Price ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: Binary CPU / Thread information.

Is there a preferred api style, or just mimic the linux kernel task? https://docs.huihoo.com/doxygen/linux/kernel/3.7/structtask__struct.html FreeRTOS has https://www.freertos.org/a00021.html#xTaskGetTickCount vxworks has a spy interface.

microblaze 2nd timer

follow the patch instructions and submit? -- Sincerely, Sam Price ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Doorstop question

Im starting to use doorstop for my project. I heard that RTEMS uses a customized version of it, and wanted to see what the differences were. I was trying to find it on https://git.rtems.org/ But can't seem to find the customized version. -- Sincerely, Sam Price

Build error microblaze

format -- Sincerely, Sam Price ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Microblaze 2nd timer interrupt

The current microblaze design only has a single timer. I want to use the 2nd timer on the microblaze to run some low level tasks. Wondering if someone could see if i'm on the right track. Regarding the timer from the Xilinx api api """The interrupt service routine reads the timer

Re: Microblaze 2nd timer interrupt

:8:10: fatal error: bsp/timer.h: No such file or directory 8 | #include | ^ Is the correct approach to just put all bsp specific calls in bsp.h? On Sat, Nov 5, 2022 at 10:04 PM Sam Price wrote: > > The current microblaze design only has a single timer. >

rtems gtest

google test repo. -- Thanks, Sam Price ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: Change build specification files from YAML to JSON?

Yaml files can have comments, json files can’t. So you would lose some documentation… -- Sincerely, Sam Price ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH 2/3] bsps/microblaze: Add support for multiple UARTs

_ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel -- Sincerely, Sam Price ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: Static analysis

Thanks Alex, I was able to write a variable analyzer using the compile_database. https://gist.github.com/thesamprice/d4a19102aa4fe11fb96a75df57b9fcfe On Mon, May 15, 2023 at 9:31 PM Sam Price wrote: > > Thanks Alex, > I was able to run cppcheck. > I had to install the newest c

unit test framework

/gtest. The code in rtems didnt seem to use cli / shell support to launch the test suite. -- Sincerely, Sam Price ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

doctest rtems example

/* Tell doctest to not use its own main */ #define DOCTEST_CONFIG_IMPLEMENT /* tell doctest to not use sigint that rtems does not have */ #define DOCTEST_CONFIG_NO_POSIX_SIGNALS #include "doctest.h" /* Setup command line part */ const char rtems_test_name[] = "DOCTEST UNIT TESTS"; static int

Re: Tool versions for RTEMS 6.1 release?

gt; due to a regression in the AArch64 toolchain. The latest release is still > 2.40, so please don't roll that forward until the 2.41 release is out and > is verified to have the fix. > > Kinsey > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel -- Sincerely, Sam Price ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: doctest rtems example

. There is no need to build and link > libraries. > > Chris > > On 16/6/2023 11:07 pm, Sam Price wrote: > > /* Tell doctest to not use its own main */ > > #define DOCTEST_CONFIG_IMPLEMENT > > /* tell doctest to not use sigint that rtems does not have */ > &g

Re: Static analysis

bblock/src/media.c:637:16: note: Uninitialized variables: partitions.begin, partitions.end, partitions.flags .begin = partitions [i].begin, ^ cpukit/libblock/src/bdbuf.c:396:3: warning: Uninitialized variable: q [uninitvar] q->avl.left = q->avl.right = NULL; ^ cpukit/li

Re: Static analysis

ean`, run `bear -- ./waf` to generate compile_commands.json. > Then you should be able to run `cppcheck --project=compile_commands.json`. > > Alex -- Sincerely, Sam Price ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Static analysis

I was trying to run scan-build on a microblaze build. However scan-build wasn't seeing any files get built. I then tried to revert down to the intercept-build command, and it generated an empty compilation database. /usr/share/clang/scan-build-py-10/bin/intercept-build --override-compiler ./waf

Re: [PATCH rtems-source-builder 2/2] devel/qemu-xilinx: Fix build on GCC 13.2.0

___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel -- Sincerely, Sam Price ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH rtems-source-builder 2/2] devel/qemu-xilinx: Fix build on GCC 13.2.0

Moore wrote: > > On Wed, Feb 14, 2024 at 9:14 AM Sam Price wrote: >> >> I was wondering if you had any notes on your process of working with >> qemu in the rtems builder. >> I imagine you have your own xilinx qemu forked to work on, and then >> take the pat

QEMU IRL not modeled

the irl. >From what i can tell https://github.com/Xilinx/qemu/blob/master/target/microblaze/cpu.c#L153 Interrupt registers actually firing. https://github.com/Xilinx/qemu/blob/master/target/microblaze/helper.c#L180 -- Sincerely, Sam Price ___ devel mail