4 Replies Latest reply on May 4, 2017 4:13 AM by RayTsou

    ISSM_2016_2_090 flash subsystem problem: always "Launching : Configuring GDB"

    RayTsou

      Hi ALL:

      I am using ISSM 2016_2_090 and Intel CRB doing some testing.

      The ISSM Build information:

        Intel® System Studio for MicrocontrollersVersion : 4.5.0.201703211802

       

      After Update ROM to QMSI-v1.4, I can flash my project into C1000 main core, and the project BSP is QMSI-v1.4.

      But, when I testing flash a simply project(Hello_World) into C1000 subsystem.

      The ISSM always shows :

      GDB_issue1.png

       

      I wait for a long time(at lease 5 min), it doesn't stop. So, I can't flash project into subsystem.

      I had check the CRB with old ISSM version. In old ISSM version, I could flash both and project could running.

      And I also re-install ISSM, but the problem can't fix.

      Could you please help check the problem?

      Or provide any suggestion to me.

      Thanks~

        • 1. Re: ISSM_2016_2_090 flash subsystem problem: always "Launching : Configuring GDB"
          MichelleC_Intel

          Hi Ray ,

           

          What OS are you using ?

          Can you take a look at the OpenOCD Session in the Debug Perspective and let me know what you see there -- set the Log Level to 'Notice'.

           

          -Michelle.

          • 2. Re: ISSM_2016_2_090 flash subsystem problem: always "Launching : Configuring GDB"
            RayTsou

            Hi Michelle :

            My OS is Win10.

            The OpenOCD Session is below:

             

            >>> Command: C:\IntelSWTools\ISSM_2016.2.090\tools\debugger\openocd\bin\openocd.exe -f scripts/board/quark_se_onboard.cfg -c set SEND_IDLE_ALIVE_BLIP 1 -c set QUARK_D2000_SHUTDOWN_ON_TAPSTATUS_FAIL 1

            Open On-Chip Debugger 0.8.0-dev-gff947541-dirty (2017-03-14-22:03)

            Licensed under GNU GPL v2

            For bug reports, read

              http://openocd.sourceforge.net/doc/doxygen/bugs.html

            Info : only one transport option; autoselect 'jtag'

            adapter speed: 1000 kHz

            trst_only separate trst_push_pull

            jtag_ntrst_delay: 300

            1

            1

            Info : clock speed 1000 kHz

            Info : JTAG tap: quark_se.cltap tap/device found: 0x0e765013 (mfg: 0x009, part: 0xe765, ver: 0x0)

            Enabling arc core tap

            Info : JTAG tap: quark_se.arc-em enabled

            Enabling quark core tap

            Info : JTAG tap: quark_se.quark enabled

            Processor type: arc-em

            Info : accepting 'gdb' connection from 3334

            undefined debug reason 7 - target needs reset

            adapter speed: 4 kHz

            redirect to PM, tapstatus=0x00300c1c

            unknown break reason at 0x4003003e

            target state: halted

            target halted due to undefined at 0x4003003e in protected mode

            adapter speed: 1000 kHz

            Info : JTAG tap: quark_se.cltap tap/device found: 0x0e765013 (mfg: 0x009, part: 0xe765, ver: 0x0)

            Enabling arc core tap

            Info : JTAG tap: quark_se.arc-em enabled

            Enabling quark core tap

            Info : JTAG tap: quark_se.quark enabled

            target state: halted

            target halted due to debug-request at 0x0000fff0 in real mode

            target state: halted

            force hard breakpoints

            0x4002f008: 000028a0

            0x4002f40c: 00000060

            ########

            1576 bytes written at address 0x40000000

            ########

            12 bytes written at address 0x40000628

            downloaded 1588 bytes in 0.786499s (1.972 KiB/s)

            0

            Info : JTAG tap: quark_se.cltap tap/device found: 0x0e765013 (mfg: 0x009, part: 0xe765, ver: 0x0)

            Enabling arc core tap

            Info : JTAG tap: quark_se.arc-em enabled

            Enabling quark core tap

            Info : JTAG tap: quark_se.quark enabled

            target state: halted

            target halted due to debug-request at 0x0000fff0 in real mode

            target state: halted

            'write' watchpoint 0 set at 0xa8000000 with length 4 (hwreg=0)

            target running

            • 3. Re: ISSM_2016_2_090 flash subsystem problem: always "Launching : Configuring GDB"
              MichelleC_Intel

              Hi Ray,

               

              I think the issue is that the Application you have running on the Quark(x86) Core is not starting the ARC (Sensor Subsystem) Core.

               

              With the latest version of the ROM the ARC is no longer started by the Bootloader and must instead be started by the Application running on the x86 core.

               

              There is a sample application (under 'Applications' in the ISSM Create Project menu) that outlines what is required to have the x86 Application start the ARC ...

               

               

              #include "qm_soc_regs.h"
              #include "ss_init.h"
              #include "power_states.h"

              /*
              * Start the ARC Running.
              *
              * This example exemplifies how x86 applications may start ARC execution.
              *
              * When ENABLE_RESTORE_CONTEXT feature is enabled, the x86 needs to be ready
              * to resume the ARC after sleep.
              * To achieve this, the x86 core saves its context, and wait for ARC to trigger
              * sleep. After wake-up, the x86 resumes execution where it stopped and
              * resumes the ARC core.
              */

              int main(void)
              {
              #if (ENABLE_RESTORE_CONTEXT)
              while (1) {
                /* Start ARC. */
                sensor_activation();

                /* Wait for ARC to enter sleep. */
                qm_power_sleep_wait();
              }
              #else
              /* Start ARC. */
              sensor_activation();
              #endif

              return 0;
              }

               

               


              -- Michelle.

              • 4. Re: ISSM_2016_2_090 flash subsystem problem: always "Launching : Configuring GDB"
                RayTsou

                Hi Michelle :

                Thanks for your answer.

                After add "Start ARC", I could flash subsystem.