Search Results

Hello Olivier, the threads are only updated on reset or halt. Please try to perform at least one single step before 'info threads'. Best regards Arne

Hello Olivier, could you please add a full log file of the GDB server debug debug session? wiki.segger.com/Enable_J-Link_log_file#J-Link_GDB_Server Which IDE do you use? Could you please add a screenshot of a break in a running task? Best regards Arne

Hello Olivier, FreeRTOS makes it difficult for GDB server plugins to find out the length of some task lists. It will work with the default configuration, but it does not, if you turn on: #define configUSE_PORT_OPTIMISED_TASK_SELECTION 1 So you can either turn off port optimized task selection, or you can add a "helper structure" to your project. This is either "uxTopUsedPriority" (simply holding the value of the highest priority) or "FreeRTOSDebugConfig" (from freertos_tasks_c_additions.h) Best …

Hello, the Flasher Portable PLUS should be able to unlock an STM32F417 MCU in standalone mode. We will check, if we can reproduce the failure. Are you using the recent J-Link software version and did you update the Flasher Portable PLUS to the newest firmware, too? Best regards Arne

Hello, it depends on which device you are going to use. There are several different methods for unlocking chips. Some of them can easily be implemented into the J-Flash project's "init steps", others can for now only be implemented by writing a special connect sequence. Which device are you going to program? Best regards Arne

The power requirements for now are 4.8V to 5.25V. The power supply needs to keep the supply voltage in this range, otherwise the modules will automatically be powered down. We will change the requirements to 4.4V to 5.25V for the next firmware release. Do you have a better power supply available for now? Best regards Arne

Hello, are the module's PWR LEDs lit? If they are not, most likely the output voltage of your power supply is not stable enough or not in the allowed range of 4.8V to 5.25V. The web server will show information about the power status on "Flasher ATE status". Best regards Arne

Quote from Aseris: “Also, what does it mean "FreeRTOSDebugConfig" I cant found any info on freeertos.org neither in J-Link User guide. Just found some code MCUXpresso IDE FreeRTOSDebug Guide freertos_tasks_c_additions.h. Is that a missing part in my project ” freertos_tasks_c_additions.h has a BSD license, so feel free to add it to your project. Probably it will make its way into one of the next FreeRTOS distributions.

Setting configUSE_PORT_OPTIMISED_TASK_SELECTION to 0 will solve the problem, because this makes it possible for the plug-in to gather all necessary information. The freertos_tasks_c_additions.h also contains the necessary information and is independent of other configuration options, so in general I would recommend to use this way. Obviously the change to evaluate FreeRTOSDebugConfig did not make it into the last release of our software. It will be part of the next release. Is "freertos_tasks_c_…

The important part is at the beginning of the log where it shows which symbols were loaded. configUSE_PORT_OPTIMISED_TASK_SELECTION caused problems, but should not be a problem in recent builds where FreeRTOSDebugConfig is evaluated. Could you please post the part of the GDB server log right at the beginning? Should be similar to this one: Source Code (18 lines)

Hello Aseris, the recent version (v6.32i) uses FreeRTOSDebugConfig instead of other sources to acquire information about the tasks. Could you please try this version and check if it solves this issue? Best regards Arne

Hello, sorry for that. I do not know what happened to your inquiry, but it should not happen that it gets lost. The SDK is not needed, the Flasher ATE has its own TELNET command interface for communication. The "Segger Flasher application" (J-Flash) is only required for setting up project files, the resulting configuration files are transferred to the Flasher ATE modules via an FTP connection. Unique identifier bytes can be supplied as so called "patch data" when sending the start command on the…

We could not reproduce any problems here, J-Flash is working stable and reliable with our evaluation board. Are you using an evaluation board too or custom hardware? If custom hardware, can you try with an evaluation board? Which debug probe do you use? Best regards Arne

Thanks for the information. J-Flash does an additional blank check before reading memory, because that is much faster, if a sector is completely erased. Is the log output in J-Flash always exactly the same? Did you already try to reduce the target interface speed?

Hello, the PowerPC architecture is only "partially" supported, but you should be able to connect to the processor, halt it and then read memory. We just gave it a quick try: Source Code (73 lines) Could you please give us more (detailed) information about your setup? Best regards Arne

Hi, there is only one global counter, which is decremented on any successful programming cycle. Best regards Arne

Hello, the crash is fixed in the new beta (V6.11m). Thank you for reporting. Regards Arne

Hello Martin, we found the cause for the failure, the next software release will include a firmware update for the Flashers. Sorry for any inconveniences caused. Best regards Arne

Hello, we could reproduce the programming failure and we will try to fix it as soon as possible.

Hello, as you are already in contact with us via email, could you please stick to this support channel? Opening additional requests makes it harder for us to analyze the issue, because the information gets spread across different locations. Your request is still under investigation, we will get back to you via email. Best regards Arne