New firmware release v1.14.0.b1 (Dual core support and CAN bus)


  • administrators

    Hello,

    We have just released firmware v1.14.0.b1. These are the release notes:

    Cheers,
    Daniel



  • @robert-hh
    Yes, i have seen it before. Great work :)
    But it require to store somewhere font in particular size.
    This is simple alternative.



  • @livius That's nice. You may however also have a look at the work of Peter https://github.com/peterhinch/micropython-font-to-py
    It deals a lot with fonts, and it is well suited to large & nice fonts and use it with the framebuffer module.



  • if someone is interested i have added simple font size scaling to framebuf
    https://github.com/pycom/pycom-micropython-sigfox/pull/131
    result on small oled
    0_1517064426190_9eb71170-2584-40c9-b6ee-87a069a3d75b-image.png



  • When framebuf will be updated to support all formats?
    now it cover MVLSB, RGB565, GS4_HMSB
    but official micropython cover MVLSB, RGB565, GS2_HMSB, GS4_HMSB, GS8, MHLSB, MHMSB


  • administrators

    @brotherdust said in New firmware release v1.14.0.b1 (Dual core support and CAN bus):

    Any plans to update documentation on using the CLI version of the updater tool?

    I will provide documentation for the CLI tool with the next release as I'm currently re-designing the command line parameters.

    If you want to flash your board after building it from source please use make flash instead.



  • release v1.14.0.b1 is crashing during boot process on one of my LoPy4 (no software loaded). At least two other LoPy4 are working with new release v1.14.0.b2.
    With v1.9.2.b2 (original hardware on delivery) the failed LoPy4 is working.


  • administrators

    @colateral said in New firmware release v1.14.0.b1 (Dual core support and CAN bus):

    self.serial = serial.Serial(port, baudrate=115200, bytesize=serial.FIVEBITS, timeout=0.25)

    Can you please try to replace above line in tools/pypic.py with:

    self.serial = serial.Serial(port, baudrate=115200, bytesize=serial.FIVEBITS, timeout=0.25 exclusive=True)

    P.S. I made a small edit after I posted this originally.



  • Still persists the pic build issue

                    LINK build/LOPY_868/release/application.elf
                       text    data     bss     dec     hex filename
                    1050027  289840   54912 1394779  15485b build/LOPY_868/release/application.elf
                    IMAGE build/LOPY_868/release/lopy_868.bin
                    esptool.py v2.1
                    Signing OTA image
                    Entering flash mode
                    Traceback (most recent call last):
                      File "tools/pypic.py", line 187, in <module>
                        sys.exit(main(sys.argv[1:]))
                      File "tools/pypic.py", line 175, in main
                        pic = Pypic(args.port)
                      File "tools/pypic.py", line 77, in __init__
                        self.serial = serial.Serial(port, baudrate=115200, bytesize=serial.FIVEBITS, timeout=0.25)
                      File "D:/ProgramFiles/msys32/mingw32/lib/python2.7/site-packages/serial/serialwin32.py", line 31, in __init__
                        super(Serial, self).__init__(*args, **kwargs)
                      File "D:/ProgramFiles/msys32/mingw32/lib/python2.7/site-packages/serial/serialutil.py", line 240, in __init__
                        self.open()
                      File "D:/ProgramFiles/msys32/mingw32/lib/python2.7/site-packages/serial/serialwin32.py", line 78, in open
                        self._reconfigure_port()
                      File "D:/ProgramFiles/msys32/mingw32/lib/python2.7/site-packages/serial/serialwin32.py", line 222, in _reconfigure_port
                        'Original message: {!r}'.format(ctypes.WinError()))
                    serial.serialutil.SerialException: Cannot configure port, something went wrong. Original message: WindowsError(87, 'The parameter is incorrect.')
                    make: *** [application.mk:458: flash] Error 1


  • For lopower consideration, to run only on one core, what we have to configure in the build ?



  • Any plans to update documentation on using the CLI version of the updater tool? Maybe I'm just using it wrong:

    .\pycom-fwtool-cli.exe -f "C:\Users\xxxx\Code\Pycom\pycom-microp
    ython-sigfox\esp32\build\LOPY_915\release\appimg.bin" -p COM3 --pypic flash
    Connecting.....
    Uploading stub...
    Running stub...
    Stub running...
    Changing baud rate to 115200
    Changed.
    Exception: Timed out waiting for packet content, on line 204
    

    Thanks!



  • Updated a LoPy (1.0) that was running a simple rainbow animation of a set of 8 WS2812b neopixels. On previous versions, the animation tended to be choppy at times. After upgrading to v1.14.0.b1 with dual processor support, the animation is SMOOTH! Nice!



  • @jmarcelino said in New firmware release v1.14.0.b1 (Dual core support and CAN bus):

    @rskoniec
    We sent customised APN LTE firmware to partners (inc Hologram) but testing didn't went as well as we hoped, we're working on it

    Thank you.



  • @daniel does this mean, that we cannot use multi core from user level or do we only have to wait until it is documented?



  • @robert-hh
    Yes, this is really awaited improvement.
    If i look ok into sources it is pinned to 1



  • @daniel said in New firmware release v1.14.0.b1 (Dual core support and CAN bus):

    esp32: Enable dual core support. WiFi, BLE and TCP/IP run on core 0. MicroPython, LoRa and Sigfox run on core 1.

    Hi Daniel, this is a great improvement. Is the LTE support running on Core 0 as well?



  • @rskoniec
    We sent customised APN LTE firmware to partners (inc Hologram) but testing didn't went as well as we hoped, we're working on it


  • administrators

    Just a few notes in case you missed the previous release...

    We recently released a new firmware update tool 1.1.6.b0. With this version the installer for Windows and MacOS will consist of only two executables, one which provides the GUI version called pycom-fwtool and another CLI version called pycom-fwtool-cli which replaces the functionality of the previous bin/updater.py file

    It is highly recommended that MacOS users remove the old application completely before installing this new version (or re-installing it if you have it already installed it). This will make sure all the old frameworks are removed which should save a considerable amount of disk space.

    During internal testing I discovered a bug where, when you try to update/register more than one Sigfox device for the first time using the restart button, the download seems to take forever when updating the second device. I will upload a bugfix for this as soon as possible.

    A bugfix for this is now available as a beta release for MacOS, Windows and Linux. I will upload this new version as a general release later today.




Log in to reply
 

Pycom on Twitter

Looks like your connection to Pycom Forum was lost, please wait while we try to reconnect.