bunnie
659796916a
chore: cleanup typos in docs, comments
2024-01-15 02:16:43 +08:00
bunnie
3deccfad2f
update local SoC binary to track release
2023-08-08 14:31:27 +08:00
bunnie
f10c6b341c
commit the latest SoC version with D$-vm fix
2023-07-29 20:49:33 +08:00
bunnie
a4cdcd7fe6
absorb v0.9.13 soc artifact
2023-05-07 15:06:55 +08:00
bunnie
911da2b92a
sync to latest release candidate
2023-04-16 02:25:15 +08:00
bunnie
904b66a6e9
absorb ebreak fix for CPU
2023-04-12 13:14:24 +08:00
bunnie
024d95e75b
sync up the precursor with what's on the releases train
2023-04-09 17:11:46 +08:00
bunnie
8357ab31a5
bump all pins because utralib got updated
2023-04-09 00:48:35 +08:00
bunnie
cb5bd20739
match latest soc_csr candidate
2023-03-23 21:23:05 +08:00
bunnie
0c752edba4
update SoC to latest candidate
2023-03-19 00:58:41 +08:00
bunnie
8aa538008d
track the latest CI candidate
2023-03-10 20:25:57 +08:00
bunnie
9dc30377ad
bump to the current CI candidate for the SoC image
2023-03-10 00:04:03 +08:00
bunnie
91d0376234
add a helper script to pull the SoC from CI
...
previously we were copying from locally built images. But,
because of the variance in route quality, it would be good
to harmonize the SoC images between the CI train and the
local Xous train.
2023-03-10 00:03:20 +08:00
bunnie
5415fb1967
these were supposed to be renamed, not deleted
2023-03-08 03:47:36 +08:00
bunnie
0dd74fe7b3
remove gitrev from precursor soc type
...
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.
2023-03-08 03:46:03 +08:00
bunnie
26ea2ee5e4
bump the precursor to latest gw build
2023-03-08 03:01:47 +08:00
bunnie
47b5b88438
bump the soc_csr to match release train
2023-02-28 03:55:34 +08:00
bunnie
8690d955d0
add a regenerated SoC
...
no major changes on the SoC; however, some unused blocks
were trimmed, and the timing has been tightened up.
2023-02-27 01:31:27 +08:00
bunnie
64d5644ecf
absorb potential MMU D$ fix from vex dev branch
2023-02-24 18:06:00 +08:00
bunnie
454f41c3b2
update perf image soc to latest rev
2023-01-03 23:25:58 +08:00
bunnie
ac1df054ab
absorb 22-bit satp fix
2022-12-26 13:52:44 +08:00
bunnie
04b441a234
add 0.9.11 build artifact
2022-12-12 16:06:19 +08:00
bunnie
360b0cbd81
commit a fixed soc image at 2022.08
2022-11-18 19:18:54 +08:00
bunnie
156e60d1dd
fix regressions from litex 2022.08
2022-11-17 22:12:32 +08:00
bunnie
3272a87545
add a trial version of the latest SOC
2022-11-17 19:38:01 +08:00
bunnie
a1ebf76e3e
update SoC to latest version for performance profiling
...
the git release number on this is a lie. But, it also doesn't
matter since it's a test build. I just didn't want to bump the
whole OS package dependencies because I'm tweaking a non-deployed
configuration.
2022-10-23 23:16:00 +08:00
bunnie
eb7796b275
move the precursor binary artifacts out of the package
...
there is a limit on the size of a package that can be sent up
to crates.io and this doesn't scale
2022-10-20 17:07:53 +08:00
bunnie
d048372d46
absorb v0.9.10 soc artifacts
2022-10-09 17:53:12 +08:00
bunnie
19c90c1cc7
move precursors to the utralib
...
this will allow us to package up utralib for generation of soc
dependencies
2022-09-26 16:49:49 +08:00
bunnie
6537661aa5
add performance monitoring variants of the SoC
2022-09-16 01:37:29 +08:00
bunnie
c77b5fd8f1
add performance counter versions of the SoC
2022-09-11 07:44:59 +08:00
bunnie
e15969050c
bump precursors to latest tag
2022-07-19 17:40:50 +08:00
bunnie
41936a1a21
update SoC to support forced reset
...
this is to try and fix a problem we're seeing on Linux with the
USB stack eventually shutting down the port as we switch
device configurations too often.
2022-06-11 18:25:22 +08:00
bunnie
7e07c69b71
fix reset timing on USB PHY
2022-05-30 17:39:24 +08:00
bunnie
45c4d6320c
bug fixes for SpinalHDL core (EP0 setups now go to the correct location)
2022-05-16 00:34:42 +08:00
bunnie
d7ad8d6356
this device image is responding to USB setup packets, at least.
2022-05-10 13:24:27 +08:00
bunnie
e3cd5de0ea
this version of precursors actually seems to be doing something usb-like
2022-05-06 13:39:39 +08:00
bunnie
1c21482796
move USB signals into the usbdev block (out of GPIO)
2022-05-03 10:47:40 +08:00
bunnie
b5bbdd87dc
absorb missing commit info
2022-05-03 01:51:23 +08:00
bunnie
2c2e15ac67
hopefully this time i got all the CSRs compiled in for the USB device
2022-05-03 00:11:16 +08:00
bunnie
66892e15d2
upgrade the netlist to include the interrupt line
2022-04-28 22:43:16 +08:00
bunnie
750de11674
add a SoC version that includes a strawman USB device block
...
this block needs to be first activated by flipping a mux,
and then drivers need to be written. wooo...drivers...
2022-04-22 02:56:33 +08:00
bunnie
aa6bf1230a
absorb v0.9.8 tagged SoC
2022-04-20 16:11:30 +08:00
bunnie
5c40908244
absorb SoC fix to reduce boot.bin size with latest rustc
...
just a shift in the optimizer settings.
2022-04-18 16:22:30 +08:00
bunnie
4192c2105f
pull in 0.9.7 soc precursors
2022-02-28 14:18:04 +08:00
bunnie
b012cfa2fc
update SoC precursors to latest Litex
...
prep for future activities e.g. vexriscv perf optimization and
Luna USB integrations
2022-02-25 02:45:36 +08:00
bunnie
862f3a804e
pull in the version string from the gateware for the bootloader
2022-02-04 04:03:52 +08:00
bunnie
3a1fd2e7d0
commit a 0.9.6 tagged prebuilt gateware image
2022-02-04 01:51:50 +08:00
bunnie
11c88b170e
implement a basis for anti-rollback upgrades
...
the actual transition to a new version isn't here. But,
at the very least, the root keys are now derived by hashing
them MAX_ROLLBACK_LIMIT times, which allows us to create a
key chain based on a global version number that can be incremented
while allowing derviation of older keys without compromising newer
keys.
2022-02-04 01:33:04 +08:00
bunnie
9cfffb18e9
some minor fixes to the console debug system to make it more consistent
...
there is still some mysterious problem involving a race condition
of the raw hardware console UART Rx path deciding it doesn't want
to report new characters anymore to the interrupt handler that
is triggered when multi-byte sequences are shoved down the
pipe. So long as you're typing simple commands it's fine, but
escape sequences tend to lock things up. I don't think there's
enough ROI to continue investigating this facility.
2022-01-28 03:36:14 +08:00