Commit graph

10340 commits

Author SHA1 Message Date
Sean Cross
b4d6884cc4 kernel: use addr_of!() and addr_of_mut!()
DUe to https://github.com/rust-lang/rust/issues/114447 direct access to
static mut variables causes a warning which will be turned into an
error in the 2024 edition.

The workaround is to use `addr_of!()` and `addr_of_mut!()` macros and
then dereference that.

Signed-off-by: Sean Cross <sean@xobs.io>
2024-03-22 15:53:11 +08:00
bunnie
62b2567ade add comprehensive host fifo test 2024-03-20 13:41:40 +08:00
bunnie
5911808611
Merge pull request #509 from betrusted-io/bio
WIP: BIO driver
2024-03-12 18:24:38 +08:00
bunnie
133bb2b74f fix a few minor details missing in the tests
also update docs and completion tracker
2024-03-12 13:54:07 +08:00
bunnie
4fa3dd3b59 add spi unit test 2024-03-12 04:53:37 +08:00
bunnie
c121da07ac cargo.toml points to local repo. should fix this before merge! 2024-03-11 19:12:50 +08:00
bunnie
bc8eb46833 commit lock file 2024-03-11 19:12:43 +08:00
bunnie
cb4e5be5ae bring back the low level tests; remove dependency on engine-25519 2024-03-11 18:43:50 +08:00
bunnie
f5fdcf7d5b lock rootkeys into a particular version of the dalek crates + cooperative release of hw accelerator
the cooperative release is THE problem that we need to discuss.
2024-03-11 18:18:37 +08:00
bunnie
3bcc0dcd88 split low-level engine verification routines into a feature flag
to use these, one must include engine-25519 and also not use
the curve25519-dalek native primitives.

Probably what we *should* do is create some backend calls that allow
us to queue up local jobs only for this sort of testing.
2024-03-11 18:17:42 +08:00
bunnie
04abd3f331 remove engine25519 from list of crates to be built 2024-03-11 18:17:07 +08:00
bunnie
bfc7e7acbc point dalek backend 2024-03-11 18:16:51 +08:00
bunnie
cc02f3ab4f
Merge pull request #513 from betrusted-io/renode-gdbserver-3456
emulation: expose gdb serial to port 3456
2024-03-11 14:10:41 +08:00
Sean Cross
24fc352517 emulation: expose gdb serial to port 3456
Signed-off-by: Sean Cross <sean@xobs.io>
2024-03-11 14:01:37 +08:00
bunnie
f389b41ccf
Merge pull request #511 from betrusted-io/cramium
add quantum timer feature to cramium target
2024-03-07 01:35:44 +08:00
bunnie
c3e0bee9dc use PIO as the system timer
other timers might work, but this is the one we can simulate
and pre-flight and know it will work.
2024-03-07 01:32:26 +08:00
bunnie
a96abc669f add interrupt clear call 2024-03-07 01:32:15 +08:00
bunnie
5a1f5e0bd9 update derived artifacts to reflect register fixes 2024-03-04 04:09:11 +08:00
bunnie
2f5a717e65 add unit test for inter-core events and fifo events
synthetic test that exercises multiple cores triggering each
other, waiting on each other to complete tasks, and waiting on
the host to meet conditions such as fifo fullness levels before
running.

this proves out the basic concept of inter-core eventing.
2024-03-04 04:08:01 +08:00
bunnie
0844cfbc52 more unit tests
fifo input/output from host with back-pressure works
gpio loopback input testing works

framework for automated assertion testing is in place;
all tests from this point forward will endeavor to include
some asserts that will cause the test to fail, so we don't require
manual inspection to check test results.
2024-03-03 18:33:30 +08:00
bunnie
ca3a3bba19 absorb extra fields for controlling quantum snapping of gpios 2024-03-03 18:33:12 +08:00
bunnie
8a7b5e5627 add the FIFO basic unit test + todo list of tests 2024-03-03 02:39:12 +08:00
bunnie
0a31875a19 add snap to quantum and extclock select to BIO 2024-03-03 02:38:55 +08:00
bunnie
d80f2824f6 Merge branch 'bio' of github.com:betrusted-io/xous-core into bio 2024-03-02 02:02:27 +08:00
bunnie
e1b0d83cbd add test plan 2024-03-02 02:02:02 +08:00
bunnie
e3cdb4a35d unit test for "hello multiverse"
four cores started all at once, each responsible for updating
a byte of the GPIO range, in unison.
2024-03-02 02:02:02 +08:00
bunnie
6c6634540c skip address tag embedded within the loadable program 2024-03-02 02:02:02 +08:00
bunnie
eff977d439 add quantum snap registers 2024-03-02 02:02:02 +08:00
bunnie
260ec0b39b wrap assembly code generator in a macro
This macro takes as arguments the name of the function
you want to use to retrieve the assembly code, and two labels,
one for the start and one for the end of the assembly code,
and the assembly code itself.

