MicroPython Forum (Archive)

Thats very strange, I added an update before @jimmo posted but it does not seem to be updated ! anyway, the problem is caused by having a custom manifest file, and there are some files in the modules folder that are needed: So this needs to be added to your custom frozen manifest file: freeze('$(POR...

OK, this is somehow related to the new method for defining overrides (viewtopic.php?f=2&t=7433) as when I re-build the f2ecfe8 file using the new method overrides, it has the problem, but when I flash using the old file built in November the problem is not there.

I think this is the key:
I have just reverted back to November build f2ecfe8 and the problem does not exist.

I have added MICROPY_VFS_FAT=1 to my make command.

I've not used the ESP32 for several months and just built 1.12 for it and flashed it. But it appears that there's no file system: REPL MPY: soft reboot could not find module '_boot.py' MicroPython v1.12-5-g42e45bd69 on 2019-12-24; ESP32 module with ESP32 Type "help()" for more information. >>> help(...

@jimmo - Great, this is working, so now my custom.mk file replaces a symbolic-linked GNUmakefile and my modified mpcconfigport.mk file without having to modify any source files and means that I can remove some bash scripts that copied and linked files before building. nice :D custom.mk ## LWIP NETWO...

Sadly it does not work for me: custom.mk MICROPY_PY_LWIP ?= 1 # wiznet5k module for ethernet support; valid values are: # 0 : no Wiznet support # 5200 : support for W5200 module # 5500 : support for W5500 module MICROPY_PY_WIZNET5K ?= 5500 # cc3k module for wifi support MICROPY_PY_CC3K ?= 0 Results ...

Maybe I'm misunderstanding what you're trying to do. I guess you don't really have a custom board so much as a custom build configuration for an existing board? Yes, sorry that's exactly what I am looking to do, I did not make that very clear. Let me test out what you have proposed, so it does not ...

Jimmo - Thanks, but that's not the behaviour I was hoping for ;) What would be really useful, is if you don't need to source the original files at all and instead, if a file exists in the custom folder, then the build process will first read the original git source file, and then override that file ...

Starting this thread to share information about build procedures, overrides, trick & hints & tips. Apparently, you can override port/board configurations by creating a folder and including the path in the make command: make BOARD=myboard BOARD_DIR=~/src/projects/myboard I just tested this, I have 2 ...

Here's my clone and update scripts, can someone confirm that I am not missing any GIT steps ?? $ARG would be either "clean" or "commit", and $OPT used with commit would be the commit hash. BASHDIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )" UPYDIR="$BASHDIR/../build/micropython" BUILDDIR="$B...