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
Related
Whenever I try and add any SpriteKit elements to my project, Xcode crashes. The files are created but not added to the project and if adding them manually, it still crashes when trying to open them. After some searching it looks as though previous versions have suffered with the same issue. I had the same issue with 8 beta 6 too.
Is there anything I can do to help with the issue? I can't find anything on the most up to date version so I'm guessing it's either something I'm doing or a problem with my setup.
I've the same issue when I try to maintain 2 Xcode versions in the same system, it is possible but you should install them into separate directories, for example Xcode_731 and Xcode_8 (my actual version is 8A218a GM, I haven't any crash).
This should be unuseful without crashes, but try also to free some memory (quit also simulator app after your crash), in your terminal:
sudo purge
i recently received my Macbook and wanted to start developing iOS apps with it.
I Created a default Master-Detail App using the Templates in Xamarin.Studio and everything worked.
Now today i wanted to actually do something in the app, but didn't change a single line of code, still the app doesn't show up anymore in the simulator as long as i want it to use the 6.1 sdk for ios. if i use any other (6.0 etc) it works fine.
I already tried clearing my Cache in /Users/MYNAME/Library/Xamarin/ but this didn't change anything.
What would you suggest me to do now? can i simply reinstall the 6.1 sdk?if so, how would i do this?
Thanks for your help
I had a similar problem where the environment hang when I was trying to debug in the simulator (just showing the spinning ball). I found out that it only occured if I had my phone connected to the computer. Perhaps not valid in your case, but it might be a lead in your problem solving.
I'm using the latest version of everything. :)
From within Xamarin Studio (or MonoDevelop):
Project -> Your.Application.Name Options
Build -> iOS Build (iPhone Build in MonoDevelop)
SDK version: -> 6.1 (it's probably still on 6.0)
This fixed it for me. Also, it wouldn't hurt to make sure the target build in info.plist is set to 6.1.
Delete this folder:
/Users/[username]/Library/Application Support/iPhone Simulator/6.1
And if your Library folder is hidden:
sudo chflags nohidden ~/Library/
I have experienced this problem several times again and my previous answer doesn't solve it. Ya know what does? Rebooting the computer. Works every time. shrug
You need to fill the Application name, Identifier, Version # in the project setting.
I had the same problem and got it solved that way.
When I compile my mobile app using Xcode and Phonegap, the application on the iPod/iPhone/iPad is the anterior version that I compiled yesterday.
Basically when I run the app in the emulator, all works fine, so I know it's the right files and everything, but when I then build it for the mobile device, it shows the one I did yesterday.
What could be causing this? Is there any settings I should check or something? Like I said I doubt it's related to the files/folder because when emulating it, it works fine.
Thanks!
I had a similar problem long time ago. Try to delete your app on the device and then build it again. I don't know how apple manage apps but I think that the major of your app is keeped on your device (in order to speed up compilation).
I hope it will works !
Did you increase the version number of your built? If you recompile with the same number, you may run into trouble.
i'm developing iPhone apps. Yesterday i updated leopard to snow leopard. Alongside i made the jump from XCode 3.1.4 to 3.2.4
I was always quite happy with XCode - working most of the time under windows, I really appreciate how well the XCode toolchain works together.
however - i'm not happy with 3.2.4 at all. i experience a lot of flaws, mainly with debugging. When an error arises, the debugger often stops at another place than the actual error happened. Sometimes the debugger does not trap into breakpoints at all and i get after some time a Error from Debugger: mi_cmd_stack_list_frames: Not enough frames in stack - whatever that means. And also I get invisible breakpoints which i can't remove anymore.
Does anyone experience similar things with XCode 3.2.4? if so, which is the newest release that works well?
Thanks!
Usually the problem is to do with level of debug symbols or some compiler optimization (which shouldn't be applied in debug builds). Maybe the information here will help.
Also try a complete clean (delete the build folder, remove the app from the device/simulator) & rebuild. Ensure you're working with the Debug configuration.
I've got 2 applications using Core Data with a sqlite persistent store. I've got a data loader routine that I run to populate the CoreData DB from csv files. During development, when my data changes I run the routine from the simulator to generate new databases and copy the new one into the project.
This has been working quite well for XCode 3.2.3 and iOS 4.0. It even works in the XCode 4 Preview 2 and 3. I just installed the final version of XCode 3.2.4 and iOS 4.1. Now my db loader fails. It gives me no message, no warning, no nothing. It just dumps out to the spring board and XCode gives me the "Debugging Terminated" message. It will fail at different times during the load so I'm pretty sure it's not a data issue. I'm not doing any threading. I assume the issue has to do with either Core Data or sqlite, since that's when the crash occurs, but with no info reported I can't tell for sure.
I uninstalled everything. Xcode 3.2.4, Xcode 4 preview (assuming it was an issue caused by XCode 4) and reinstalled XCode 3.2.3/iOS 4.0. Things returned to normal. After getting some work done I attempted to upgrade to 3.2.4/iOS 4.1 again. I uninstalled 3.2.3/iOS 4.0, rebooted. Installed 3.2.4/iOS 4.1, rebooted and tried again. No luck. Same hard crash. Same lack of messaging as to the cause.
I have determined that this only happens with the Simulator with XCode 3.2.4, the device is fine as is XCode 4 and 3.2.3. I've tried playing with the target OS selection (3.0,3.1,4.0,4.1). I've tired adjusting the Compiler from GCC 4.0, GCC 4.2,LLVM GCC 4.2, LLVM 1.5. I've tried setting the Base SDK to iOS Simulator 4.1. Interestingly enough it will work in the iPad simulator when using the 3.2 SDK. So I've at least go that as a work around.
I guess there is one of 3 issues:
An issue with my code that has been uncovered by 3.2.4.
Bug in 3.2.4.
A configuration issue that I've missed.
If anybody has any troubleshooting ideas or answers I'd love to hear them. I've been doing iOS full time since V 2.1 and I am seriously stumped.
Thanks in advance,
I figured out my issue. It looks like the CoreData/Sqlite connection was a total red herring. Following a tip I read on SO, I used OSX's Console application and got a critical message "Failed to launch in time" that was not being displayed in XCode's debugger console.
It looks like the process was being killed due to what is essentially a timeout error. The iPhone will kill an application that takes too long to complete "didFinishLaunching." That's where I was kicking the data load routine off from. The new version of XCode must have adjusted it's timeout values.
So my takeaway is give OSX's console a shot if XCode isn't telling you everything and watch out for those red herrings.
When I upgraded I ran into troubles in the simulator when saving the managedObjectContext. I finally deleted my sqlite CoreData store file and have not run into similar problems. Try deleting your data file (well save a copy of it before deleting to see what is different).