-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update submodules and modernize platforms/target files #348
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you merge this with #311 ?
8e3b6ec
to
3675714
Compare
c2d154f
to
8e9db79
Compare
0b923aa in LiteX changes the way vendor tools are located and removes toolchain_path argument
Now that the target Makefile is included *before* the IMAGE_FILE is redefined, if FIRMWARE has been changed we will be using an old version of IMAGE_FILE from the environment, and thus were inadvertently generating two rules to build the "none" firmware bundle if FIRMWARE=none.
(Instead of relying on third_party/ports/fupy having a cached copy of the "hw" includes, which could get out of date; and was out of date after updating litex; modern litex has a different set of CSR routines.)
47b85f5
to
012c5f7
Compare
The new fork containt a commit removing an outdated `hw` directory generated by LiteX.
012c5f7
to
421a402
Compare
@ewenmcneill - I cherry-picked more commits from you branch. Will you have some spare time to test the current version of this branch on the HW? I'm currently testing it on Arty - I do that by simply running:
|
@mateusz-holenko Yes, I have a TinyFPGA BX among other devices. I was testing with TinyFPGA BX mostly because it was convenient and tiny to use for "laptop" development :-) Seems to me like it's working. With the steps below to build PR #348, I get basically the same results as I was getting with my changes (compare, eg, with #277 (comment)).
gives me a working litex BIOS, with 10kB of RAM, and a working MicroPython. I notice that you're temporarily pinned to my MicroPython WIP change. Possibly we should merge that into the FuPy MicroPython if we're agreed that's the direction we want to go? Then you could change the pin back to the FuPy one. Ewen
|
@ewenmcneill - Any idea if the ROM is coming from SPI flash? (I guess we should also put the ROM source in the BIOS output?) |
@mithro I can't see how the TinyFPGA litex-buildenv/targets/tinyfpga_bx/base.py Lines 36 to 39 in 421a402
litex-buildenv/targets/tinyfpga_bx/base.py Lines 68 to 73 in 421a402
It was definitely coming from the SPI Flash in the version I was working on, because I looked at the linker maps. Ewen ETA 2020-04-06 now that I've grabbed the laptop I built on, this is the TinyFPGA BX linker map:
Note how the Also FWIW, MicroPython boots just as slowly as it did before, ie, consistent with slow SPI single speed no cache :-) |
@ewenmcneill - Great! Just wanted to check. @mateusz-holenko Is this ready to merge now then? |
@mithro I tested it on Arty and both the default HDMI2USB and Micropython boot fine. Otherwise I believe it's ready to be merged. |
@ewenmcneill That was exactly my idea. Could you create a PR to FuPy MicroPython? Once it's merged I will point back to the original repository. |
@mithro Travis is red, but it's caused by some network problems when downloading conda packages:
It happens a lot lately :( All other tests passed. |
Tested on The only problem was that for Targets tested on HW:
|
Great! Let's merge for now and continue with more pull requests. |
fupy/micropython#58, which I've just merged since I have commit rights on that repo, and since we all seem in agreement with the approach. We'll want to revert 421a402 (which changes it to use my fork/branch) fairly soon. @mateusz-holenko Do you want do do that revert? Or should I create a revert commit/PR? (The two are currently the same, other than the merge commit in the FuPy MicroPython version.) Ewen |
@mithro Great! @ewenmcneill I created a PR: #385 |
This updates submodules, including LiteX, to the newer versions and fixes compatibility problems.
EDIT: This also includes rebased (and a bit reworked) changes from #311.