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 providing additional details. We gave it a quick try on a regular Windows network share, where everything was working as expected. So currently we assume that it has to do with your specific setup. In any case we prepared a preliminary version of Embedded Studio that handles file locations better where locking is not supported/working. To provide you with that version, could you open a support ticket at the following link with reference to this thread? segger.com/support/tec…

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Could you provide more information about your setup? What host OS are you using exactly? How is the drive mounted/mapped? Could you provide an example project with which the behaviour is reproducible with? What are the exact setup and reproduction steps? Best regards, Nino

  • Hello, Feel free to evaluate our software. The *unpaid* part was meant more from SEGGER's perspective. For commercial usage an ES/ESPRO license is always required after evaluation is finished on the users/customers side. Anyhow we have added this TargetDevice/Board to our ESPRO wishlist and is planned to be added in the next couple of weeks. Best regards, Nino

  • Hello, Thank you for your inquiry. The particular chip ETA Compute ECM3532 that is used on this board is supported by both our J-Link debug probes and Embedded Studio. We also have a CPU support package for it so you can get up and running quickly: segger.com/products/developmen…o/technology/cpu-support/ We currently do not have any blinky sample for this board as that would require a board support package. But with the CPU support package it should be very easy to create your own blinky. Or you…

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Do you see the same behaviour with the latest Embedded Studio version? segger.com/downloads/embedded-studio/ If yes, could you provide an example project where the issue is reproducible with? Best regards, Nino

  • Hello, Thank you for your inquiry and keeping us updated. Good to hear that you are up and running again. We will mark this thread as solved now so others can find this thread in future. Best regards, Nino

  • Hello David, Depends on where you do the calls. Could you provide your .jdebug file for reference? Best regards, Nino

  • Hello, Great to hear that you are up and running again. If you require the script file source feel free to open a support ticket here: segger.com/support/technical-support/ However all our trace pex/scriptfiles do all changes in a read modify write fashion so whatever your bootloader sets up will not be touched. So there should be no need to edit anything. But you can of course request it if you desire. Just not all script files are available publicly. We will consider this thread as solved now.…

  • Hello, Thank you for your inquiry. To get trace up and running in Ozone you have to do the target specific trace pin init. We recommend to do this with a JLinkScript file and not within your target application during startup otherwise all trace data from the beginning of your application will be missing as no trace pins were active at that time. A general how to is explained here: wiki.segger.com/How_to_configu…t_files_to_enable_tracing We try to make as many target devices work out of the box a…

  • Hello David, Thank you for your inquiry. Yes you can use Break.SetOnSrc with symbol names directly. How is explained in the Ozone manual in section 7.9.21.3 Break.SetOnSrc. An example project where the a callback is executed automatically after the BP is hit can be found here: wiki.segger.com/Automated_Tests_with_Ozone#Debug_example Best regards, Nino

  • Hello Michael, Could you attach the Ozone project file .jdebug for reference? Best regards, Nino

  • Hello, We took a look at your example code. According to the addresses you see when debugging, 0x2000637a is not aligned correctly which means that your struct is called/used incorrectly. It should be 4 byte aligned but is 2 byte aligned instead. This is not a bug in the compiler but incorrect usage of the C language. It is pure luck that gcc creates other code here that runs by accident. We recommend to revisit your application and how that struct is used. Best regards, Nino

  • Hello, Thank you for your inquiry. We will add this board to our ESPRO wishlist so it will be available in future. This usually takes a couple of weeks if it is an unpaid project. Would your usage be commercial? If yes, the ESPRO package creation and Middleware ports could be prioritized higher. For this feel free to contact our sales team at sales@segger.com to receive and offer and a timeframe. Please make sure to add all details on what Middleware you require exactly for that evaluation board…

  • Hello David, Exactly, and it will most likely have nothing to do with how J-Link is implemented as we have thousands of customers running similar setups without any issues. As you have opened an inquiry in our support system this thread will be closed now to make sure no information is lost between separate channels. Best regards, Nino

  • Hello, Thank you for your inquiry. The issue is reproducible and will be fixed in future. Sorry for any inconveniences caused. Best regards, Nino

  • Hello, Thank you for your inquiry. Could you provide a bit more information about your setup? What version of ES are you using? How is your project set up? Which Run time library, which linker, which compiler etc.? To simplify things, could you provide an example project with which the issue is reproducible? Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Could you provide a project for reproduction which runs on an eval board? Best regards, Nino

  • Hello David, Being able to download to a memory address and being able to execute code from a memory location are two completely separate things. So only if it works for J-Flash still does not mean you can execute or debug from that memory area. As said before, if everything is set up correctly you will be able to debug with Ozone. You could try and see if the application downloaded with J-Flash at least executes stand alone. If not the Flash does not allow execution. If it does, the questions i…

  • Hi David, I assume the FlexBus init is done in that bootloader of yours? Please note that in that case J-Link essentially treats such memory areas that are added behind its back as "RAM" and all read/writes are handled completely on target side. The correct init is then completely user responsibility. If everything is set up correctly this will obviously work. But here it sounds like the init is not fitting to what you are looking to do. Please understand that we can't provide support for chip s…

  • Hello, When you have a bootloader part and application part where you want to debug only the application we recommend to just load the bootloader part before your application part is downloaded: wiki.segger.com/Debug_Bootload…der_and_debug_application Your application will then be downloaded via the elf file you provided to the File.Open function and for this application also all debug symbols will be available. Then just make sure that your bootloader runs through as explained here: wiki.segger…