I am using a SAME70 Xplained microcontroller for a project I am working on. I program it using an editor made by Microchip called MPLAB X. About a week ago, suddenly I could no longer upload any code to the board as I keep receiving the error
java.lang.RuntimeException: java.lang.RuntimeException: TransferFault
Resetting the board, uploading different code or using other features in the program to interact with it do nothing. An important note is that when I got ahold of a brand new board of the same type and tried to upload to the board, it actually succeeded the first time. But then for some reason later the same error pops up again. It seems the issue is a bit more than downloading code as the function in the program which allow for uploading code or pausing the controller throw the same error. I have been struggling with this issue for over a week now and cannot use the board because of it. I cannot find any mention of this issue on the internet. Has anyone ever encountered this? Does anyone know the specifics of what a transfer fault is and can point me in the right direction?
Related
I am trying to publish an appx on the Windows Store built with electron-builder.
In the repport, I get this error: Failed to extract imported API information for this application
I have no idea about what this is supposed to mean and I found no documentation about it. I contacted Microsoft Developer Support that just sent me here.
I found this link that mention the issue.
After two days of trail and error we nailed it. It looks like it has
something to do with the lenght of filepaths to contents inside the
app package.
Notice the difference between the cause and the error message. This probably means that this error is just a random generic error that is raised when something happens, and doesn't provide any meaningful information about what exactly went wrong...
The issue is that now, I have absolutely no idea about how to move forward. Any help is greatly appreciated.
The issue is that the WACK tool developed by Microsoft to test the packages sent to the store is crashing if any file complete path is longer than 255 characters, and it returns that random error giving you the impression that you did something wrong on the manifest.
The best you can do for now is to measure the full path of all the files that are going to be packaged into your app and try to rename the longest ones, or try to reach the Microsoft support. It's 300$ / request, but you can get it refunded as it's clearly their own responsibility.
I have created a number of tools with Google Apps Script, using Google Sheets as a database. Since the move to the new IDE (which I really like), I've seen a new error that I had never seen before.
On two (and so far only two) of the tools I've created, when I go to do a Test Deployment, the new window shows an error message: "We're sorry, a server error occurred. Please wait a bit and try again."
When this happened to the first tool, I did some research, and saw mentions of this happening when more than one user logged into a Script project. That was a possibility for my situation, as I had been in that sheet/project with different usernames. However, everything I had read indicated it was an issue with the Production Deployment; I didn't see anything related to a Test Deployment error. The only solve I had for this was to start a whole new Project and copy the code over.
Now I am seeing this issue on a second project, but it's one that only one user has ever accessed. Initially, it was reported by one of my users who was getting that message on the Production Deployment. When I go into the Project to do a Test Deployment, I'm getting the same error. In Production, it appears to have resolved itself (mostly), as the tool is working again, but it's been up and down some this morning. And even with the Prod Deployment working, I am still unable to run a Test Deployment.
This is not something I ever ran into with the legacy editor. Has anyone else seen this sort of behavior since the new Editor was released? Any thoughts on how this can be resolved, short of creating a whole new project for this specific tool?
Your issue has already been reported in the issue tracker as a potential bug:
There seems to be a workaround though, posted by the OP:
You can also star the request to make the issue more visible:
Note that if the steps are different, you also have the option to file a separate ticket in the Issue Tracker.
I'm trying to find a way of replicating the action / instruction that a physical button being pushed on a control panel sends to the software of a CNC machine of ours.
Ultimately I would like to integrate this instruction into an executable file I could make using AutoIT, but that is further down the line!
After some googling, resulting in all kinds of weird and wonderful results, I'm at a loss of how to begin this task. I believe I need to either use debugging software to find the instruction as it takes place, or possibly Process Monitor?
The machine runs off of a Windows XP machine.
Unfortunately obtaining this information from the manufacturer is not an option.
If anyone could help point me in the right direction that would be appreciated,
Thanks
Edit: I have since come across Windows Hooks, Detours and Interception, but still haven't made much progress!
Your topic is too broad ... You might as well be asking "How do I reverse engineer?" First thing I would do would be to load up the program in a debugger, put a breakpoint in the callback function and find out what the button is doing. What you will most likely find is that it's pushing some information onto the stack and making a call to an external .DLL such as an API or device driver ( you could probably find out which DLL using Process Monitor too ). Just load that .DLL up into your new program and make the same call.
I am getting a lot of crashes in failure report on my Dev Center account like:
XXXXXXX!{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}
_Timeout_expired:_event_type_=_TargetStateChanged,_timeout_modifier_type_=_None,_server_task_currentState_=_NavigatingTo,_tar
MISSING_DUMP_EM_WATCHDOG_TIMEOUT_DEADA444_XXXXXXX!{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}
_Timeout_expired:_event_type_=_TargetStateChanged,_timeout_modifier_type_=_None,_server_task_currentState_=_NavigatingTo,_tar
EM_WATCHDOG_TIMEOUT_DEADA444_XXXXXXX!{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}
_Timeout_expired:_event_type_=_TargetStateChanged,_timeout_modifier_type_=_None,_server_task_currentState_=_Showing,_targetSt
MISSING_DUMP_EM_WATCHDOG_TIMEOUT_DEADA444_XXXXXXX!{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}
_Timeout_expired:_event_type_=_SystemKeyPressed,_timeout_modifier_type_=_None,_server_task_currentState_=_Active,_targetState
I'm not able to fix them in my app because in Failure Log there is no stacktrace for them and this kind of crashes are not catched by Application Insights.
The EM_WATCHDOG_TIMEOUT_DEADA444 error is a big mystery to everyone.
a lot of developers have them in the dashboard and they are not reproducable, and and they suddenly came when the Dashboard got a mayor update.
The error occurs in all kind of apps; with c++ runtime components and without, in background thread and in apps that do not use background threads at all....
Finally; there is not way to get the stacktrace and there is no way to catch it yourself because UnhandledException event doesn't get hit.
Meanwhile I'm ignoring the error, up until MSFT gives a proper explanation in the dashboard what this error means.
PS: if someone magically knows to solve/get more info out of this exceptions; I would love to hear about it.
I am searching for a nice way how to close an WinRT app after fatal error.
This should be used only in last chance error handlers TaskScheduler.UnobserveTaskExcption and App.UnhandledException where I obviously failed to handle it correctly on right places. Should never happen, but...
Desired behaviour: Application should then show 'Sorry' message, log the exception and after user clicks Ok button, app should be closed.
I searched for solutions and lot of results points me, that WinRT must not be closed programmatically. Eg. here programatically close win8 app .
When I call Exit method, app is closed, but afterwards exceptions are thrown, like could not do this and that because app is closing...etc.. Makes me kind of nervous.
How would you solve my problem? It has no sence to keep the app running after unhandled exception, and let it crash by setting Handled = false is not good solution as well I thing. Beside this UnobservedExceptions does not trigger crash. I heard that apps with crashes will be removed from store.
Thx for your ideas!
Referring to the application lifecycle provided by Microsoft, the app should terminate without any warning and return the user to the Start screen.
http://msdn.microsoft.com/en-us/library/windows/apps/hh464925.aspx#app_crash
You should not be closing apps which target the Windows Runtime at all. The app lifecycle management system built-in takes into account many factors including usage statistics and current system resources and will almost certainly make better decisions about when to close apps than you will.