hw | PC periphery and device drivers

valgrind not showing reachable memory leak source

C++ application was built using cmake with following extra options:

My Platform: ZynQ MP; PetaLinux 2020.2

Build system: Ubuntu 18.04

I'm writing a Kernel module which registers itself as a platform_device with compatible string 'erika' with the PetaLinux Kernel on boot.

I specified two memory areas in the system-user.dtsi file for this device (one bigger one (16M) to hold data which will get exchanged between the PetaLinux on the APU and a bare metal implementation on the RPU and one smaller one (4k) to hold signals for a interrupt shared between the kernel module on the APU and the bare metal application on the RPU):

I'm adding a code in qemu-5.1.0 and this code should use a .so file.
I added -ldl to the QEMU_CFLAGS, QEMU_CXXFLAGS, QEMU_LDFLAGS using the configure --extra-cflags/--extra-cxxflags/--extra-ldflags options and can see they are really set.
But when I actually do "make", it gives me this error and I can't figure out what is wrong.

so I am trying to render math formulas in flutter. I am trying to do it with flutter_tex

https://github.com/shah-xad/flutter_tex

I installed the flutter_tex package as explained on the github, but if I want to render a formula (like in the example), I get that error message:

I am currently working on a project for which I am trying to use Deepspeech on a raspberry pi while using microphone audio, but I keep getting an Invalid Sample rate error. Using pyAudio I create a stream which uses the sample rate the model wants, which is 16000, but the microphone I am using has a sample rate of 44100. When running the python script no rate conversion is done and the microphones sample rate and the expected sample rate of the model produce an Invalid Sample Rate error.

The microphone info is listed like this by pyaudio:

Yesterday the emulator was working perfectly. The system image was arm64-v8a. I don't exactly remember the Release name of the working system image but, yesterday there was an update for the ARM 64 system image which I accepted and the release name is "S".

I can start the emulator from my AVD Manager, the emulator also starts when I press the 'Run app' button however, the app isn't loaded on the emulator and the emulator appears offline if I check through "adb devices" or if I click on "Troubleshoot Device connections" it shows:

"emulator-5554 - Device is currently in the offline state"

I have tried most of the suggestions found on StackOverflow like:

• adb kill-server, adb start-server

• Remove and re-create AVD device

• Invalidate Caches/Restart

• Enable USB debugging inside the emulator

• Wipe data and cold boot from AVD manager

  I am using Android Studio 4.1.3

  Build #AI-201.8743.12.41.7199119, built on March 10, 2021 Runtime version: 1.8.0_242-release-1644-b3-6915495 x86_64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o macOS 10.16 GC: ParNew, ConcurrentMarkSweep Memory: 1981M Cores: 8 Registry: ide.new.welcome.screen.force=true, external.system.auto.import.disabled=true Non-Bundled Plugins: org.jetbrains.kotlin

AVD:

There are many question on StackOverflow about detecting whether an iPhone device has a notch in the screen, such as this one. The answers almost always recommend using the safeAreaInsets property of the top window. I have used that in my app to determine whether a status bar should be shown, from the prefersStatusBarHidden method of the currently shown view controller. I would like to show the status bar when there is a notch, but not when not. It works fine in all my tests, but for some customers the status bar disappears sometimes, even though they use a device with a notch (an iPhone 12 Pro Max).

I looked into it, and I think the problem is probably caused by a recursive call to safeAreaInsets, see following call-stack:

It makes some sense. In order to determine how large the safe area needs to be, iOS needs to know whether the status bar needs to be shown. And therefore, it calls prefersStatusBarHidden of the visible view controller, which then uses the safe area to determine that....

Despite the recursive call, it still works for me in tests, but as said, it fails sometimes for some users. I need to work with prefersStatusBarHidden, because at top-level the app consists of a UITabBarController, for which only one tab hides the status bar. The other tabs should always show the status bar, independent of whether there is notch or not.

I have considered checking the device type with sysctlbyname with "hw.machine" argument, and then use a mapping table to get the notch/no-notch result. But that has the disadvantage that the mapping table would need to be updated for each new iPhone model, and that it doesn't work on the simulator, which always returns the Mac machine name.

Any ideas how to solve that in a better way? I could simply avoid the recursive call, but will that solve the problem?

My code that determines the notch right now (Objective-C):

I have been asking several questions for locating and extracting maze from photos on SOF, but none of the answers I get work across different photos, not even across 4 testing photos. Every time when I tweaked the code to make it work for 1 photo, it will fail on the rest of photos due to warped corners/parts or light etc. I feel that I need to find a way which is insensitive to warped image and different intensity of light or the different colors of maze walls(the lines inside a maze).

I have been trying to make it work for 3 weeks without a luck. Before I drop the idea, I would like to ask is it possible to just use Image Processing without AI to locate and extract a maze from a photo? If yes, could you please show me how to do it?

Here are the code and photos:

What is the Open CL command that actually updates the FPGA of an accelerator card with the bitstream included within an .xclbin file created in Vitis with v++ --link -t hw ...?

Otherwise, what are all the possible methods to update the FPGA of an accelerator card with the bitstream included within the .xclbin file created in Vitis?

Thanks