0

Hi,

 

Due to “E2Studio’s workspace bloat” phenomenon I delete the workspace when switching between projects takes several seconds. Today I deleted the workspace and re-imported the project. However when selecting the hardware debug for the RZA1 it fails to connect with the message:

 

Warning: the current language does not match this frame.

 

Since I last did this I have upgraded to E2Studio Version: 5.0.1.005 & uninstalled the GNUARM-NONEV14.01-EABI tool chain.

 

Any idea of what could be wrong?

 

Best regards,

 

Adam.

Open Source Tools Support 回答済
    • Hello Adam,

      The error message displayed by e2 Studio below:

      >>Warning: the current language does not match this frame.

      seems to be the normal behavior for the e2 Studio environment, as the IDE needs to do background processing in order to determine if the current programming language in use is the C language or otherwise.

      Did this continue to happen, or does it continue to happen on a regular basis, preventing the proper usage of e2 Studio? If so, please let me know the exact steps you have taken, so we can try to reproduce the issue on our end and provide further assistance/feedback.


      Thank you,
      The GNU Tools Support Team

    • Hi,

      It happens every time so I am unable to debug the project.

      What I did was as follows:

      1. Work on a project with E2Studio V5.0.0.43 using the GNUARM-NONEV16.01-EABI tool chain and GDB with Jlink.
      2. Upgrade the following components
      e2 Studio 5.0.1.005
      KPIT GNUARM to GCC ARM Embedded Project Import Feature
      Renesas Code Generation Feature
      Renesas e2 Studio Integration Service Feature
      Renesas KPIT GNUARM-NONE Toolchain Integration
      Renesas Optimisation Assistant
      Renesas Smart Help
      Renesas Stack Analysis
      3. Continue on work on the project after upgrade
      4. Delete the .metadata folder in the workspace
      5. Import the existing project
      6. Debug the project & warning message prevents connection

      Usually when the existing project is imported there are both C/C++ and debug perspectives created. On step 5 there was no debug perspective, perhaps that is a clue?

      Any suggestions as to what I can do so I can continue working?

      Best regards,

      Adam.

    • Hi again,

      Just to clarify, please let us know: when you had upgraded the components, did you reinstall version 5.0.1.005 from scratch? That is the recommended approach to upgrading e2 Studio, just so that there are no remnants or leftovers from a previous version, which may affect functionality otherwise after the upgrade.

      Nonetheless, the warning message is not the issue here. That is just a notice, but should not affect functionality.

      You also mentioned:

      >>On step 5 there was no debug perspective, perhaps that is a clue?

      The perspective had disappeared because you have deleted the .metadata folder in the workspace. There will not be any new debug perspective created successfully, until you are able to launch a successful debug again.

      Let us know please if this helps.


      Thank you,
      The GNU Tools Support Team

    • Hi,

      After looking at the change log of the .jlink & .launch files I figured out that the problem must be with e2 Studio. So I ran setup_e2_studio_5_0_0_043 and re-installed e2 Studio and the RZ tool chain. Then re-imported the project. This now allows me to connect to the debugger but it starts execution immediately.

      If I select the RZA1 HardwareDebug configuration the debugger tab has a white cross on a red background with the text J-link ARM does not support the target device R7Z72100. Please check your debug support is up-to-date and that any applicable working sample debuggers are installed. As it works they are installed but e2 studio has forgotten that they do.

      At least I can continue to work. How can I get the J-Link dialog back?

      Best regards,

      Adam.

    • Hi,

      I ran the update tool, which installed the new components. Are you saying that your customers should not use the update tools but to uninstall and then install the new version?

      I’d still need to get the J-Link dialog working again. Any idea what is making that go wrong?

      Best regards,

      Adam.

    • Hi,

      In an attempt to get the RZA1 debugging dialog back I uninstalled e2 Studio and ran setup_e2_studio_5_0_1_005.

      On start-up it registered the RZ tool chain and project generators.

      I imported the workspace and launched the debugger to get the following error:

      Exception occured during launch. Reason: Error in final launch sequence.
      Details:
      Error in final launch sequence
      Failed to execute MI command:
      target extended-remote localhost:61234
      Error message from debugger back end:
      localhost:61234: The system tried to join a drive to a directory on a joined drive.
      Failed to execute MI command:
      target extended-remote localhost:61234
      Error message from debugger back end:
      localhost:61234: The system tried to join a drive to a directory on a joined drive.
      localhost:61234: The system tried to join a drive to a directory on a joined drive.

      So then I thought I’d see if I generated a project (using the new bug fixed generators) to see if I could make a debug connection. On the Select Additional CPU Options there is still no Target FPU option of vfpv3, just none & vfp. I changed the Floating Point ABI to Hard, selected Newlib with all header files and project built library. I built the project and launched the debug connection to get exactly the same error.

      On the generated project the debug configuration debugger tab has the J-Link ARM R7S72100 device, but the imported project still has the white cross on the red background.

      This is very frustrating as all I want to do is to continue working. Any suggestions apart from rolling back to 4.3.0.007 which I started working on the project with?#

      Best regards,

      Adam.

    • Hi Adam,

      While we do offer support for the GCC-based compilers for various Renesas platforms and work closely with Renesas on accomplishing that, we do not offer full-fledged support for the e2 Studio IDE and/or its annexes. The best way to obtain support for it is to either a) contact Renesas directly through their website at https://www.renesas.com/en-us/support/contact.html or b) post your questions on the RenesasRulz forums at http://renesasrulz.com/

      Regarding your message below:

      >> Failed to execute MI command:
      >> target extended-remote localhost:61234

      This seems to be an error caused by the inability to connect to port 61234 on your machine, port which is usually opened when the GDB server is ran/executed. It seems the GDB server is not running properly on your end.

      We hope this helps clarify the issue.


      Thank you,
      The GNU Tools Support Team

    • Hi,

      I got it to work again by reinstalling the Segger Jlink tools.

      Best regards,

      Adam.