Thanks for the reply.
I agree the pip solution isn't the worst thing ever.
I will be trying out a bare metal build on the cm3+ and post an update on how it worked out.
Search found 12 matches
- Thu Apr 16, 2020 11:14 am
- Forum: General Discussion and Questions
- Topic: MicroPython vs Ubuntu Core
- Replies: 2
- Views: 1479
- Wed Apr 15, 2020 4:06 pm
- Forum: General Discussion and Questions
- Topic: MicroPython vs Ubuntu Core
- Replies: 2
- Views: 1479
MicroPython vs Ubuntu Core
I have a Raspberry Pi CM3+. I will be running considering my OS options. I could flash MicroPython and run the required MicroPython modules. Or, I could run Ubuntu Core and run a python application. Some observations so far: 1. The MicroPython flash would come with packages for the GPIO, UART etc. b...
- Wed Mar 25, 2020 12:19 pm
- Forum: Programs, Libraries and Tools
- Topic: Large flash size on STM32 port for PyBoard 1.1
- Replies: 9
- Views: 4244
Re: Large flash size on STM32 port for PyBoard 1.1
I understand better what you mean by the minimal libraries used for stm32. And yes, there is a lot of duplication that I do not need. I suppose, I could add the additional functionality manually to the upy source code. Would that be a good idea ? If so, where could I potentially find the source code...
- Wed Mar 25, 2020 10:31 am
- Forum: Programs, Libraries and Tools
- Topic: Large flash size on STM32 port for PyBoard 1.1
- Replies: 9
- Views: 4244
Re: Large flash size on STM32 port for PyBoard 1.1
Previously, I had reallocated more space for flash from the file system as you mentioned but now the size is just too big. Possibly due to the duplication.
- Wed Mar 25, 2020 10:29 am
- Forum: Programs, Libraries and Tools
- Topic: Large flash size on STM32 port for PyBoard 1.1
- Replies: 9
- Views: 4244
Re: Large flash size on STM32 port for PyBoard 1.1
I understand. Basically, I've only added the libraries that helped me remove linker errors when I compiled the user module into the firmware. I'd have to investigate more thoroughly to determine what would've been duplicated. About the flash, I interpreted it as flexible and since I am flashing to a...
- Wed Mar 25, 2020 7:12 am
- Forum: Programs, Libraries and Tools
- Topic: Large flash size on STM32 port for PyBoard 1.1
- Replies: 9
- Views: 4244
Re: Large flash size on STM32 port for PyBoard 1.1
I have a C++ user module that uses a libstdc++, libm etc. and when I add the module, the entire flash just becomes super large.
I'll double check if I'm doing anything off, just in case
I'll double check if I'm doing anything off, just in case
- Tue Mar 24, 2020 10:42 pm
- Forum: Programs, Libraries and Tools
- Topic: Large flash size on STM32 port for PyBoard 1.1
- Replies: 9
- Views: 4244
Large flash size on STM32 port for PyBoard 1.1
I added a bunch of user modules and ended up with a large build package. Resulted in the following error: arm-none-eabi-ld: region `FLASH_TEXT' overflowed by 523020 bytes Fix: by allocating more space for FLASH_TEXT in the linker script for STM32F405 (<>/micropython/ports/stm32/boards/stm32f405.ld) ...
- Tue Mar 24, 2020 10:20 pm
- Forum: Programs, Libraries and Tools
- Topic: Error trying to build a C++ module that uses the standard c++ library
- Replies: 4
- Views: 2326
Re: Error trying to build a C++ module that uses the standard c++ library
Building everything with -mfloat-abi=softfp seems to have worked
- Sat Mar 21, 2020 10:12 pm
- Forum: Programs, Libraries and Tools
- Topic: Error trying to build a C++ module that uses the standard c++ library
- Replies: 4
- Views: 2326
Re: Error trying to build a C++ module that uses the standard c++ library
What I understand is that there is no way I can use it ?
- Fri Mar 20, 2020 2:12 pm
- Forum: Programs, Libraries and Tools
- Topic: Error trying to build a C++ module that uses the standard c++ library
- Replies: 4
- Views: 2326
Error trying to build a C++ module that uses the standard c++ library
Hello, I am trying to add a user module written in C++ on the stm32 port. I have compiled the shared library with appropriate flags and written part of my python wrapper. The module micropython.mk looks like this: EXAMPLE_MOD_DIR := $(USERMOD_DIR) SRC_USERMOD += $(EXAMPLE_MOD_DIR)/test.c LDFLAGS_USE...