element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
MaaXBoard Hardware Design MaaXBoard-RT: "Wire ACK fault in DAP access"
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 4 replies
  • Subscribers 322 subscribers
  • Views 1774 views
  • Users 0 members are here
  • recover
  • MaaXBoard-RT
  • debugger
  • "ACK fault"
Related

MaaXBoard-RT: "Wire ACK fault in DAP access"

tjaekel
tjaekel over 2 years ago

I tried flash another "import SDK project" for MaaXBoard-RT (related to input GPIO interrupt).
It has bricked the board.

What happened?

When I tried to flash the FW for this new project - it has complained with errors on accessing board, to flash etc.
I got "Wire ACK fault in DAP access" during flashing for debug.

And: Now all my other projects cannot be flashed anymore. All projects show the same error and I cannot flash board anymore (with any project, which were working before).

I assume:
Something is wrong with this project, e.g. the Flash scripts, memory regions... (even I have used the same patches needed for MaaxBoard-RT board).
The old, recently flashed and running project, is ripped out, nothing done anymore by the board. Debugger access is broken.
Also the "GUI Flash" tool does not work (e.g. erase entire flash).

I can imagine:
The Flash was erased (all with 0xFFFF now), but not written with new FW code image.
If SP is set to 0xFFFFFFFF or ResetHandler vector entry is 0xFFFFFFFF - and the MCU released from reset (or after a power cycle) runs "crazy".
It seems to get into a lockup state, executing wrong code which seems to disable also the debugger.
(I found: when SP is set as 0xFFFFFFFF - MCU is locked up, also PC for ResetHandler as 0xFFFFFFFF cannot be right, even it is thumb code, but outside available memory)

How to fix?

Luckily I found a way to fix and to recover.
The MaaXBoard-RT has a jumper for "Internal Boot" vs. "Serial Download" (default).

This was working for me. - Have an *.AXF or *.BIN file ready from a working project:

  • unplug the board
  • set the jumper to "Internal Boot" (the other option)
  • plugin again
  • use the "GUI Flash" tool
  • select to flash the FW for a working project (therefore have one "golden FW" ready)
    BTW: even erasing entire flash works - but it does not help
  • it should flash w/o error (but it does not reboot to it automatically)
  • unplug board
  • change jumper back to "Serial Download" (the default option)
  • plugin again: now your "golden FW" should be running (e.g. see the debug terminal)

Now I could also flash again other projects, the debugger was working again.

Conclusion:

It can happen (for a still unknown reason) that a project taken from SDK, clean on compile, but "bricks" the board.

Have a "golden FW BIN" file ready to recover.

Use the jumper to recover and use the "GUI Flash" tool (to flash a working FW again).

Erasing entire flash with "GUI Flash" tool does not fix, just a working FW flashed seems to recover.

  • Sign in to reply
  • Cancel

Top Replies

  • TheSanjanaSuresh
    TheSanjanaSuresh 5 months ago +1
    I'm also facing the same problem, but I haven't been able to fix it :(. can any one help me
Parents
  • msaka
    msaka over 1 year ago

    Hello,

    Please refer to the Section "6.6.4 HyperFlash Programming using NXP MCUBootUtility Application" of the MaaXBoard RT Hardware User Guide.

    This section describes how to program the Hyperflash via the USB-C interface or a UART interface, using “Serial Download” boot mode which is useful for recovering from a corruption causing the "Wire ACK fault in DAP access".

    Best regards.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • msaka
    msaka over 1 year ago

    Hello,

    Please refer to the Section "6.6.4 HyperFlash Programming using NXP MCUBootUtility Application" of the MaaXBoard RT Hardware User Guide.

    This section describes how to program the Hyperflash via the USB-C interface or a UART interface, using “Serial Download” boot mode which is useful for recovering from a corruption causing the "Wire ACK fault in DAP access".

    Best regards.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube