Building my own firmware?

[misterlisty]

I'm ready to start building my own firmware, here are my questions?

Where is the firmware URL for pycom devices?

Is there a different firmware for each device type ie Lopy, Sigfox?

What IDE should i use for this?

Is their any guide on how i setup my environment for this?

Sorry for all the questions?

[jmarcelino]

@misterlisty

You don't need any IDE. Just setup your compiler and pycom-esp-idf first using the instructions provided in its README: https://github.com/pycom/pycom-esp-idf

Once that's done clone the main repository: https://github.com/pycom/pycom-micropython-sigfox

and follow build the instructions from esp32/README.md there

[misterlisty]

@jmarcelino thank you, and i assume when you make chnages to the firmware i just need to merge your changes into my version?

[jmarcelino]

@misterlisty
Yes, that’s right

[misterlisty]

Looking at the readme for the code...what do i use to build firmware for the fopy? Its just mentions wipy,lopy,sipy

[robert-hh]

@misterlisty The procedure is the same for all boards. In the make command, you mention

make BOARD=xxxx .....

with xxx being WIPY, LOPY, GPY, SIPY, LOPY4 or FIPY or whatever the next board is being called. For the OEM modules, use the name of the matching development board.

For the Lora frequency, tell either:

LORA_BAND=USE_BAND_868
or
LORA_BAND=USE_BAND_915

[misterlisty]

When i try

$ cd esp32
$ make clean
$ make TARGET=boot
$ make TARGET=app
$ make flash

i get bash: python: commandnot found ...any idea..running on windows

[seb]

You will need to install python from: https://www.python.org/

[misterlisty]

@seb Already have python, do i have to do something with the path?

[livius]

@misterlisty
edit msys2_shell.cmd
and uncomment line (remove rem)

rem set MSYS2_PATH_TYPE=inherit

[misterlisty]

@livius still no luck..what should the path be anyway? When installing python should the path have been addded?

[robert-hh]

@misterlisty In windows you have to add the path to python to the PATH environment variable, which is normally done by the installation process. So if you open a cmd window and type the command "python"(enter), python should start. If not, PATH is not set. You can do that in System Control->system>enhanced setting>environment variables.
I'm guessing the names because I have no english system here.

[livius]

@misterlisty
what if you right click and "Run as administrator"?

[robert-hh]

@misterlisty Besides everything else, the best method of creating your own firmware on a windows machine is to install Linux in a virtual machine and do it there. Then the only problem left is getting the compiled firmware onto your board, because the USB support of virtual machines is poor. That can be done with ftp too.
If you have an older computer at hand, install linux there. Unless it's older than 10 years, it should still be fast enough for the task.

[misterlisty]

@robert-hh Just curios, why is running this on linux advantageous?

[robert-hh]

@misterlisty because it matches the development environment for both micropython and esp-idf. All teh toosl used are generic Linux/Unix tools.

[gnm]

Hi guys.
I am trying to build the firmware for mi FIPY but I am having trouble when executing
make BOARD=FIPY TARGET=app

I have followed the steps indicated in this thread, more precisely:

@jmarcelino said in Building my own firmware?:

@misterlisty

You don't need any IDE. Just setup your compiler and pycom-esp-idf first using the instructions provided in its README: https://github.com/pycom/pycom-esp-idf

Once that's done clone the main repository: https://github.com/pycom/pycom-micropython-sigfox

and follow build the instructions from esp32/README.md there

However the compilation throws the following error (for brevity, I show only the first part when the error messages begin):

For the compilation of mpy-cross and for TARGET=boot I have no problem. I have the problem with TARGET=app.

I am using the Toolchain from: https://dl.espressif.com/dl/xtensa-esp32-elf-linux64-1.22.0-80-g6c4433a-5.2.0.tar.gz

I have also tryed with the toolchain sugested here by @jmarcelino 9 months ago, which is https://dl.espressif.com/dl/xtensa-esp32-elf-linux64-1.22.0-61-gab8375a-5.2.0.tar.gz, but in that case the compilation fails even for TARGET=boot with the following error (I obtain the same error with TARGET=app):

Can you please help me to build and flash my own firmware? I need to then make some changes/corrections to the official firmware...but I can't even build the official one in https://github.com/pycom/pycom-micropython-sigfox

[Xykon]

@gnm I suggest you check out this page as well: https://esp-idf.readthedocs.io/en/latest/get-started/linux-setup.html

[jcaron]

@gnm Have you correctly updated the ESP-IDF as well, and cleaned previous output?

[gnm]

Yes @jcaron , I cleaned up everything and made the process all over again a couple of times. Same result every time.
I haven't checked out the suggestion of @Xykon yet.
For the moment I have given up with pycom (my final objective is to implement a nanogateway able to operate with downlink messages), and I am using a multitech gateway and microchip nodes for my project because I need to move on, and the process with pycom as gateway is way too complicated and time consuming. However, I will return to this subject as soon as possible.