Wednesday, November 22nd 2017, 10:57pm UTC+1

You are not logged in.

  • Login
  • Register

Search results

Search results 1-20 of 337.

Today, 2:03pm

Author: SEGGER - Nino

[SOLVED] moving an existing solution

Hello, Thank you for your inquiry. Currently there is no other option than to edit the .emproject file manually. Best regards, Nino

Today, 1:09pm

Author: SEGGER - Nino

Connection with R-Car M3 or Cortex R-7

Hello, This particular device is currently not supported by J-Link nor is the core type. A list of all supported cores can be found here: https://www.segger.com/products/debug-pr…us-and-devices/ Best regards, Nino

Today, 9:34am

Author: SEGGER - Nino

Can not connect to BGM113 Module with Segger J-Link EDU Mini

Hi Jose, Quoted Yes, I already posted: Sorry, I overlooked it the first time. This error appeared to me only when I actively disabled the debug connection to the EDU Mini with the dev kit base board. So it is most likely related to a hardware setup problem. A J-Link issue can be ruled out as the connection works when using the BGM Module + SiLabs dev kit base board. Looking on your schematic from the debug header side everything looks connected correctly. Unfortunately i don't know if this is th...

Today, 9:21am

Author: SEGGER - Nino

J-Link error - "Could not measure total IR len. TDO is constant high." SWD stuck in reset

Hello, The error output you are seeing suggest that the JTAG connection is physically not connected properly. At least TDO is not wired as expected and is pulled constantly high. Please check your physical debug connection again and if all for JTAG needed connections are present. Best regards, Nino

Today, 9:17am

Author: SEGGER - Nino

Connecting J-Link via USB within ARM DS-5 IDE

Hello, Thank you for your inquiry. To connect with DS-5 to J-Link you will need a J-Link Plus or higher model that includes the RDI/RDDI feature. More information can be found here: https://www.segger.com/products/debug-pr…/ides/arm-ds-5/ Best regards, Nino

Today, 9:09am

Author: SEGGER - Nino

SES v3.30 crashes when Monitor Mode Debugging is enabled

Hello, As this issue is not reproducible with the examples we provide this thread will be closed now. Please contact Nordic in regards of issues with their examples. The blog post you linked is outdated and might not work with current ES and Nordic SDK examples. For reference use the example that i linked in my previous post. Best regards, Nino

Yesterday, 2:06pm

Author: SEGGER - Nino

J-Link EDU [JAYLINK_ERR_DEV_NO_MEMORY]

Hello, Thank you for your inquiry. Such an issues is not known to us. Actually that error code is even unknown to us. What exactly is your setup? Which J-Link are you using? Can you show a screenshot of that message? What software are you using to program your target? Best regards, Nino

Yesterday, 1:56pm

Author: SEGGER - Nino

FPU regs: FPU not enabled / not implemented on connected CPU

Hi Abba, It means that the target device has no floating point unit available. Quoted Is it responsible of log issue ? I don't understand what issue you mean. The flashing of the target device seems to be working. Best regards, Nino

Yesterday, 12:02pm

Author: SEGGER - Nino

Flasher ARM with NXP K64 ERR255

Hi audi80, Files have been received. We are currently investigating the issue. Further correspondence will be taken trough e-mail from this point on. This thread will be closed now. Best regards, Nino

Yesterday, 9:54am

Author: SEGGER - Nino

Can not connect to BGM113 Module with Segger J-Link EDU Mini

Hi Jose, I just retested the setup you described with a EDU Mini and had no problems connecting to the device. Could you try the steps described under "Verify functionality using J-Link Commander" and post a screenshot of the complete Commander output? https://wiki.segger.com/J-Link_cannot_connect_to_the_CPU Quoted I can't set Debug Mode to "IN" because Simplicity Studio tell "No local adapter firmware available" That is expected as this feature is only working on the SiLabs J-Link OBs on their ...

Yesterday, 9:37am

Author: SEGGER - Nino

Flasher ARM with NXP K64 ERR255

Hi, Ok, this issue seems to be related to something else. Quoted Where can I send my files to? (jflash & hex) They shouldn't be public.... This is fully understandable, please send the files to support_jlink@segger.com We will then try to reproduce the issue and offer a solution as soon as possible. Best regards, Nino

Yesterday, 9:33am

Author: SEGGER - Nino

Windows Jlink v6.10c

