its arguments require the 0x decorator to define hex,
whereas arguments to xtask don't. A little confusing, but
only if you actually ever call create-image -- which nobody
does, to a first order.
The kernel and loader may need to use a different target, particularly
in the case of Precursor where the kernel and loader need an OS of
`none`.
Signed-off-by: Sean Cross <sean@xobs.io>
The problem is the original way of specifying crates for remote
download is the same that Rust uses to specify a version of a crate
(e.g. the @ symbol), and so I could not differentiate between the
two cases.
Switch to using a ^ symbol for remote download crates. Hopefully
that doesn't have conflicts??
this has become necessary because with the inclusion of a version
number in a crate name, rustc always consults the on-line index on
every build (even when it's not necessary), which can double the
build time. Using --offline reduces that thrashing.
this is because we are keeping an older version around
for a legacy ed25519 depedency, so we have to fully
specify which sha2 we want build as our server
A BinaryFile was previously identified only by its path,
thus if a bianry file represented an app rather than a service,
there was no information that could go in the manifest for the gam.
This let's one optionally specify a name for a BinaryFile.
passing this flag causes the loader to print debug output.
This slows down the loading process but gives you some visibility
into what's going on (maybe also an idea for the future to add
VDBG flags for verbosity, they exist in the code but not exposed
as command line options).
This creates:
1) An `xtask' command that allows someone to compile individual apps
without compiling the entire image (note that this is required because
xtask generates files that contain gam context names, and if you just
do a regular `cargo build' building the app will fail)
2) A python file app_server.py that acts as a server to give the
app-loader a list of the apps and actually send it the
3) A basic UX that allows app-loader to set the server, get the list
of apps, and load apps.
Currently, this mostly works, except that there is some random
`ShareViolation' when the app-loader loads the app.
When the user selects App Loader from the app menu, a new menu shows
up that displays the currently loaded apps (in the future this will
contain options to add/remove apps as well). This is a much more sane
approach than whatever I was doing before because it requires minimal
changes to the rest of the source tree (I had to change xtask so that
it would replace -'s with _'s in constant names so that I could name
my app app-loader).
This patch set goes across all the toolchains and brings
in the support for split SVD descriptions of SoCs.
This is helpful for dealing with designs that have multiple
"top" files for the same core IP set. For exmaple, you may have
a SoC that you are developing that targets silicon, but
you have a version that wraps this in additional peripherals
available only in an FPGA emulator that are used for debugging.
In this case, you can have one SVD file be the description of
the SoC itself, and another SVD file describe just the "delta"
introduced by the FPGA wrapper that emulates/controls the SoC.
In order to reduce friction of bringing on new platforms and experimenting
in utralib and svd2utra, xous-core now by default pulls these libraries
from the local repository.
Differences between the local version and the published version for
just these two packages are now downgraded to warnings, instead of
hard errors. This is because a difference does not indicate that
crates.io has had a modification we didn't expect; it simply means
we forgot to publish the package and we should eventually do so
once we have stabilized changes, so that others who rely upon it
can have the updated version.
But, with this patch, at least if we are experimenting with utralib
or svd2utra we don't have to publish a patch to bump revisions on
every major package every single time for a build to succeed.
I think this is an OK trade-off, but happy to roll this decision
back if it affects @eupn / @jeandudey negatively.
The new location makes a lot more *sense* (previously the
cache said 'git' when it was actually crates.io) but
it broke the verifier. This is now fixed.
This change is made with the intention of making the xous-rs crate a bit
more freestanding without depending on the xtask build system.
Signed-off-by: Jean-Pierre De Jesus DIAZ <me@jeandudey.tech>
- make the "base" field no longer public. It is accessible, but only
through an `unsafe` method, because, it is unsafe.
- add accessors to offest/mask fields. Because, it's not at all
unsafe to access these, and it can be useful for bit-ops that are
not part of the generic set of UTRA.
- add Arc to AtomicCSR, and require `std` for AtomicCSR types.
This should not break anything, I checked inside @foundation-devices
keyOS and they don't seem to be using AtomicCSR anywhere.
The Arc makes it a bit safer to clone the AtomicCSR base pointer
and share it between threads, but it will have an impact on performance.
The USB stack (which requires AtomicCSR) was regression testing and the
impact seems minimal.
Recall that the main purpose of AtomicCSR is to provide a CSR accessor
that does not require a mutable reference to the base object. This
can make certain Rust idioms a bit cleaner. We wrap the base accessor
in Arc+Atomic to try and improve the safety of throwing the borrow
checker under the bus, but it's still not perfect because hardware
mutable state can have side-effects within hardware itself that cannot
be modeled or checked by Rust's borrow checker.
Restrict crates.io published set to just APIs, not implementation
files. Nobody is using the implementations anyways -- it was requested
but I've never seen the package pulled except for CI.
in practice this has not been a useful indicator, and we
have stabilized the SVD format so that changes in the code don't
cause the SVD files to go incompatible anymore.
this should make maintenance a bit easier going forward, hopefully.
also merge in cramium support to harmonize the forks for easier
cross-patches in the future.
it works with e.g. shellchat, but not vault.
still scratching my head on what's gone wrong -- it's
crashing in the pre-boot, which means something is not
mapped right for some case that wasn't caught in the
earlier testing.
commit a09100ab4a
Author: bunnie <bunnie@kosagi.com>
Date: Fri Dec 30 15:55:55 2022 +0800
bump lockfile
commit 53172e1471
Author: bunnie <bunnie@kosagi.com>
Date: Fri Dec 30 15:46:40 2022 +0800
bump verification pins
commit 36398810dd
Author: bunnie <bunnie@kosagi.com>
Date: Fri Dec 30 15:24:36 2022 +0800
bump version numbers to absorb new syscalls
commit 062fa6178a
Merge: ac4a854e3bcc955a
Author: bunnie <bunnie@kosagi.com>
Date: Fri Dec 30 15:23:31 2022 +0800
Merge branch 'reply-and-receive-next-syscall' into main
commit ac4a854e49
Merge: d1375343e4c298db
Author: bunnie <bunnie@kosagi.com>
Date: Fri Dec 30 15:22:25 2022 +0800
Merge branch 'main' of github.com:betrusted-io/xous-core into main
commit 3bcc955aba
Author: bunnie <bunnie@kosagi.com>
Date: Fri Dec 30 15:21:43 2022 +0800
add test code that also benchmarks the new routines.
commit e4c298db40
Merge: f71278b4e2bf7109
Author: bunnie <bunnie@kosagi.com>
Date: Fri Dec 30 15:16:13 2022 +0800
Merge pull request #289 from betrusted-io/reply-and-receive-next-syscall
Reply and receive next syscall
commit e2bf710939
Author: Sean Cross <sean@xobs.io>
Date: Thu Dec 29 21:06:51 2022 +0800
services: xous-ticktimer: use reply_and_receive_next()
Convert the ticktimer server to use the new
reply_and_receive_next_legacy() call. This is an example of how to use
this API for future projects.
Signed-off-by: Sean Cross <sean@xobs.io>
commit 0e75b8e479
Author: Sean Cross <sean@xobs.io>
Date: Thu Dec 29 21:05:26 2022 +0800
test-spawn: rename `Message` to `MessageEnvelope`
Signed-off-by: Sean Cross <sean@xobs.io>
commit 3218bde2b4
Author: Sean Cross <sean@xobs.io>
Date: Thu Dec 29 21:04:01 2022 +0800
kernel: implement reply_and_receive_next
Implement `ReplyAndReceiveNext` as a syscall. This will reply to a
message, pull the next message out of the queue, and then re-queue the
server to run. This should make servers much more responsive.
This patch has been tested on both hosted and native modes.
Signed-off-by: Sean Cross <sean@xobs.io>
commit d1375343c1
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 29 23:34:48 2022 +0800
update release notes
commit f71278b422
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 29 22:04:55 2022 +0800
fix issue #109 - refactor key fill/scan to not crash after pruning
After a prune, key fill/scan can crash because there is an assumption
that data is always resident in the cache for a small key.
This code handles the case where the small key data was evicted during
a prune, and reads the data back in just for that key on demand.
Furthermore, during a `sync` call, it will pull in the key data
that corresponds to the page containing just the small key, allowing
that page to be re-composed and replaced in memory. caching is used
on the decryption of the small key page so the expensive bit
of the call should only happen once per small key bank.
tested with pddb-ci and manually in hosted mode.
A portion of code was re-written to make it clear that only the
length of allocated data is copied to/from disk and memory, instead
of the reserved space as the previous code would indicate. The reserved
space is guaranteed to be zero because the RAM-based page for composing
the small key block is zero-ized prior to operations; left comments
reminding me of this in the future so I don't accidentally optimize
something out and cause data leakage between small keys because I'm
allowing the reserved areas to contain stale data.
commit e25da3a720
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 29 22:04:15 2022 +0800
add implemenation of the `prune` debug call
this allows us to trigger the cache prune manually, instead of
in response to memory backpressure only
commit 549e67fead
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 29 22:03:19 2022 +0800
add a `prune` debug call to force a hard-prune of the pddb cache
commit e045574d39
Author: Sean Cross <sean@xobs.io>
Date: Thu Dec 29 21:06:51 2022 +0800
services: xous-ticktimer: use reply_and_receive_next()
Convert the ticktimer server to use the new
reply_and_receive_next_legacy() call. This is an example of how to use
this API for future projects.
Signed-off-by: Sean Cross <sean@xobs.io>
commit 23c17d7632
Author: Sean Cross <sean@xobs.io>
Date: Thu Dec 29 21:05:26 2022 +0800
test-spawn: rename `Message` to `MessageEnvelope`
Signed-off-by: Sean Cross <sean@xobs.io>
commit aae5f3737c
Author: Sean Cross <sean@xobs.io>
Date: Thu Dec 29 21:04:01 2022 +0800
kernel: implement reply_and_receive_next
Implement `ReplyAndReceiveNext` as a syscall. This will reply to a
message, pull the next message out of the queue, and then re-queue the
server to run. This should make servers much more responsive.
This patch has been tested on both hosted and native modes.
Signed-off-by: Sean Cross <sean@xobs.io>
commit ab0c7d3b32
Author: Sean Cross <sean@xobs.io>
Date: Thu Dec 29 21:03:39 2022 +0800
kernel: server: check buf is some when returning mem
Signed-off-by: Sean Cross <sean@xobs.io>
commit 46f340324d
Author: Sean Cross <sean@xobs.io>
Date: Thu Dec 29 21:02:57 2022 +0800
kernel: rename `Message` -> `MessageEnvelope`
This syncs with the latest changes to `xous-rs`.
Signed-off-by: Sean Cross <sean@xobs.io>
commit 911ddb60fc
Author: Sean Cross <sean@xobs.io>
Date: Thu Dec 29 21:01:27 2022 +0800
kernel: debug: fix klog on baremetal
klog() refers to an outdated `.uart` struct, which has since been
renamed to `.serial`.
Signed-off-by: Sean Cross <sean@xobs.io>
commit d88254b1b1
Author: Sean Cross <sean@xobs.io>
Date: Thu Dec 29 21:00:35 2022 +0800
xous: add reply_and_receive_next_legacy call
This call is used to return values while simultaneously listening for
new messages.
The -legacy suffix is used to disambiguate scalar values, so we know
whether to send Scalar1, Scalar2, or Scalar5 messages.
Signed-off-by: Sean Cross <sean@xobs.io>
commit 64c88f9942
Author: Sean Cross <sean@xobs.io>
Date: Thu Dec 29 21:00:05 2022 +0800
xous: add Message type
This type actually contains the message contents, and will be used to
return data to the caller.
Signed-off-by: Sean Cross <sean@xobs.io>
commit d463f9563f
Author: Sean Cross <sean@xobs.io>
Date: Thu Dec 29 20:58:51 2022 +0800
xous: rename Message to MessageEnvelope
This reflects the fact that up until now, the `Message` struct has
merely been the envelope that surrounds the message. It does not contain
any actual Message contents.
Signed-off-by: Sean Cross <sean@xobs.io>
commit 49ce85f9a8
Author: Sean Cross <sean@xobs.io>
Date: Wed Jul 6 15:57:10 2022 +0800
ticktimer-server: prepare for using ReplyAndReceiveNext
Misc cleanup prior to switching which call we use.
Signed-off-by: Sean Cross <sean@xobs.io>
commit be56af6303
Author: Sean Cross <sean@xobs.io>
Date: Wed Jul 6 15:35:22 2022 +0800
xous: add wrapper for reply_and_receive_next
This wrapper enables userspace programs to use the new
ReplyAndReceiveNext syscall easily.
Signed-off-by: Sean Cross <sean@xobs.io>
commit 36e6e6c30b
Author: Sean Cross <sean@xobs.io>
Date: Wed Jul 6 15:18:32 2022 +0800
xous: syscall: add ReplyAndReceiveNext call
Signed-off-by: Sean Cross <sean@xobs.io>
commit 1e56598b10
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 29 00:53:32 2022 +0800
chore: fix some typos
commit 1291b0f00b
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 29 00:38:27 2022 +0800
add issue # to release note
commit 7206f24271
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 29 00:37:47 2022 +0800
update release notes
commit 2f30e1b50a
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 29 00:11:03 2022 +0800
implement #269
commit 5370c333da
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 29 00:10:42 2022 +0800
add callback for monitoring basis lock/unlock events
commit 8d42feb051
Author: bunnie <bunnie@kosagi.com>
Date: Wed Dec 28 19:48:40 2022 +0800
increase heap for mtxcli; add memory usage reporting
commit ac1df054ab
Author: bunnie <bunnie@kosagi.com>
Date: Mon Dec 26 13:52:44 2022 +0800
absorb 22-bit satp fix
commit 89500015a7
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 15 17:52:55 2022 +0800
try to fix regression from #284
still hitting cache coherence edge cases. expanding the flush
set read by one more way.
commit 41ea0a37c5
Merge: e422740db288d93a
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 15 14:36:40 2022 +0800
Merge branch 'main' of github.com:betrusted-io/xous-core into main
commit b288d93abd
Merge: 8e1d0502d4527b82
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 15 14:00:10 2022 +0800
Merge pull request #284 from betrusted-io/use-thin-lto
cargo: use thin-lto
commit d4527b8227
Author: Sean Cross <sean@xobs.io>
Date: Thu Dec 15 12:26:00 2022 +0800
cargo: use thin-lto
Use thin LTO for linking. This shouldn't have too big of an affect on
the resulting binary size, and it fixes the build for 1.66.0:
= note: rust-lld: error: undefined symbol:
core::panicking::panic_str_nounwind::h9b449c0fe03c8dac
>>> referenced by compiler_builtins.22a3dcb1-cgu.13
>>> compiler_builtins-b913bacb8fda1c55.compiler_builtins.22a3dcb1-cgu.13.rcgu.o:(compiler_builtins::math::libm::rem_pio2_large::rem_pio2_large::h3db6431f23a281c1)
in archive root\lib\rustlib\riscv32imac-unknown-xous-elf\lib\libcompiler_builtins-b913bacb8fda1c55.rlib
>>> referenced by compiler_builtins.22a3dcb1-cgu.13
>>> compiler_builtins-b913bacb8fda1c55.compiler_builtins.22a3dcb1-cgu.13.rcgu.o:(compiler_builtins::math::libm::rem_pio2_large::rem_pio2_large::h3db6431f23a281c1)
in archive root\lib\rustlib\riscv32imac-unknown-xous-elf\lib\libcompiler_builtins-b913bacb8fda1c55.rlib
Signed-off-by: Sean Cross <sean@xobs.io>
commit e422740d37
Author: bunnie <bunnie@kosagi.com>
Date: Tue Dec 13 23:03:50 2022 +0800
chore: last one. really.
commit ad79ebf8ba
Author: bunnie <bunnie@kosagi.com>
Date: Tue Dec 13 23:02:09 2022 +0800
chore: more typos. no really, i can stop at any time.
commit b1b6d46d27
Author: bunnie <bunnie@kosagi.com>
Date: Tue Dec 13 22:56:37 2022 +0800
chore: more typos
probably should not have tried to spell check this, now i'm wasting
my time.
commit 283ea1de0d
Author: bunnie <bunnie@kosagi.com>
Date: Tue Dec 13 22:49:25 2022 +0800
chore: fix more typos, add french dictionary to vscode workspace settings
commit 1d94968b2f
Author: bunnie <bunnie@kosagi.com>
Date: Tue Dec 13 22:36:47 2022 +0800
chore: fix typos
commit e930d88563
Author: bunnie <bunnie@kosagi.com>
Date: Tue Dec 13 01:42:00 2022 +0800
placeholder for 0.9.12 release notes
commit 8e1d05020d
Author: bunnie <bunnie@kosagi.com>
Date: Tue Dec 13 00:32:11 2022 +0800
add v0.9.11 to the restore.py URL list
commit bd230f5bb0
Author: bunnie <bunnie@kosagi.com>
Date: Mon Dec 12 16:51:27 2022 +0800
fix text to speech mode preferences setting
never allow the audio system to be turned off for blind people,
and disallow 0-volume setting as well.
commit 38bc254bb9
Author: bunnie <bunnie@kosagi.com>
Date: Mon Dec 12 16:28:33 2022 +0800
fix missing ja/zh translation
commit 60d4482ce2
Author: bunnie <bunnie@kosagi.com>
Date: Mon Dec 12 16:16:04 2022 +0800
bump lockfile
commit 56f0843229
Author: bunnie <bunnie@kosagi.com>
Date: Mon Dec 12 16:08:28 2022 +0800
bump verifier numbers
commit 5370ce396d
Author: bunnie <bunnie@kosagi.com>
Date: Mon Dec 12 16:07:20 2022 +0800
bump all revs due to SoC artifact update
commit cac0e57cda
Author: bunnie <bunnie@kosagi.com>
Date: Mon Dec 12 16:06:31 2022 +0800
change default target
commit 04b441a234
Author: bunnie <bunnie@kosagi.com>
Date: Mon Dec 12 16:06:19 2022 +0800
add 0.9.11 build artifact
commit 08cf863ff5
Author: bunnie <bunnie@kosagi.com>
Date: Mon Dec 12 16:05:15 2022 +0800
update SoC artifacts for 0.9.11 build
commit c32b5d5bac
Author: bunnie <bunnie@kosagi.com>
Date: Mon Dec 12 15:31:15 2022 +0800
bump release notes
commit 80ce119c95
Author: bunnie <bunnie@kosagi.com>
Date: Mon Dec 12 15:31:06 2022 +0800
fix RSSI calculations
commit edf24d9fc2
Author: bunnie <bunnie@kosagi.com>
Date: Mon Dec 12 14:11:19 2022 +0800
clean up on the wifi signal bars
commit eb17edc4ec
Merge: 9a580070435a6ea2
Author: bunnie <bunnie@kosagi.com>
Date: Mon Dec 12 11:47:18 2022 +0800
Merge pull request #283 from gsora/feat/wifi-signal-bars
feat: wifi signal bar
commit 9a580070a3
Author: bunnie <bunnie@kosagi.com>
Date: Sun Dec 11 17:50:51 2022 +0800
revert threaded init question now that deface issue is fixed
commit f9cdf31857
Author: bunnie <bunnie@kosagi.com>
Date: Sun Dec 11 17:07:29 2022 +0800
bump release notes
commit 196ceb0d29
Author: bunnie <bunnie@kosagi.com>
Date: Sun Dec 11 16:42:03 2022 +0800
fix: avoid thrashing when recomputing previously defaced canvases
There was a dubious line that I never felt good about and today
I found out why. By flipping every canvas to drawable before doing
the intersection computation we also throw away the defacement state,
so previously defaced canvases would lose their status bit, causing
thrashing of the canvases anytime there is a re-computation of
the canvas ordering.
This fix caches if a canvas was already defaced, and if it turns out
that an on-screen canvas should not be drawable but was already
defaced, the setting is re-applied, preventing thrashing.
commit dca043d387
Author: bunnie <bunnie@kosagi.com>
Date: Sun Dec 11 16:41:53 2022 +0800
improve context swap debug messages
commit 8d8dd2bd2f
Author: bunnie <bunnie@kosagi.com>
Date: Sun Dec 11 16:41:25 2022 +0800
fix typo in unwrap message
commit f31afa5125
Author: bunnie <bunnie@kosagi.com>
Date: Sun Dec 11 16:41:06 2022 +0800
remove unused opcode in shellchat; improve debug output
commit 6138b65d76
Author: bunnie <bunnie@kosagi.com>
Date: Sat Dec 10 23:44:18 2022 +0800
update comments to reflect changes in CI infra
commit 399124f942
Author: bunnie <bunnie@kosagi.com>
Date: Sat Dec 10 22:05:47 2022 +0800
fix hosted mode
commit 939e13950d
Author: bunnie <bunnie@kosagi.com>
Date: Sat Dec 10 18:59:55 2022 +0800
comment out debug in rootkeys implementation section
commit 2097afc166
Author: bunnie <bunnie@kosagi.com>
Date: Sat Dec 10 18:58:06 2022 +0800
add efuse burning flow to rootkeys
currently only available for builds that have the `efuse` feature
enabled
commit 19e16aea29
Author: bunnie <bunnie@kosagi.com>
Date: Sat Dec 10 18:56:59 2022 +0800
fix jtag fuse burning & add diagnostic messages
- msb/lsb swap on efuse bank fixed
- hazardous-debug feauter gates added
- dry-run for "testing only" added
commit 4ec866e1d7
Author: bunnie <bunnie@kosagi.com>
Date: Sat Dec 10 18:56:12 2022 +0800
add diagnostic seal command
commit f5c687a524
Author: bunnie <bunnie@kosagi.com>
Date: Sat Dec 10 17:45:30 2022 +0800
clarify user prompt
commit 2b4e47384e
Author: bunnie <bunnie@kosagi.com>
Date: Sat Dec 10 17:44:54 2022 +0800
add fused device support and warnings to precursorupdater
commit e42c4c7b33
Author: bunnie <bunnie@kosagi.com>
Date: Sat Dec 10 16:39:14 2022 +0800
add warnings & support for fused devices
burning a generic image to a fused device will surely lead to
a brick, so, try to keep a user from shooting themselves in the foot.
commit c2f7a63f97
Author: bunnie <bunnie@kosagi.com>
Date: Sat Dec 10 16:39:01 2022 +0800
remove some whitespace to allow for easier debugging
commit 1f89843122
Author: bunnie <bunnie@kosagi.com>
Date: Fri Dec 9 12:38:53 2022 +0800
defer init root keys question until status thread starts
also defer the preference thread from loading until after the
PDDB mount thread is started -- doesn't make sense to start it
any earlier than that, since it depends on the PDDB being mounted.
commit 02f9701546
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 8 17:42:12 2022 +0800
make an explicit dvt feature to simplify flags
commit 4dd983bfc4
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 8 17:19:05 2022 +0800
adjust security parameters for dvt build
commit fc08c3e29d
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 8 17:14:47 2022 +0800
add hazardous-debug to modals bip-39
for convenient key printout during debug. flag is normally off.
commit dd82b7f32a
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 8 17:14:21 2022 +0800
add no-codec mode to status
this is for DVT builds where the codec isn't supported, needed
for efuse testing
commit a5d341c7a6
Author: bunnie <bunnie@kosagi.com>
Date: Thu Dec 8 14:09:36 2022 +0800
add a bitstream encryption/recovery tool for fused devices
This is useful for recovering bricked devices where the backup
key is available. This tool can be used to generate an FPGA
image for a device that has been permanently fused to a non-0
backup key.
commit 4f270f54be
Author: bunnie <bunnie@kosagi.com>
Date: Wed Dec 7 22:24:56 2022 +0800
revert debugging on status opcodes
commit 435a6ea2bd
Author: Gianguido Sorà <me@gsora.xyz>
Date: Wed Dec 7 14:28:07 2022 +0100
feat: wifi signal bar
This commit draws a Wi-Fi signal bar with 5 bars (lowest to highest signal), to the right of SSID name.
Signal power is calculated from a lowest of -90dBm to a maximum of -30dBm, by increments of 13dBm.
commit f84a9d10c7
Author: bunnie <bunnie@kosagi.com>
Date: Sun Dec 4 18:13:37 2022 +0800
add placeholder for the efuse flow in the rootkey service
commit 8208a86c08
Author: bunnie <bunnie@kosagi.com>
Date: Sun Dec 4 18:12:30 2022 +0800
add the UX front-end for backup key burning
- instructions for BBRAM flow (refers to wiki)
- consent for efuse flow
- fix a blocking issue on backup prep (minor problem, just gives
users more time to contemplate without a panic)
commit 3838f3bc15
Author: bunnie <bunnie@kosagi.com>
Date: Sun Dec 4 18:12:05 2022 +0800
add a pause for context swaps on menu release
commit 53c9af1033
Author: bunnie <bunnie@kosagi.com>
Date: Fri Dec 2 23:00:38 2022 +0800
bump readme's
We now use build flags to decide which version of utralib to use. This
makes `LAST_CONFIG` obsolete, since the version of utralib is decided
using a hash of build configs and build flags.
Signed-off-by: Sean Cross <sean@xobs.io>
The `args.bin` file served only to be copied to `xous_presign.img`. Skip
this step and directly generate a file called `xous_presign.img`.
Signed-off-by: Sean Cross <sean@xobs.io>
resurrecting some old hardware as an efuse testing target;
new hardware is too precious at the moment given the ridiculous
shortage of FPGAs on the market.
verification is sort of pointless, because:
The Cargo.toml file is parsed and reformatted by the packaging tool to normalize its contents.
Thus, the Cargo.toml file of the downloaded version never matches the Cargo.toml file that's actually used.
Unfortunately, there doesn't seem to be an easy way to check the equivalence of two Cargo.toml files,
except for recursively and deeply parsing through and comparing all the possibile keys and values of
the abstract key/value tree. This is a much bigger project than I'm prepared to figure out today.
As a hack, we compare to the Cargo.toml.orig file. Which is...kind of OK, but really, this opens us
up to attacks where someone just has to replace a version on a package or even just swap out an
entire package for a malicious one by just using package name re-assignment which is a thing that
the format supports. In other words, all this checking is kind of pointless because it's super-easy
to swap out key crates for whole other crates and have it go undetected.
- strip out gdb-stub. Per xobs, the feature never worked, and it
depends upon a branch of a git repo which is not allowed by crates.io
Since the feature hasn't been developed, and crates.io will not
allow even an optional feature that points to a git repo, the feature
was stripped out.
- rename "kernel" to "xous-kernel", so that we can live in a crates.io
package namespace that is specific to Xous.
still have to figure out the riscv package issue.
this is necessary because we need the full SVD path to generate
the whitelist of physical pages that can be addressed. Since the
SVD path is now domiciled in utralib, a file called "SVD_PATH"
is created in the target/ directory which contains the resolved
path to the SVD file given the abstract target/rev feature pair.
this fix makes it so that
1) you always get a correct build when the SVD spec is toggled
2) you don't always rebuild when nothing has changed
(2) is with the caveat that the no-change flag is only clean
after your second build (i.e. your third run will be fast).
I'm not quite sure why but I think it's because the "changes"
to the config file tracker are computed throughout the first
build and the second build still sees that file as recently
changed, so, it'll trigger a rebuild (could also just be
a race condition because the timestamp of the rebuild is
at the same second that the file was regenerated, so conservatively
you'd rebuild the next time).
- default SVD file is specified now as a constant at the top of xtask
- SVD files are now tracked to commit refs in the betrused-soc tree
this is so that we don't have to guess which crate rev corresponds
to which SVD rev -- we specify it explicitly with a feature flag.
also add a routine to manually switch over the UTRA in this case.
for whatever reason, the system is not picking up the change in
the UTRA when specified as an environment variable change --
maybe there is a hard coded link somewhere, but I can't seem
to find it.
since performnace counting is an edge case use mostly by
frankly just me, I'm not going to worry about ergonomics so
much.
turns out, they're pretty useless. I mean, for debugging actual
running code. it tells us basically what we know already which is
99.99% of the time is spent waiting on inter-thread messaging
in hosted mode.
adding a key of "submenu" will automatically create the corresponding
integer argument of submenu contexts for the app.
NB: you should try to only create 1 and re-use it. Menus
are resource hungry, and will rapidly eat through your connection
and thread table.
Had two JSON entries with the same key, which meant you had
a 50/50 chance of a rebuild being triggered depending on which
entry was picked for the build. :-/
The manifest was being processed, but the package list was
going back to the original base set, which would lead to
a confusing situation of apps being listed but the binaries not
being present.
The vault app is the beginning of a multi-purpose authentication vault.
It will feature:
1. FIDO2 authentication
2. TOTP authenticators
3. Password storage to PDDB with auto-typing via keyboard HID
This is the first step on a very very long journey.
Also includes the USB test commands in shellchat.
This is different from the usb-test crate, in that it's fully
integrated into Xous. usb-test is just for quick-testing the USB
driver, in the absence of most of the rest of Xous.
I don't know why it doesn't break under a default config, but if
xous-core is cloned to a directory that doesn't match the repo
name this breaks. This patch tries to fix it for that case.
Now that we have full JSON parsing inside xtask, actually parse the
assets API endpoint to determine the correct URL.
Signed-off-by: Sean Cross <sean@xobs.io>
Add the loader into the main workspace, removing it from its own
sub-workspace. We can do this now that we can specify the linker script
in `build.rs`.
This improves IDE support, and should shrink disk storage requirements.
Signed-off-by: Sean Cross <sean@xobs.io>
The `renode-bypass` flag is used for development in order to speed up
certain features. This creates invalid keys and skips many checks, which
causes problems in the main image.
Remove this flag in order to fix the Renode image.
Signed-off-by: Sean Cross <sean@xobs.io>