• 0 Votes
    2 Posts
    808 Views
    J
    @eric24 That is the plan, although it might not come on the first firmware releases. Since LoRa/LoRaWAN (Class A) or Sigfox don't really have a "connection", they just send uplinks or wait to receive for very well determined periods it should certainly be possible to send for example one packet over LoRa and switch to Sigfox for the next one and so on.
  • New firmware release 1.10.2.b1

    Announcements & News firmware
    18
    3 Votes
    18 Posts
    5k Views
    C
    L01 board. Sendn continuously MQTT messages crashing the board 1970:01:01 04:25:31 DEBUG:Conn: SEND <MqttConn object at 3f821f80> value POS 000 001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 032 HEX 001 003 0CD 04B 000 017 000 07F 0AC 0A6 000 000 000 000 000 000 000 000 000 000 000 048 008 08F 042 022 042 038 046 044 045 047 0AE DEC 001 003 205 075 000 023 000 127 172 166 000 000 000 000 000 000 000 000 000 000 000 072 008 143 066 034 066 056 070 068 069 071 174 Guru Meditation Error of type StoreProhibited occurred on core 0. Exception was unhandled. Register dump: PC : 0x400f55e4 PS : 0x00060a30 A0 : 0x800fe1e9 A1 : 0x3ffd6520 A2 : 0xffffffff A3 : 0x3ffd6540 A4 : 0x3f85b4a0 A5 : 0x00000002 A6 : 0x00000000 A7 : 0x00000f12 A8 : 0x00000000 A9 : 0x3ffd6500 A10 : 0x00000000 A11 : 0x00000000 A12 : 0x00000001 A13 : 0x00000001 A14 : 0x00000001 A15 : 0x00000f12 SAR : 0x00000002 EXCCAUSE: 0x0000001d EXCVADDR: 0xffffffff LBEG : 0x40098620 LEND : 0x4009862b LCOUNT : 0x00000000 Backtrace: 0x400f55e4:0x3ffd6520 0x400fe1e6:0x3ffd6540 0x400f35d2:0x3ffd6580 0x400eff91:0x3ffd65b0 0x400fb1e7:0x3ffd65d0 0x400f365c:0x3ffd6670 0x400eff91:0x3ffd6710 0x400efff9:0x3ffd6730 0x400fb27d:0x3ffd6750 0x400f365c:0x3ffd67f0 0x400eff91:0x3ffd6830 0x400efff9:0x3ffd6850 0x400fb27d:0x3ffd6870 0x400f365c:0x3ffd6910 0x400eff91:0x3ffd6990 0x400efff9:0x3ffd69b0 0x400fb27d:0x3ffd69d0 0x400f365c:0x3ffd6a70 0x400eff91:0x3ffd6af0 0x400efff9:0x3ffd6b10 0x400fb27d:0x3ffd6b30 0x400f365c:0x3ffd6bd0 0x400eff91:0x3ffd6c10 0x400efff9:0x3ffd6c30 0x400fb27d:0x3ffd6c50 0x400f365c:0x3ffd6cf0 0x400eff91:0x3ffd6d80 0x400efff9:0x3ffd6da0 0x400fb27d:0x3ffd6dc0 0x400f365c:0x3ffd6e60 0x400eff91:0x3ffd6ef0 0x400efff9:0x3ffd6f10 0x400fb27d:0x3ffd6f30 0x400f365c:0x3ffd6fd0 0x400eff91:0x3ffd7050 0x400efff9:0x3ffd7070 0x400fb27d:0x3ffd7090 0x400f365c:0x3ffd7130 0x400eff91:0x3ffd7170 0x400fb1e7:0x3ffd7190 0x400f365c:0x3ffd7230 0x400eff91:0x3ffd72b0 0x400effbe:0x3ffd72d0 0x400dd887:0x3ffd72f0 0x400dd9dc:0x3ffd7390 0x400dcb98:0x3ffd73c0 ================= CORE DUMP START ================= tDEAAAsAAABsAQAA nEX8P2Bk/T9odf0/ oGH9PwB1/T/JMPMAiEL8P4hC/D+cRfw/gEL8PxQAAACQ2v0/kNr9P5xF/D8AAAAA BQAAAGxV/T9NaWNyb1B5AAAAAAAAAAAAAAAAAGh1/T8AAAAAIAwGAAUAAAABAAAA 8GD7P2hO/D9cNA1AAAAAAIAAAADcSf0/REr9P6xK/T8AAAAAAAAAAAEAAAAAAAAA
  • New firmware release 1.10.1.b1

    Announcements & News firmware
    41
    2 Votes
    41 Posts
    14k Views
    robert-hhR
    @devinv What is happening?
  • 0 Votes
    8 Posts
    2k Views
    sebS
    @danielm said in No more LoRa packet reception after updating firmware: https://github.com/pycom/pycom-micropython-sigfox/issues/102 Daniel is currently out on a business trip so is quite busy. I will remind him about this issue.
  • Flash Wipy with own build

    Discussion wipy 2 flash wipy firmware build
    13
    1
    0 Votes
    13 Posts
    3k Views
    robert-hhR
    @charly86 For OTA you just need appimg.bin, if the other two files are already loaded. The esptool.py command line for that would look like: esptool.py --chip esp32 --port /dev/ttyUSB0 --baud 460800 write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x10000 appimg.bin
  • 0 Votes
    47 Posts
    20k Views
    K
    @seb Thanks, I found them and was able to start playing with the new calls.
  • 0 Votes
    4 Posts
    1k Views
    C
    Every update seems to be different. This time, the PyTrack was detected as a COM device. With the same number as before :). But I was not able to connect. To fix it, I had to select show unconnected devices in the device manager, browsed for the usk driver and deleted the unknown and unconnected device.
  • 3 Votes
    9 Posts
    3k Views
    catalinC
    @jcaron Hi, just released new firmware for Pytrack and Pysense v0.0.8, where both your requests were implemented: https://forum.pycom.io/topic/2286/new-firmware-release-for-pytrack-and-pysense-version-0-0-8
  • Silly Firmware Mistak - SiPy thinks it's a LoPy

    Pinned SiPy firmware sipy wrong lopy
    6
    0 Votes
    6 Posts
    3k Views
    X
    For anyone who is reading this... while the method described by @robert-hh works to load the SiPy firmware into the board, it does not perform Sigfox activation which is necessary to connect to the Sigfox network. If you have this issue, please do the following: Note the MAC address of your board: import machine,binascii binascii.hexlify(machine.unique_id()) Email support@pycom.io and include the output of the above commands. We will respond to your request within 24h on weekdays (often much sooner especially if you write to us during CET working hours).
  • New firmware release version v1.9.2.b2

    Announcements & News firmware
    4
    0 Votes
    4 Posts
    3k Views
    L
    @daniel I have upgraded device (WIPY2.0) from 1.7.2.b1 to 1.9.2.b2 and have problems: ntp_sync most of the time not wrok (hang and never ending) i use for it old method def getNTPTime(host = "pool.ntp.org"): port = 123 buf = 1024 address = socket.getaddrinfo(host, port)[0][-1] msg = '\x1b' + 47 * '\0' msg = msg.encode() TIME1970 = 2208988800 # 1970-01-01 00:00:00 # connect to server client = socket.socket(AF_INET, SOCK_DGRAM) client.setblocking(15) client.sendto(msg, address) msg, address = client.recvfrom(buf) t = struct.unpack("!12I", msg)[10] t -= TIME1970 tuple_time = time.localtime(t) rtc.init((tuple_time)) client.close() but also tested if rtc.ntp_sync could help but same result :( i2c not work - i2c buss error i init it with id=0 (i do not remember if in 1.7.2 it was hardware or software based) bus=I2C(0, I2C.MASTER, baudrate=100000, pins=("P19", "P20")) to test it what is going on i have updated board 3 times (all times sucessfully) but with the same result i have downgraded firmware back to 1.7.2.b1 all work without any problems - any hint?
  • New firmware release version v1.9.1.b1

    Announcements & News firmware
    7
    0 Votes
    7 Posts
    2k Views
    D
    @redimo it's fixed already ;-)
  • 1 Votes
    5 Posts
    2k Views
    R
    @daniel Thanks for the hint and the file downloaded fine when I used Google Chrome. I had previously tried Internet Explorer and MS Edge, with similar results. Perhaps it was caused by a Norton add-in ??? @crumble Thanks for your hint as well.
  • 0 Votes
    5 Posts
    1k Views
    Jurassic PorkJ
    hello, @robin said in Using a DHT11 with a LoPy works with old firmware version but not new firmware?: JurassicPork's library did not work for me. What code ? I have two branches in my library : master with the old method to collect the data . and pulses_get using the new function pulses_get Be careful in this branch the constructor has changed (see new examples) Friendly, J.P
  • How I built a custom firmware for frozen bytecode

    Guides frozen firmware
    4
    0 Votes
    4 Posts
    2k Views
    robert-hhR
    @betterauto I found this redirection of USB to a VM often flaky. VMware works better than Virtualbox.
  • Unable to Program SiPy

    SiPy repl sipy firmware serial pymakr
    7
    0 Votes
    7 Posts
    2k Views
    C
    @jcaron It worked! My bad. Didn't even think about that. I erased flash memory and uploaded most recent firmware. Thank you @robert-hh as well. For the future, are there any best practices for connecting/disconnecting, from both a hardware and software standpoint. e.g. my boot.py file: import os from machine import UART uart = UART(0, 115200) os.dupterm(uart) Should I include anything else?
  • New firmware release version v1.9.0.b1

    Announcements & News firmware
    6
    3 Votes
    6 Posts
    2k Views
    affoltepA
    @daniel Right! - thx a lot ;)
  • New firmware release version v1.8.0.b1

    Announcements & News firmware
    10
    3 Votes
    10 Posts
    4k Views
    R
    @rdixey When placing the jumper for the update I was disconnecting the USB but forgetting to disconnect the battery. Sometimes I do silly things :-). But after I realized this I have updated both of my LoPy's.
  • Macos Sierra: Pycom firmware update crashes.

    Issues & Bugs firmware tool crash
    1
    0 Votes
    1 Posts
    868 Views
    No one has replied
  • [SOLVED] Can't update the firmware

    SiPy sipy firmware sipy firmware
    7
    0 Votes
    7 Posts
    2k Views
    O
    It works ! Thank you !