Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    PyTrack 2.0 - esp_image: Checksum failed. Calculated 0x36 read 0x16

    Scheduled Pinned Locked Moved Expansion Board
    pytrack2gpyfirmware upgradfirmwareesp32
    1 Posts 1 Posters 27 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R Offline
      Raymond Limpens
      last edited by

      My PyTrack 2.0, in combination with the gpy, is having issues with booting up after I updated the firmware version to version 16 (pytrack2_v16.dfu).
      It keeps throwing the following error that the checksum is failing for the device. Also, I tried to find an older firmware version or perform an update via the PyCom update firmware tool but this tool also keeps failing.

      I tried to do the whole upgrade process on multiple PC's (Linux and Windows), but no success so far.

      configsip: 0, SPIWP:0xee
      clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
      mode:DIO, clock div:1
      load:0x3fff8020,len:8
      load:0x3fff8028,len:2128
      load:0x4009fa00,len:19760
      entry 0x400a05bc
      E (552) esp_image: Checksum failed. Calculated 0x36 read 0x16
      

      Logs of the firmware upgrade progress:

      dfu-util.exe -D pytrack2_v16.dfu
      dfu-util 0.9
      
      Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
      Copyright 2010-2016 Tormod Volden and Stefan Schmidt
      This program is Free Software and has ABSOLUTELY NO WARRANTY
      Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
      
      Match vendor ID from file: 04d8
      Match product ID from file: f014
      Opening DFU capable USB device...
      ID 04d8:f014
      Run-time device DFU version 0100
      Claiming USB DFU Runtime Interface...
      Determining device status: state = dfuIDLE, status = 0
      WARNING: Runtime device already in DFU state ?!?
      Claiming USB DFU Interface...
      Setting Alternate Setting #0 ...
      Determining device status: state = dfuIDLE, status = 0
      dfuIDLE, continuing
      DFU mode device DFU version 0100
      Device returned transfer size 64
      Copying data from PC to DFU device
      Download        [=========================] 100%        16384 bytes
      Download done.
      state(2) = dfuIDLE, status(0) = No error condition is present
      Done!```
      1 Reply Last reply Reply Quote 1

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      • 1 / 1
      • First post
        Last post

      Pycom on Twitter

      Pycom