Search Results

Search results 1-20 of 32.

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

  • That's why I wrote "and friends": forum.segger.com/index.php/Att…529bdfcde39e9afa83b7392a5

  • You could create a small tool (read: a shellscript, a python program or whatever your favorite poison is) that generates a unique timestamp in a headerfile that is included in your software. Run that in each build through the Pre-Build command settings ("Options > User Build Step > Pre-Build command" and its friends). That's how I do it. However, be aware there are small issues with this - there's a slightly different behavior between building from within the EDE and through emBuild. Alternative…

  • There is one in the debugger. Just load your executable, open "stack usage", than choose main from the list of functions. You can easily drill down from there. It's not ideal and the callgraph isn't available in the editor environment but it seems to work.

  • Quote from SEGGER - Nino: “ Dynamic folders have a little red arrow icon next to the generic folder picture in the Project Explorer window ” In that case I'm not using dynamic folders. I'll try and provide an example soon - prolly need a couple of days though. If you keep this thread open for now I'll make sure to attach it here.

  • Project Options, Debug > J-Link. At "Host Connection" you can choose "USB" and add the serial number of your J-Link (see the defines in the bottom of the dialog). Disclaimer: I did not check if it works but it seems as if it should.

  • Hi, Yes, the header filename does not change, it's always the same. Dynamic or static virtual folders? How do I check that? I did notice that sometimes SES complains it cannot remove the project.dep file (where project is the project's name). It does continue compilation when that happens. Is this related to this problem? I'm using SES 4.16 by the way but it also happened when still on 4.12.

  • Is it just me or does SES not keep track of dependencies correctly? In my project, I have a single headerfile that is generated by a shellscript. The shellscript is part of the build process. We use this to insert version information from our build system, define names etc. So, it changes a file named "svnversion.h" which in turn is included in several modules. We use a shellscript that runs the shellscript (resulting in a new svnversion.h), and consequently runs emBuild. emBuild doesn't honor t…

  • This issue has disappeared after an hour or so. Must've been a hickup.

  • Trying to download SES for ARM for a Linux host (either 32- or 64-bit) from segger.com/downloads/embedded-studio. Both (32-bit and 64-bit) versions don't start a download but send me to an old-looking download page. Is SES for Linux not available anymore?

  • Fair enough. The workaround basically is what I built myself. The disadvantage of using such a solution is that the extra hardware spoils the power profiling, so I'll just use the good'old 1 Ohm resistor and oscilloscope.

  • Ah, thanks for the heads-up. Will I still be able to see power consumption and voltage levels through this webserver? Also, thanks for the pointer to the power profiling features from oZone. I'll sure play around with it when I find some spare time! It is a pity the probes provide 5V Vcc only. I think it's safe to assume most (if not all) modern low-power designs require lower voltages (my hardware for example will run from a single CR2032 battery once it goes into production - the nRF52 and the…

  • Hi Nino, The latest and greatest v6.44 "suffers" from the same issue. It's no biggie since it's clear that either there's just a decimal point missing or there's a mismatch in unit of measure of course, it's just silly. Quote from SEGGER - Nino: “The J-Link software version you are using is quite old, could you try the latest one and see if the values improve? ” Anyway, 50 uA accuracy would be good enough for daily testing and power optimisation.

  • I'm feeding my target hardware from the J-Link Pro when debugging. The 5V output is regulated down to ca. 3V using an LM317T. The hardware connected to it is known to peek at ca. 10 mA. However... the J-Link Control Panel however says: forum.segger.com/index.php/Att…529bdfcde39e9afa83b7392a5 Yes, it really says "18161 mA". That's 18A and a continuous current of 6.2A. Whoa! I guess it is using smoke signals inside the processor core! (hint: there's a couple of decimal points missing). On a more s…

  • I had this same problem, see [ABANDONED] RTT Viewer 6.40 slow? (never got a notification from the forum software therefore I had not seen it was answered). We noticed the behavior depends on the host machine in use. We had this problem on several laptops and one desktop, all running Windows 10 Pro. In the end, we found a single machine (some HP laptop) where RTT ran sluggish / slow on 2 of the available USB ports but ran fine on a third one. Unfortunately, that specific laptop belongs to a custo…

  • Huh, sounds like it doesn't take the settings from sdk_config.h. do you define USE_APP_CONFIG by any chance? Let's check if something weird is happening: 1. Load your application in the SES debugger. 2. Set a breakpoint on _DoInit. 3. Run until the app hits this breakpoint 4. Set a new breakpoint on the end of the function. 5. Continue execution until the app hits this breakpoint 6. At this second breakpoint, open a Quick Watch on p 7. Drill down to aUp and aDown as shown below What are the valu…

  • Okay, I'll answer this myself In the SES debugger, you can actually read from files that will be opened on the host. Don't know if it'll work from oZone too, too lazy to try out. Note: the library does not contain freopen() and "stdin = fopen( ... )" did not really do the trick - no redirected stdin.

  • Quick question to which I could not find an answer: is there a hosted filesystem simulation in SES? I would like to execute a script that contains timed simulation stimuli where the script is stored on an RTT host.

  • Check the blocking mode used in RTT: in sdk_config.h, the macro SEGGER_RTT_CONFIG_DEFAULT_MODE decides what should happen when the RTT buffer is full (not cleared by your J-Link). I bet it is set to "2" ("BLOCK, Wait until there is space in the buffer"). Switch to a non-blocking mode and recompile.

  • Quote from SEGGER - Nino: “If I now go to my project settings ” At that exact point you start "hiding" the setting in a vendor-specific way because one needs the IDE installed and up and running to see it. I can't see the definition in the sourcecode, I can't see 'm in a makefile (note: "make" is a defacto standard, every engineer should be able to read makefiles IMHO). If I want to add definitions, I can't just take out vi or emacs (insert your favorite editor here) and create them - I need to …

  • Unfortunately, the solution you mention is merely a method that still hides the macro definitions somewhere in the IDE. We'll just have to live with it I guess, if there just is no way to do pre-include the header we'll just have to document them in such a way they won't be "forgotten about". Fair enough. Thanks for your help anyway Nino!