Search Results

Search results 1-20 of 1,000. There are more results available, please enhance your search parameters.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Hello, Thank you for the update. Great to hear that you are up and running again. We will consider this thread as solved now. Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. You seem to be using a rather outdate J-Link software. Could you try the latest version and see if the behaviour improves? If not, could you provide a J-Link log of the failed session? wiki.segger.com/Enable_J-Link_log_file Where do you source the QPSI Flash loader from? Did you get it form SEGGER oder did you write your own? Did you consider the additional information regarding FlashBPs on our Wiki? wiki.segger.com/Unlimited_N…

  • Hello, Thank you for your inquiry. RTT input handling needs to be processed by the target application. For this RTT_API function SEGGER_RTT_HasKey() can be used. An generic implementation over SVC is currently no planned and it is not clear if it would be technically possible in a generic way. Best regards, Nino

  • Hello Henrik, Great to hear that you are up and running again. We will consider this thread as solved now. Best regards, Nino

  • Hello, Due to certain limitations by FreeRTOS, SystemView needs to memorize task names externally on its own. Per default 8 task names will be buffered. To increase this value go to the SEGGER_SYSVIEW_FreeRTOS.h and edit entry SYSVIEW_FREERTOS_MAX_NOF_TASKS to the number of tasks you need. After that all task names should show up. Does this solution work for you? We will improve our manual in that regard. Best regards, Nino

  • Hello Henrik, Thank you for your inquiry. Did you consider the trace defines that need to be set for FreeRTOS explained on our Wiki? wiki.segger.com/FreeRTOS_with_SystemView Quote from HeSa: “Do I need SystemViewer PRO to be able to show all task names or what can I do about it? ” Not needed, with the free SystemView version you can record up to 1 million events including all basic features. Best regards, Nino

  • Hello, Thank you for your inquiry. These defines are needed so FreeRTOS task switches can be traced more easily. For more information we recommend consulting with FreeRTOS support or check the source files. Best regards, Nino

  • Hello, Quote from pweberlth: “When you say erase the whole chip I'm assuming you mean setting the erase -> chip option in the production tab of the project settings? ” Target Manual Programming-> Erase Chip To program use Target-> Manual Programming-> Program & Verify We just retested the modified loader and we always get the attached result that verification was successfull and the STemWin demo runs perfectly. From the log it seems that you are not using the newly provided flash loader but stil…

  • Hello Genis, Thank you for your inquiry. Such an issue is not known to us. We tried to reproduce the issue with a X-TWR-KL28Z72M eval board but everything was working as expected. Which J-Link software version are you using? Could you provide a J-Link log of the failed session? wiki.segger.com/Enable_J-Link_log_file What is the exact device description printed on your MCU? Do you have the reset line connected to the J-Link debug interface? Does programming only a specific image fail or with any …

  • Hello, Thank you for providing the reproducer. With it we were able to reproduce the reported issue. Attached you can find a improved version of the flash loader. Could you test it with the attached version? Make sure to erase the whole chip before reprogramming it. Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Which J-Link software version are you currently using? Could you provide a J-Link log file of the failing session? wiki.segger.com/Enable_J-Link_log_file Could you also provide the .hex file for reproduction purposes? Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Are you using custom hardware or an eval board? We tried to reproduce the issue with a SAMV71 XPlained Ultra eval board which is recommended by Microchip for SAMS70 series evaluation and we could connect always to the board without any issues. We assume it is related to bad signals between J-Link and target device. Could you try another cable between J-Link and target? How do the signals look like? Could you measure them with a…

  • Hello, Thank you for your inquiry. For the reported issue a change in the Flash loader algorithm is most likely needed. As this forum is not our official support channel and you seem to be working for one of our partners, we recommend getting in touch with us in this regard via e-mail. More information can be found in my signature. Best regards, Nino

  • Hello, Thank you for your inquiry. If the third party toolchain is not directly supported the importing must be done manually. So create a generic project for your target device in Embedded Studio and add all required files to the project. Best regards, Nino

  • Hello, Thank you for your inquiry. We would need a bit more information about the issue. What OS are you using? How did you install Embedded Studio? Which version are you using? How did you create the project? Best regards, Nino

  • Hello Mario, Thank you for your inquiry. 1: This is intended behaviour as stack and heap are not sections with symbols in them. Should you try to reserve to much memory for stack you will get the appropriate linker warning. EDIT: After further discussion with our Embedded Studio team, heap and stack will show on future version of ES again when using SEGGER Linker. 2: This behaviour should be improved with our latest ES release V3.52. Could you give it a try? Do you still get no errors? Best rega…

  • Hello, Thank you for your inquiry. Could you contact us per e-mail for further proceedings? You can find contact information in my signature. This thread will be closed now. Best regards, Nino

  • Hello, We received your inquiry per e-mail as well. Please try to keep future requests to one communication channel so no crucial information gets lost. As this is no support forum we suggest contacting us preferably per e-mail should you be entitled to support. More information can be found in my signature. This thread will be closed now. Best regards, Nino

  • Hello, Quote from ollittm: “How does Ozone handle e.g. showing source lines if you're using CCS (eclipse)? ” Sorry, I don't quite understand the question. With Ozone you can take CCS output and open it with Ozone. The source files will then be displayed when needed during debugging. Quote from ollittm: “WRT Texas evaluation boards, no such luck I'm afraid, they use ARM-20 header without the extra pins. ” This is quite unfortunate. We will see if the available boards can be used for at least a fl…

  • Hello, Thank you for your inquiry. Which target device are you debugging? To make a SWO printf stream visible we suggest using JLinkSWOViewer which is part of the J-Link software package. Best regards, Nino