I'm running with OMNET 5.0 veins 4.4 and SUMO 0.25.0 ...
Everything works fine until the last time when I tried to run my code the simulation window does not appear but its icon exists in the taskbar and the simulation crashes with this error
I have all reinstaller but the problem persists (I have read in other topics that I have to verify the versions but my version is countable according to http://veins.car2x.org/download/)
Can you help me please ?!
I know only OMNeT++ Version 5.0 with INET 3.4 and Versions before ...
In OMNeT++ is Language C++ used, you have to take about nullptr or
garbarge in memory.
The first step is to run GDB in OMNeT++ this graphical user interface
in eclipse editor is quite enough to get neccessary information.
If it don't run after simple checking memory, objects, nullptr, exceptions and so on. See working with valgrind http://www.eclipse.org/linuxtools/projectPages/valgrind/
But usally it is enough to workout with GDB, try to initialize everything, check exception and it works sthhow ...
Related
In using the Pickit4 for flashing the code.
When I first open the MPLAB X IDE and use the Make and Flash button to flash the MCU, it works fine.
But the next time in the same session, the Make and Flash button goes grey and does not do anything and I get and error saying:
Failed to initialize PICkit 4.
Then when I try to clean and build, I get an error saying:
Script engine is not supported.
I have tried deleting the persistent files and starting fresh, but the errors remain. I tried with multiple different projects, but I still have the same issue.
I'm not sure what do do next?
Is it a PICkit 4 issue?
How can I fix this?
I started seeing the same thing today. Worked fine for months until now. No MCC installed. Turns out some packs were out of date. I updated them and everything is back to normal so far.
PicKit 4
Product Version: MPLAB X IDE v6.05
Windows 10 Pro 22H2
PIC16F887
This is an issue of the MCC:
If you want to work with MPLABX5.05 you need MCC 5.2.2 (or the other way around)
It also may be neccessary when upgrading to MPLAB X IDE v6.05/MCC v5.2 on an existing MCC Classic configuration it may be necessary to update your MCC libraries for some GUIs to display properly
I am working on a IddCx indirect Display Driver. I have run into a bug that I cant find any reason to blame my own code on. Every two seconds or so IddCxSwapChainReleaseAndAcquireBuffer takes over 100ms, up to 8000ms to complete. It normally takes below 16ms to complete (depends on your frame rate).
I even added timestamps to the IddCx Sample code from Microsoft. It still has this issue, so it cant be a fault with my own code. I have exhausted most of my debugging options.
Changing IddCx versions I am compiling with (1.4 to 1.8) by targeting the libs, the headers, and defining the macros (IDDCX_VERSION_MAJOR, IDDCX_VERSION_MINOR, IDDCX_MINIMUM_VERSION_REQUIRED). 1.9 btw doesnt seem to run well, IddCxDeviceInitConfig() fails with Invalid Parameter if I choose version 1.9.
Changing which UMDF version I am compiling with (2.25 to 2.33).
Changing the Windows SDK version I am using (10.0.19041.0, 10.0.20348.0, 10.0.22000.0, 10.0.22572.0).
Swapping my OS to the Insider Program preview version of win11 (currently 22000.588 co_release).
Things I think may be solutions that I need help on.
When I am running the Driver, within dxdiag, the display says its using WDDM version 1.3, while my other displays use WDDM version 3.0. WDDM 1.3 is old, so maybe this could be causing issues? How do I tell visual studio to compile my driver to compile with WDDM version 3.0? Does my driver need to WHQL Logo'd first?
IddCxGetVersion() returns with version 1801 or 1803 no matter what I change (SDK, IDDCx version, etc), which is from 2018! So what am I doing wrong here to get the OS to choose to use a newer version of IddCx? This may be related to the WDDM version being 1.3 instead of 3.0.
Swapping back to Windows 10. I originally swapped to Windows 11 because the WDK dev environment is completely unstable, with the samples sometimes not creating functional drivers, that fail to call into 'EVT_IDD_CX_ADAPTER_INIT_FINISHED', I have confirmed its being compiled incorrectly (sometimes) on windows 10, and the old dlls from earlier that day will still work, but the new dlls will not. So thats why I am staying with Windows 11, I also need to swap to Windows 11 anyways since we should be moving forwards, not backwards.
forgot to close this.
Realized the issue was that the monitor desktop simply wasnt updating. So the OS was just rendering the desktop less often, resulting in less frames being pushed to the swapchain for me to grab
I've a modified version of kernel 5.6.0, I followed the instructions showed here to compile and to install it. The process goes well, but when I boot my compiled kernel, the screen freezes on "Loading initial ram disk", I found the same problem here, but there is no answer to the question. I would like to know how to solve this problem, I've already tried to compile the kernel on different distros but all of them be stuck at the same screen.
I was running my simulation in OMNeT++ 3 months ago, and now that I've tried to launch it, it says initializing and it's stuck. The only "error" I get is the java.lang.runtimeError which doesn't really say much. Even that error doesn't pop up, you need to bring it up by clicking inside the OMNeT IDE. I am using OMNeT++ 5.4.1, SUMO 0.32.0, and Veins 4.7.1.
Sumo was checked with the gui, and it runs normally. I don't know which java version needs to be installed..
Picture attached,
Simulation stuck
Please if any1 could offer a solution?
The .metadata directory in your workspace contains a detailed log of the IDE. I would try to upgrade to OMNeT++ 5.6.2 though, to use a later version of the IDE (and Eclipse which the IDE is based on)
I wonder why every once in a while, Intel RealSense 3D camera fails to start? I have re-installed the drivers and SDK as well as the DCM but still it is whacky and very unpredictable. Any idea what the source of the problem could be? It should be able to run the examples in the SDK in a normal working situation.
Well, previously that it couldn't init problem was that only two of the its drivers could be recognized (not the virtual driver) like the following but now all of its driver are recognized and still it can't init.
so I am receiving an init failed message when running the SDK examples.
Any pointer for fixing is really appreciated.
If you are also showing an integrated webcam (other than the 3 RealSense listings), try disabling that so the RS camera can be seen as the primary.
Actually you can select the device you want to run the sample on in the menu "Device". If you installed the RealSense correctly and if the latest DCM is running (the current version is 1.4 if I remember), you should be able to select the RealSense device there and then run the sample.
Sometimes the DCM Service fails to start (e.g. if you force-restarted your machine recently). Then you just need to make the service restart and it should work.
Hope this helps.
I’m also facing the same problem (on windows 10), and found a way that solved it for me: search “Scanners and Cameras” in Control Panel, choose “Add Device”, under “Manufacturer” choose “Intel” and under “Model” choose “Intel(R) RealSense(TM) Camera SR300 Virtual Driver” or the version you use, and continue to install.
Have you installed the right drivers? There are two versions of the real sense cameras. The Windows 10 works with Intel Real Sense R3 which has completely different architecture than its predecessor.