The labels for the start/end of assembly code are identifiers
and because of Rust's rules macros can't create identifiers out
of thin air (I wish instead of saying "partially hygienic", they
just said, "you can't create identifiers that don't exist". Yes,
I'm sure "partially hygienic" has some other meaning to computer
science people but to me it's just pretentious bullshit that
forces me to read through four blog posts and three issues to
come to the practical conclusion I really wanted to know; I
think maybe they wanted to refer to it as hygiene because the
limitation is super frustrating and hygiene sounds like a positive
way to spin something that is annoying. Sure. It's fine. You
didn't want to allow macros to make identifiers because it can lead
to surprising behavior and name space conflicts. That's your choice
as a language designer, just say it.).

Anyways. as usual, rust macro took way too long to write.
2024-03-02 02:02:02 +08:00
bunnie
f24746b88a start on a simple "multi-core" test 2024-03-02 02:02:02 +08:00
bunnie
633b76eb5d flesh out common useful routines for bio access 2024-03-02 02:02:02 +08:00
bunnie
e9e373ac0f initial register mods for BIO to Daric target 2024-03-02 02:02:02 +08:00
bunnie
e297c02cf3 add crate for BIO - better I/O - driver 2024-03-02 02:02:02 +08:00
bunnie
8622fbdf7a
Merge pull request #508 from betrusted-io/ring-0.17
WIP: Ring 0.17
2024-03-02 01:36:08 +08:00
bunnie
b6e5e7f2c2 apply formatting patch
@nworbnhoj, i saw you had explicitly done a formatting pass.
However, I think maybe the +nightly flag was missing, it looks
like the formatting ignored our custom rule set, which requires
nightly?
2024-03-02 01:26:51 +08:00
bunnie
a3b869ef0f reflect ring patch change in lockfile 2024-03-02 01:22:18 +08:00
bunnie
cfafa7f609 Update Cargo.toml to point to the git-based version of ring
this will allow the gh actions check to succeed, hopefully?
2024-03-02 01:21:56 +08:00
bunnie
9a43db9654 remove ring-test command that was not ported to 0.17
we'll port it forward if we end up needing to get that deep
into the crate.
2024-03-02 01:21:25 +08:00
bunnie
91e0661e9d add test plan 2024-03-02 01:08:59 +08:00
bunnie
153db680f2 unit test for "hello multiverse"
four cores started all at once, each responsible for updating
a byte of the GPIO range, in unison.
2024-03-01 23:31:42 +08:00
bunnie
0045e32508 skip address tag embedded within the loadable program 2024-03-01 23:31:18 +08:00
bunnie
241cfd6cca add quantum snap registers 2024-03-01 23:30:52 +08:00
bunnie
7af01fc5e9 wrap assembly code generator in a macro
This macro takes as arguments the name of the function
you want to use to retrieve the assembly code, and two labels,
one for the start and one for the end of the assembly code,
and the assembly code itself.

The labels for the start/end of assembly code are identifiers
and because of Rust's rules macros can't create identifiers out
of thin air (I wish instead of saying "partially hygienic", they
just said, "you can't create identifiers that don't exist". Yes,
I'm sure "partially hygienic" has some other meaning to computer
science people but to me it's just pretentious bullshit that
forces me to read through four blog posts and three issues to
come to the practical conclusion I really wanted to know; I
think maybe they wanted to refer to it as hygiene because the
limitation is super frustrating and hygiene sounds like a positive
way to spin something that is annoying. Sure. It's fine. You
didn't want to allow macros to make identifiers because it can lead
to surprising behavior and name space conflicts. That's your choice
as a language designer, just say it.).

Anyways. as usual, rust macro took way too long to write.
2024-03-01 16:39:30 +08:00
nworbnhoj
ffac721c6b rustfmt
deliberate check of automated rustfmt_check.yaml

confirmed - system works
2024-03-01 09:19:15 +10:00
nworbnhoj
01b13e0e32 replace vendored-in rustls::crypto:💍:SUPPORTED_SIG_ALGS with public access 2024-03-01 06:50:04 +10:00
bunnie
27760d5477 start on a simple "multi-core" test 2024-03-01 03:38:48 +08:00
bunnie
7c30a6960c flesh out common useful routines for bio access 2024-03-01 03:38:22 +08:00
bunnie
dbfaa60429 initial register mods for BIO to Daric target 2024-03-01 00:40:35 +08:00
bunnie
347930d287 add crate for BIO - better I/O - driver 2024-03-01 00:39:54 +08:00
nworbnhoj
7f19e660d9 add link to rustls issue
https://github.com/rustls/rustls/issues/1819
2024-02-29 09:53:02 +10:00