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 CORE DUMP LOOP

    Scheduled Pinned Locked Moved Issues & Bugs
    pytrackcoredumpbootloop
    4 Posts 2 Posters 490 Views 2 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.
    • G Offline
      Glagnar
      last edited by

      I have an empty LoPy ( i.e. no code on it ) and it core dumps when inserted into my PyTrack v1.1. When connected to an old Expansion Board 2.1a it works fine.
      I have tried upgrading and downgrading the PyTrack to versions:
      pytrack_0.0.2.dfu
      pytrack_0.0.3.dfu
      pytrack_0.0.4.dfu
      pytrack_0.0.6.dfu
      pytrack_0.0.7.dfu
      pytrack_0.0.8.dfu
      ...
      none of them help.

      Guru Meditation Error: Core  0 panic'ed (InstrFetchProhibited)
      . Exception was unhandled.
      Register dump:
      PC      : 0x00000000  PS      : 0x00060f30  A0      : 0x80118079  A1      : 0x3ffbd670
      A2      : 0x00000000  A3      : 0x00000037  A4      : 0xffffffa4  A5      : 0x3ffdd38c
      A6      : 0x00000008  A7      : 0x00000000  A8      : 0x80123348  A9      : 0x3ffbd660
      A10     : 0x3ffdd3a8  A11     : 0x00000037  A12     : 0xffffffa4  A13     : 0x3ffbd704
      A14     : 0x7777d9c3  A15     : 0x7777d9c3  SAR     : 0x00000010  EXCCAUSE: 0x00000014
      EXCVADDR: 0x00000000  LBEG    : 0x4009abc5  LEND    : 0x4009abf9  LCOUNT  : 0xffffffff
      Backtrace: 0x00000000:0x3ffbd670 0x40118076:0x3ffbd690 0x40119083:0x3ffbd760 0x4012f611:0x3ffbd780 0x40131173:0x3ffbd7d0
      ================= CORE DUMP START =================
      ZDEAAA4AAABsAQAA
      hNj7P7DV+z982Ps/```
      1 Reply Last reply Reply Quote 0
      • P Offline
        Paul Thornton
        last edited by

        Hey,

        Just to let you know we have seen this. Im currently im the process of tracking down an answer to what might be going on. Ill update this thread as soon as I hear/discover anything.

        G 1 Reply Last reply Reply Quote 0
        • G Offline
          Glagnar @Paul Thornton
          last edited by

          @paul-thornton Thank you, I am very grateful. I have created an RMA as I seem to have narrowed it down to a defective board. My second PyTrack running 0.0.8 of the formware works perfectly.
          I have also ordered 5 new PyTrack boards, so we can continue our development :)

          P 1 Reply Last reply Reply Quote 0
          • P Offline
            Paul Thornton @Glagnar
            last edited by

            @glagnar Hey,

            Pretty sure I just responded to your rma a short while ago you can go ahead and ignore my request to confirm its running the latest firmware in that now I realise its linked to this thread :). Ill update the RMA shortly :)

            Paul

            1 Reply Last reply Reply Quote 0

            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