4 Replies Latest reply on Nov 4, 2019 10:55 PM by NoAr_1540581

    DeneBola (CX3) with J-Link for debugging

    NoAr_1540581

      Hello

       

      DeneBola (CX3) and J-Link are connected and debugged, but debug error occurs. Please refer to the attached document for debugging procedures and survey results.
      Is there anything I can assume about the cause of the error?

       

      Best Regards

      Arai

        • 1. Re: DeneBola (CX3) with J-Link for debugging
          HirotakaT_91

          Could you please replace {cross_prefix} variable with arm-none-eabi- on the "Debugger" tab?

           

          Please look at the latest User Guide. The latest SDK is 1.3.4 as of 25th Oct 2019 and above description is surely mentioning.

           

          Regards,

          Hirotaka Takayama

          • 2. Re: DeneBola (CX3) with J-Link for debugging
            NoAr_1540581

            Hello

             

            They have done to replace {cross_prefix] variable with arm-none-eabi- on the “Debugger tab”. as a result,  the debugger can be connected normally. but, "Step debug"  is not possible. Attach the message displayed on the Console screen of EZ USB below. Could you give me advice on how to improve it?

             

             

             

             

            Best Regards

            Arai

            • 3. Re: DeneBola (CX3) with J-Link for debugging
              HirotakaT_91

              Thank you for showing the error message.

               

              It is expected to see the Bad JTAG communication error while debugging in step mode. This error occurs especially when you do step debugging from main to DeviceInit API.

              This is due to change of CPU frequency during run time.

               

              This can cause a JTAG debug session using the JLINK  debugger to  break. This problem can be prevented by setting up  the FX3 device clocks to the desired value during JTAG initialization itself.

              If the clocks have already been setup to the desired value, the FX3 API does not make any further changes.

              Please add the following code fragment to the set of Initialize commands used in Eclipse based debug configuration.

               

              With this modification, JATG debugging error will be resolved.

              This is mentioned in page 20 of FX3 SDK 1.3.4 release notes.

               

              Best regards,

              Hirotaka Takayama

              • 4. Re: DeneBola (CX3) with J-Link for debugging
                NoAr_1540581

                Hello Takayama san

                 

                Thank you for you reply.

                 

                Best Regards

                Arai