Xpatch.bin error

#1

Hi ,

Trying to an axoloti running under windows 8.1. The unit works fine under osx however i get the following error when I attempt to compile a patch.

I would copy the error but there is no way to copy the text from the axoloti window. Going to the edit menu and choose ctrl+c as the option does not copy the text.

I will type the error out.

Finished loading objects

Generate Code complete
Start compiling code
Done compiling patch
Start uploading patch

bin path: C:\Users\username\Documents\axoloti\build\xpatch.bin
FileNotFound Exception,java.io.FileNameNotFoundException: C:\Users\username\Documents\axoloti\build\xpatch.bin (The system cannot find the file specified)

at java.io.FileInputStream.open0 (Native Method)
at java.io.FileInputStream.open(FIleInputStream.java:195
at java.io.FileInputStream. (FileInputStream.java.138)
at qcmds.QCmdUploadPatch.Doo(QCmdUploadPatch.java.64
at axoloti.USBBulkConnections$Transmitter.run(USBBulkConnection.java:885
at java.lang.Thread.run(Thread.java:745)

Disconnect request
Done uploading patch

When I navigate to that folder to see if xpatch.bin exists it does not.

The only file in that folder is called xpatch.cpp

Any advise welcome.

Thank you

ted

#2

did you not get any other errors?

basically the patch didn't compile... and so you should have had a whole bunch of errors.
the usual reason for this is the Runtime is not installed, or not installed correctly, or your anti virus is blocking it.

see https://sebiik.github.io/community.axoloti.com.backup/t/installing-on-windows

#3

Hi ,

I have attached a screen shot of the complete error log window.

This errror occurs with any and every patch. I have up till this point been using osx and everything has been fine and dandy. So I know the boards etc are good.

Thank you for your time.

Ted

error.jpg1536x864 83.6 KB

#4

DId you check the anti virus logs ?

#5

Hi ,

What specifically do you think I should be looking for in the logs?

There is nothing there that pertains to axoloti in anyway that I can see. I saw no virus warnings when installing either the axoloti runtime or the .msi installer.

The axoloti_runtime folder is in program files(x86) as expected.

I have checked my java installation and according to the java application everything is installed as it should be. I installed the version linked from the axoloti site. 1.81 I believe.

Any thoughts?

ted

#6

yeah, my thoughts are simple...

your logs show that compilation was successful... there is no error saying it cant file the compiler, or that xpatch.cpp cannot be compiled.
the compilation will result in a file called xpatch.bin

so... that implies some thing is deleting or moving it, in between the compilation state and the upload stage. as you can see from the error (FileNotFound) when it attempts to upload, its simply not there.

the question is where has it gone? what moved it?

the only thing i know of that moves things is anti virus software, when it becomes suspicious of a file it quarantines it.

what you could try to do, is to add the build directory (as noted in your logs) to the anti virus exclusion list - and try again.

really thats the only idea i have, i cannot see why else it would successfully compile, yet not have a file to upload.

#7

Hi ,

Thank you for the reply.

I disabled my anti virus software.

I also added an exclusion. Just in case....

Tried to run axoloti.

Same error.......

Thoughts?

Thank you.

#8

FYI..

Added an exclusion for both the runtime folder and the main axoloti folder and all its sub folders....

#9

sorry no idea then...

if you haven't already try deleting the build directory (which axoloti is closed), perhaps something is corrupt in there.

after that, id probably start trying to run it from the command line to see if anything shows up, but honestly not seen this before - so not sure what to suggest.

other than that, delete everything axoloti/runtime/document directory and re-install...but just because i cant think of anything else.

#10

Hi ,

Thanks for the reply.

I un-installed axoloti completely. Both runtime and main program folder.

Re-installed everything again with no anti virus software even installed on my computer.

Exactly the same error occurs.

I am going to guess at this point your not going to attempt to provide any more 'support' and that as a user and customer I am 'shit out of luck'.

Not particularly helpful or re-assuring.

I have seen your comments about being unpaid help and frankly that is a bit sad.

Johannes (hope I have spelt that correctly apologies if not) this does not reflect very well on you here.

Some of us have invested quite heavily (in relative terms on this platform) I own 5 axoloti's myself.

I have been using the exclusively under osx till this point in time.

To just be told 'sorry I have no clue' is not really acceptable for a product you are taking money for.

Whilst I appreciate that when it comes to patching and the like that axoloti is a very buyer beware type product.

However when it comes to installation and simple usage problems I do expect some what better help and support than some unpaid persons good will and knowledge.

I am not one to be critical usually but having read quite a few posts on this 'forum' I have to say the attitude towards helping users especially those who are less technical leaves a lot to be desired.

Being told 'I cannot think of any thing else' is not really acceptable. It is the typed version of shrugging and walking away. Not particularly conducive to the creation of warm and fuzzy feelings inside.

I know the problem is not user error or my pc being weird or what have you as I simply do not experience any kind of problems with any of piece of hardware I have of which I have many dev type boards attached and working without problem. I am not a clueless idiot with these types of things.

Any further advice/help welcome'd however I feel none is going to be forthcoming. Sadly.

Thank you

Ted

#11

frankly, as the person that tried to help you, i find your post pretty offensive.
I was not saying, i didn't want to help, rather i had run out of ideas...

cool, then you should understand the difficultly...

1.0.12 is not a new release, its been successfully installed by many users on windows including 8.1.
Ive offered suggestions based on things we have seen crop up from time to time.

so the question has to be is... what is different about your setup (compared to those that had it working ok) ? once that is identified the solution will be forthcoming - your attitude of 'its not my problem, its a general axoloti issue' , is frankly not helpful - we are not after 'blame' here... we are after differences that might cause issues.

you should also note in my 3rd post, I even explained to you the underlying problem (the file not being present, but appearing to have been compiled), my hope was this by explaining the issue, you might be able to contribute something more to the problem, something that might 'advance' the problem - give new clues

also you didn't say ... did you delete the build directly as i suggested?
another suggestion, if you edit the prefs file, you can turn on expert , then try to do a compile... but without upload, and see if the xpatch.bin is created.

#12

I got the opportunity to check this again on my windows machine, and my first assumption was correct.
the compilation is not happening at all.
this is evident because not all the compilation messages that usually appear in the console are present, in particular the messages logged by the makefile (Makefile.patch to be specific)

this means that its one of:
- incorrect installation of runtime, or anti virus blocking, so make cannot run make correctly
- incorrect installation of Axoloti, or anti virus blocking , so the firmware makefile cannot be accessed (seems unlikely , as this would still create a make error)
- the firmware directory specific in the Axoloti.prefs been changed to something invalid, or has become corrupted. (again unlikely, surely a make error would occur)
- something blocking command tools running (anti virus?), possible but never seen before

anyway, given Teds lack of response/appreciation of my efforts, I guess he wont use this,
but hopefully if other stumble on something similar it might give further insights, if not an immediate solution.I can't give the solution , as in this particular case, Ive not been given enough information to get to the next step.