TEST: Enable ulab and attempt to catch app/filesystem overlap #926
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Try to enable ulab for additional builds.
TODO: Most of the required tooling changes to know if ulab builds will work or not have been moved to #927 which needs merged and this PR rebased.
Generally it seems additional ulab builds are... unlikely... but we can always monkey with the filesystem size for people who really want to make that tradeoff.
pimoroni-pico
build in this PR/branch which adjusts the memory split from 640k/1408k to 1024k/1024k. This makes room for ulab and perhaps other things, but since the filesystem has moved, it is not compatible with our Pico or the stock Pico build. ✨ Back up your files! ✨