STM32F407 memory layout - ram

I am trying to use Percepio trace lib for FreeRTOS in Snapshot recorder mode.
After compilation and running it on my discovery board I need to somehow dump entire RAM to file.
I've started ST-LINK utility but I am puzzled on how to dump entire RAM.
Could some give hint on that matter?

You can find the memory layout on page 71 of the STM32F407xx Rev8 datasheet.
As ejohnso49 pointed out the SRAM of this chip is not contiguous. So you need address them twice (green and yellow area in the picture) to read out the whole data.
In STM32 ST-LINK Utility connect to device and enter 0x20000000 for address (start of SRAM, first section). For size enter 0x20000 0x30000 (128kB 192kB).
Now you can see the contents of the RAM in the window. For dumping the current view either click on the save icon or in the file menu on Save file as.
Do this also for the other CCM RAM section if you want.

Related

Expose GNU Screen's entire scrollback buffer without holding up arrow forever?

When I reattach to a screen session, it only fills up my current terminal's window size worth of the scrollback buffer. If I enter Copy mode (ctrl+a [) then I'm able to scroll up the buffer (using the up arrow key) and "uncover" the history of this session (one line at a time). I have my scrollback buffer set to 30000 and some of the output that I want to see is very long so this can take a long time.
I tried using the hardcopy command, but that only saves whatever has been uncovered by me. I tried using g within copy mode, but that only jumped to the top of what had been uncovered. The full scrollback buffer is clearly still there because I can uncover it using the arrow key, but I can't figure out how to access the entire thing without holding the arrow key for a very long time.
Ideally, I'd be able to issue a command to store the whole screen session's past output to a file (or at least up to my screenbuffer limit). Which is what hardcopy is supposed to do. But since it is only saving what has been uncovered by my up arrow, this is useless for my situation.

How to show the whole buffer in emacs minimap?

I am running Doom Emacs with the minimap enabled in init.el.
I would like emacs-minimap to show the whole buffer and not just a part of it, so that i can see where i am in relation to the whole file.
However, i didn't find an option to define the amount of lines that the minimap shows.
How can i set emacs minimap to show the whole file?

Issues with IntelliJ on a 4K screen

I splurged and bought one of those high definition 4K screens. More specifically, the Dell UltraSharp 4k UP3216Q 31.5", combined with a new PC running Windows 10.
When the computer occasionally reboots, it goes into a mode where when I load IntelliJ, it shows the following error message:
8:16 PM You may need to manually configure the HiDPI mode to prevent UI scaling issues. See the troubleshooting guide.
The interesting thing is that when it's running in this mode, I actually like the way IntelliJ looks. I like it because it's running in true sharp 4K mode, and at the same time, all the fonts are large enough to be legible, and not require a magnetic resonance microscope or a monocle to make out the letters.
However, other times, when the system boots up, I do not get that error, meaning everything is functioning normally, but in that case, all the fonts are so tiny as to be illegible. It literally hurts my eyes to look at it, and the only alternatives I have left at that point is to either drop down from 3840x2160 into 1920x1080, or to go into the settings, and start increasing the font sizes, which is annoying. Not to mention that if I drop down into 1920x1080 mode, then the quality of what I am looking at degrades, everything starts looking pixelated...
Is there anything that can be done to stabilize the situation on these new 4K screens so that IntelliJ looks normal?
Try this:
Help > Edit Custom VM Options:
-Dsun.java2d.uiScale.enabled=true
More information can be found here:
https://intellij-support.jetbrains.com/hc/en-us/articles/115001260010-Troubleshooting-IDE-scaling-DPI-issues-on-Windows
If that does not help create a ticket in the JetBrains issue tracker: https://youtrack.jetbrains.com/
They are usually very responsive.
Another possibility is that you have the Windows UI scaling value for the screen set to a non-integral value in display settings. This messed me up, I had the setting to 175%, while the default is 200%. Intellij (and many other applications) will not scale properly if that is set to a non-integral scaling value.
As soon as I switch this back to 200% Intellij scales perfectly.
I fix this problem after setted env variable IDEA_JDK_64 to jdk path in windows 10

RealSense R200 Playback error

I have recorded an RSSDK file with R200 on my laptop. But when I try to playback the file on my desktop PC, the depth stream displays correctly, however the color stream doesn't display correctly (example shown as below). At the same time, both streams can display correctly on the laptop.
Does any one know what is the problem? How can I solve it?
Thanks.
snapshot of playback
You need to have Intel GPU enabled on your desktop and latest Intel Graphics driver installed for H264 color playback. Alternatively, you can configure your laptop to store uncompressed/LZO compressed color stream (see documentation for details, there are registry keys for that). But it may be problematic for HD resolution depending on your CPU/hard drive speed. Another option is to decompress H264 streams using clip editor tool after recording.

How can I change the monitor resolution on a Banana Pro?

I'd like to change the resolution of my monitor, connected via HDMI from a Banana Pro.
I get a list of available monitor resolutions by the following command:
cat /sys/class/graphics/fb0/modes
and then pick one of them that I want to use, say:
D:1280x720p-50
(1280x720p, 50 Hz refresh rate)
I've edited the /etc/rc.local file to include
echo D:1280x720p-50 > /sys/class/graphics/fb0/mode
Saved the file, rebooted - no change from the default resolution.
I figured this out with a bit of tinkering.
Remove the SD card with the linux image on it, and stick it into a computer that can read it.
Open up the uEnv.txt file to edit it.
Change this
disp.screen0_output_mode=EDID:1280x720p50
to this
disp.screen0_output_mode=1280x720p50
The EDID argument tells the kernel to try and use the monitor's settings to determine a resolution. Removing it forces your selected resolution to be used.
For some reason, this defaulted to a really low resolution for my screen with the Banana Pro.