Hi Filipe, Could you provide the example or where to find them so we can try to reproduce the issue here? Are you using the nordic SDK? If so there have been some problems with older SDK versions regarding Telnet applications. So using updated SDK source might already solve the problem. Also did you know that you can use our IDE Embedded Studio for free with Nordic devices and is compatible to the latest SDK? More information can be found here: https://www.segger.com/news/segger-embed…rdic-sdk-u...

Monday, November 20th 2017, 5:44pm

Author: SEGGER - Nino

Windows Jlink v6.10c

Hello Filipe, Thank you for your inquiry. Of course we can provide you with a specific older version. I will contact you regarding this per mail. Generally we do not recommend using older versions. Only in certain fixed production environments it makes sense to stay on older version. With each update we try to stay backwards compatible and improve old features and add new ones. Could you try the latest release version V6.20i and see if the issue persists? About the issue you were seeing. Can you...

Monday, November 20th 2017, 5:36pm

Author: SEGGER - Nino

Can not connect to BGM113 Module with Segger J-Link EDU Mini

Hello Jose, Are you using the following dev kit by any chance? https://www.silabs.com/products/developm…ess-starter-kit If yes then what does the LCD screen say for Debug Mode or DGB? If you want to use a external debug probe like the EDU Mini you need to set the Debug Mode to "IN". You can do that through Simplicity Studio. More information can be found in the Dev Kit User Guide. Alternatively you can use the J-Link OB that is already implemented on that dev kit. For this simply connect the USB...

Monday, November 20th 2017, 2:23pm

Author: SEGGER - Nino

Can not connect to BGM113 Module with Segger J-Link EDU Mini

Hello Jose, Thank you for your inquiry. Such issues are not known to us. Can you post a complete output of a connection sequence when using a J-Link Commander? How is your board powered? Quoted In Simplicity Studio v4 the soft detect the debugger but when I select it appear "No local adapter firmware available". If I push on Download button the software does nothing. Did you follow the instructions described on our website? https://www.segger.com/products/debug-pr…plicity-studio/ Quoted Also, Wh...

Monday, November 20th 2017, 1:37pm

Author: SEGGER - Nino

J-Link VCOM Voltage Levels

Hello Martin, Thank you for your inquiry. All J-Link Pin voltage levels will adjust to the VTref voltage level (Pin 1). Maximum is 5 V. So whatever voltage you apply to Pin 1 will be applied as the high state for the JTAG pins. Low level is always ground. Best regards, Nino

Monday, November 20th 2017, 12:11pm

Author: SEGGER - Nino

Flasher ARM with NXP K64 ERR255

Hello audi80, Quoted Why do you suppose us to use a Flasher ARM v3?? We assumed you would be using a v3 because the issue was only reproducible with that hardware on our side. Sorry for that misconception. Quoted I think our Flasher ARM is new and should work with Software Version V6.20h. This is correct and should be the case. Quoted Are there any issues known with our Flasher ARM and Kinetis K64 target? Usually no. Only if the K64 Flash is irreversibly locked then programing will obviously fai...

Monday, November 20th 2017, 10:43am

Author: SEGGER - Nino

Cannot flash CYW943907AEVAL1F Dev Kit using J-Flash tools using J-Link Plus

Hello, Thank you for your inquiry. The board you are using has only a serial flash equipped. That setup is currently not supported for the CYW43907 device family by our software. The CYW43907 has a QSPI interface however so we will most likely be adding support in the next year. We will put it on the list and support can be expected to be available at the end of Q2 2018. Should you need support added faster than that you have the option to implement it yourself using our open flashloader interfa...

Friday, November 17th 2017, 3:29pm

Author: SEGGER - Nino

[SOLVED] unknown to this version of the J-Link software ?

Hi Abba, Quoted How we label thread "solved" please ? Don't worry about that. I will take care of that. Quoted Now Its flashing correctly with Jlink name reference EFR32MG1PXXXF256, without updating. Glad to hear that it is working for you now. Quoted Do you advise me to update the Jlink ? If, yes how please ? We usually recommend to use the latest software version as we constantly improve our software and add new features. But if you have a stable programming setup running you can stay with the...

Friday, November 17th 2017, 11:55am

Author: SEGGER - Nino

[SOLVED] unknown to this version of the J-Link software ?

Hi Abba, I see that you are using a older J-Link software version. Could you update to the current one (V6.20h)? When you choose ? as your device you should get a pop up window with the device selection window. Attached is a screenshot how it should look like. You can also type in the device name directly, but then you will have to use the exact name that is known to J-Link. In your case it would be EFR32MG1PxxxF256 just like you can see in the screenshot. You tried the name EFR32MG1P233F256GM48...