<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Help needed to recover a qn9080-dk in Wireless MCU</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/Help-needed-to-recover-a-qn9080-dk/m-p/771216#M4723</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&amp;nbsp;Anders Tietze,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe the chip memory was left in a locked state and the CMSIS Debug adapter can't perform a mass erase to&amp;nbsp;unlock the memory. Please try debugging with the JLink debugging interface. A similar window as below should appear if the memory is locked. Press Yes to perform a mass erase.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/31810iD01D05FBFDE51A33/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note:&lt;/P&gt;&lt;P&gt;To update the debugging interface, please follow the instructions from the &lt;STRONG&gt;7 Appendix B - Updating Debugger firmware&lt;/STRONG&gt; in the "&lt;EM&gt;C:\NXP\SDK_2.2_QN908xCDK_Beta\docs\&lt;STRONG&gt;Getting Started with MCUXpresso SDK for QN908x.pdf&lt;/STRONG&gt;&lt;/EM&gt;" document.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Gerardo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 29 Jan 2018 22:17:30 GMT</pubDate>
    <dc:creator>gerardo_rodriguez</dc:creator>
    <dc:date>2018-01-29T22:17:30Z</dc:date>
    <item>
      <title>Help needed to recover a qn9080-dk</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Help-needed-to-recover-a-qn9080-dk/m-p/771215#M4722</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have been trying to program the flash from the USB mass storage interface in ISP mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have used the following method from Linux:&lt;/P&gt;&lt;P&gt;dd bs=1024 conv=nocreat,notrunc if=ble_power_profiling.bin of=”/media/CRP DISABLD/firmware.bin”&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After that the Bluetooth chip won't boot, and when I am using MCUXpresso IDE to download code, it fails with "Flash driver failed to initialize". The Bluetooth chip is able to enter ISP mode(Mass storage device is present), but I'm not able to flash the device using the JTAG on the DK-board.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need help to recover from this error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Anders Tietze&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ns: MCUXpresso RedlinkMulti Driver v10.0 (Jun 22 2017 23:34:07 - crt_emu_cm_redlink build 272)&lt;BR /&gt;Pc: ( 0) Reading remote configuration&lt;BR /&gt;Wc(03). No cache support.&lt;BR /&gt;Pc: ( 5) Remote configuration complete&lt;BR /&gt;Nc: Reconnected to existing redlink server (PID 4294967295)&lt;BR /&gt;Nc: Connecting to probe 1 core 0 (server PID unknown) gave 'OK'&lt;BR /&gt;Wc: ============= SCRIPT: RunBootRomConnect.scp =============&lt;BR /&gt;Wc: DpID = 2BA01477&lt;BR /&gt;Wc: APID = 0x24770011&lt;BR /&gt;Wc: Halt on reset vector catch&lt;BR /&gt;Wc: Halt on watchpoint read of vector table&lt;BR /&gt;Wc: ============= END SCRIPT ================================&lt;BR /&gt;Xe:&lt;BR /&gt;Nc: Probe Firmware: LPC-LINK2 CMSIS-DAP V5.173 (NXP Semiconductors)&lt;BR /&gt;Nc: Serial Number: LSAVAQDQ&lt;BR /&gt;Nc: VID:PID: 1FC9:0090&lt;BR /&gt;Nc: USB Path: /dev/hidraw4&lt;BR /&gt;Pc: ( 30) Emulator Connected&lt;BR /&gt;Xc:&lt;BR /&gt;Pc: ( 40) No Halt&lt;BR /&gt;Pc: ( 50) CPU ID&lt;BR /&gt;Nc: number of h/w breakpoints = 6&lt;BR /&gt;Nc: number of flash patches = 2&lt;BR /&gt;Nc: number of h/w watchpoints = 4&lt;BR /&gt;Nc: Probe(0): Connected&amp;amp;Reset. DpID: 2BA01477. CpuID: 410FC240. Info: &amp;lt;None&amp;gt;&lt;BR /&gt;Nc: Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.&lt;BR /&gt;Nc: Inspected v.2 On-chip Flash Memory QN908XC_512K.cfx&lt;BR /&gt;Nc: Image 'QN908XC_512KB Apr 20 2017 16:27:16'&lt;BR /&gt;Nc: NXP: QN908XC&lt;BR /&gt;Pc: ( 65) Chip Setup Complete&lt;BR /&gt;Nt: Connected: was_reset=true. was_stopped=false&lt;BR /&gt;Cr:v MCUXpresso Free License - Downloads unlimited&lt;BR /&gt;Pc: ( 70) License Check Complete&lt;BR /&gt;Nt: Loading 'qn908xcdk_wireless_examples_bluetooth_power_profiling_freertos.axf' ELF 0x00000000 len 0x114&lt;BR /&gt;Nc: Opening flash driver QN908XC_512K.cfx&lt;BR /&gt;Nc: Sending VECTRESET to run flash driver&lt;BR /&gt;Ec:&lt;BR /&gt;Nc: Driver from AXF file:&lt;BR /&gt;Nc: 04000000: 23010020 54000045 00001032 04000000 ..#E..T2.............&lt;/P&gt;&lt;P&gt;-------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Pb: (100) Writing Flash ended with an error.&lt;BR /&gt;Ed:05: File 'qn908xcdk_wireless_examples_bluetooth_power_profiling_freertos.axf' load failure: Ef(50): Flash driver failed to initialize&lt;BR /&gt;Pc: (100) Target Connection Failed&lt;BR /&gt;Nc: error closing down debug session - Nn(05). Wire ACK Fault in DAP access&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Dec 2017 09:57:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Help-needed-to-recover-a-qn9080-dk/m-p/771215#M4722</guid>
      <dc:creator>anderstietze</dc:creator>
      <dc:date>2017-12-07T09:57:22Z</dc:date>
    </item>
    <item>
      <title>Re: Help needed to recover a qn9080-dk</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Help-needed-to-recover-a-qn9080-dk/m-p/771216#M4723</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&amp;nbsp;Anders Tietze,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe the chip memory was left in a locked state and the CMSIS Debug adapter can't perform a mass erase to&amp;nbsp;unlock the memory. Please try debugging with the JLink debugging interface. A similar window as below should appear if the memory is locked. Press Yes to perform a mass erase.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/31810iD01D05FBFDE51A33/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note:&lt;/P&gt;&lt;P&gt;To update the debugging interface, please follow the instructions from the &lt;STRONG&gt;7 Appendix B - Updating Debugger firmware&lt;/STRONG&gt; in the "&lt;EM&gt;C:\NXP\SDK_2.2_QN908xCDK_Beta\docs\&lt;STRONG&gt;Getting Started with MCUXpresso SDK for QN908x.pdf&lt;/STRONG&gt;&lt;/EM&gt;" document.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Gerardo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Jan 2018 22:17:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Help-needed-to-recover-a-qn9080-dk/m-p/771216#M4723</guid>
      <dc:creator>gerardo_rodriguez</dc:creator>
      <dc:date>2018-01-29T22:17:30Z</dc:date>
    </item>
    <item>
      <title>Re: Help needed to recover a qn9080-dk</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Help-needed-to-recover-a-qn9080-dk/m-p/771217#M4724</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&amp;nbsp;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/gerardorodriguezespinoza"&gt;gerardorodriguezespinoza&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;I'm having the same issue when trying to debug the power profile example on the QN9080 Development Board. What can I do to recover the chip if I don't have a JLink debugging interface?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Khanh Huynh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Aug 2018 13:22:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Help-needed-to-recover-a-qn9080-dk/m-p/771217#M4724</guid>
      <dc:creator>khanh_huynh</dc:creator>
      <dc:date>2018-08-31T13:22:18Z</dc:date>
    </item>
    <item>
      <title>Re: Help needed to recover a qn9080-dk</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Help-needed-to-recover-a-qn9080-dk/m-p/771218#M4725</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&amp;nbsp;Khanh Huynh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The on-board debugging circuit (LPC-Link2) in the QN9080DK is capable of running a JLink debugger interface. You can refer to&amp;nbsp;&lt;STRONG&gt;Appendix B - Updating Debugger firmware&lt;/STRONG&gt; in the "&lt;EM&gt;&amp;lt;QN908x SDK &amp;gt;\docs\Getting Started with MCUXpresso SDK for QN908x.pdf&lt;/EM&gt;" document or alternatively to section &lt;STRONG&gt;4.4 Update debugger firmware to support J-Link/CMSIS-DAP&lt;/STRONG&gt; of the&amp;nbsp;&lt;A href="https://www.nxp.com/docs/en/nxp/user-guides/UM11097.pdf"&gt;QN908x Quick Start User Manual&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Aug 2018 15:43:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Help-needed-to-recover-a-qn9080-dk/m-p/771218#M4725</guid>
      <dc:creator>gerardo_rodriguez</dc:creator>
      <dc:date>2018-08-31T15:43:51Z</dc:date>
    </item>
  </channel>
</rss>

