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 your inquiry. The reported issue is reproducible. It will be fixed in future so other expressions other than == will work again. Best regards, Nino

  • Hello, with the new Embedded Studio versions the projects are usually based on the new SEGGER run time library. You can check what your project is based on in the project options. For SEGGER RTL we recommend the following guide: wiki.segger.com/Embedded_Studio_Library_IO Best regards, Nino

  • Hello Matthias, Such an issue is not known to us. What is the serial number of your J-Link plus? Does programming board #1 work when using J-Link Commander? Could you provide a J-Link log of the session with board #2? wiki.segger.com/Enable_J-Link_log_file Best regards, Nino

  • Hello, I just tested the default Hello World example on a TMC570LC Hercules board (example attached) on Fedora 33 and there everything is working as expected. Could you give the latest Ozone version a try and see if the issue persists? Quote from v01d: “I can tell you that if you start with just a sample default code startup for the TMS570xxx chip using their/TI default code you should be able to get it straight away. ” What does "their/TI default code" mean here? Where would I source this from?…

  • Ozone crashing consistently

    SEGGER - Nino - - Ozone related

    Post

    Hello, Thank you for your inquiry. Such an issue is not known to us. Could you give the latest Ozone version a try? Do you still see the crashes? Are they reproducible reliably? If yes, what are the exact reproduction steps? Best regards, Nino

  • Hi Martin, Yes we were able to fix the issue. Great to hear that it is working for you. Best regards, Nino

  • Hi, this is not a support forum. If you are entitled to support please use our official support channel as explained in my signature. Best regards, Nino

  • Hi Steve, The importer will simply import whatever the CudeIDE project is at that point. A reimport is not available. Best regards, Nino

  • Hi, Thank you for providing the file. However it displays perfectly fine on my Ozone setup, see attachment. Did you change any of the default Ozone settings in the preferences that are font related? If yes, could you change them back to default ans check again? What host OS are you running on exactly? Are you using the 32 bit or 64 bit version of Ozone? Best regards, Nino

  • Hi, The importer was tested for Windows only for now as CubeMX was not always multi platform. So it is possible that some paths may not be matching for the import. We are currently planing on creating a little guide on how to import CudeMX generated projects to Embedded Studio and will check the other platforms as well. Best regards, Nino

  • Hi, it should make no difference what J-Link you are using. Best regards, Nino

  • Hello, Yes Delay functions can be helpful. But as said the implementation is target specific. With Arduino you have thousands of files in Arduino software taking care of this under the hood. Same goes for the ST HAL in CubeMX. Someone has to implement the function. We do not do this as it does not make sense to us to create yet another HAL and try to compete with ST. But you can of course also use the ST HAL in an Embedded Studio project and then you can also use the same delay function. You can…

  • Hello, Thank you for your inquiry. Currently it seems that chinese characters in textblocks are not supported. Could you provide a text file with some chinese characters for reference? We will add this as a feature request to our wishlist. Best regards, Nino

  • Hello Martin, The issue is indeed reproducible. We will check if this is something that can be fixed from our side. Best regards, Nino

  • Hello Martin, Thank you for your inquiry. Such an issue is not known to us. Kubuntu is not one of the tested distributions by us, but it should still work as well as with Ubuntu. Anyhow I will try to get a hold of an Kubuntu VM and see if the issue is reproducible. In the meantime could you give the portable tarball of Ozone a try? segger.com/downloads/jlink/Ozone_Linux_x86_64.tgz Does this work on your setup? Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Could you give the latest SystemView and J-Link software version a try? Do you still see the issue then? Best regards, Nino

  • Hello, Thank you for your inquiry. As mentioned in your other post the CPU support Packages provided by Embedded Studio will give you access to CMSIS files from the silicon vendors, but not the HAL or SDK or whatever else a silicon vendor might offer. One of the files is e.g. the system_stm32f4xx.c (or what ever STM32F subfamily you are using). There you will find function SystemInit(). There the clock init is happening. The CMSIS default will give you a setup that should run on any board with t…

  • Hello, Thank you for your inquiry. There is no generic way to implement a time based delay function for embedded targets. It is always target and architecture specific. So providing a "generic" function is not possible as we are supporting all Arm targets and not only ST. The CPU support packages provided with Embedded Studio give access to the Arm CMSIS layer for that particular device which gives you all you need to get started with your chip bare metal and have the whole chip described via re…

  • Hi, Quote from MUETA: “I am not really where such an approach ends ” Well it ends there where you have resolved all dependencies and added all needed sources to your project. Not sure what you expect here. It is always the same approach when writing software. Please understand that setting up a custom project is user responsibility which we can't provide support for. Best regards, Nino

  • Hello, Thank you for your inquiry. The focus should be on the yes by default. Could you reupload your picture? It did not seem to have worked the first time. Quote from TxCodeMonkey: “for reference, Big Sur, V3.22d (V3.22e is not usable on Big Sur) ” How so? We have many customers using V3.22e on big sur. What is not working? Best regards, Nino