I was going through the example of FRDM-KL25Z library in MATLAB Simulink and having some problems when deploying it to the board.
1) Most of the H files are missing in the directory during (compiling?) and was FIXED by downloading individually from website.
2) After the H files are fixed, MATLAB prompt me another error stating FILE_DIR/TOOLCHAIN_GCC_ARM/libmbed.a' needed by ".../freedom_board_servo.elf'
I'm quite new to this field so was hoping someone can guide me through these errors as I have been stuck here doing nothing for few days fixing errors and errors.
Thanks.libmbed.a ERROR
Hi all the problem is fixed by changing the directory of the file.
During installation MATLAB have named the directory wrongly "8e73be2a2ac1" was supposed to be named to "mbed-8e73be2a2ac1".
Related
I have a stand alone script, that opens a QGIS project file in order to extract details.
I accidentally moved a file and the script broke. Below is the interesting part.
QgsApplication.setPrefixPath("/usr", True)
project = QgsProject.instance()
qgs = QgsApplication([], False)
qgs.initQgis()
project.read('/home/jdoe/textproj.qgz')
# invalid path, but does not fail or warn in any way
print(project)
# prints: <QgsProject:'/home/jdoe/textproj.qgz'(singleton instance)>
# no indication of any problems with loading file
Question 1 - Why no error?
I think everyone would expect it to fail (throwing an exception). Is there any good reason for it to behave different than failing?
Question 2 - How to properly load a project from a file?
Is there anything in my code that that is is using the library differently that intended, which may partly explain why I got no errors?
Question 3 - How do I make sure it fails?
Of course I could write my own assertion to test if the path does point to a file. But I guess there could be other ways in which reading/loading a project file could fail. So what is the proper way of catching this right away?
I have problems translating Modelica models with Dymola 2020: When I try to translate the models, the following error message appears:
"unknown internal error in Dymola".
The model was translating and simulating a couple of days ago, and the same model still runs on the computer of other colleagues. I didn't change the compiler in between nor the Dymola version. I've also restarted the computer but the problem persists.
Also, other models are still translating, so not all models are affected by this error.
Does anyone have a clue how to debug this error? Thank you very much for all hints!
The most likely explanation would be some weird setting of some flag.
You can see if you have any odd settings of normal flags by:
Dymola 2020: Edit>Options>General>Flags... Check "Non-default"
Dymola 2020x: Tools>Options>General>Flags... Check "Non-default"
(If it is a non-Boolean setting it is a bit messier.)
That is assuming it is really the same model and there is no difference in any model in the path (including working directory).
Frankly speaking, if you get "unknown internal error in Dymola" you should report it to technical support at Dassault Systèmes (through your reseller), and let them debug it.
It is not your job to debug such errors.
Have you tried to delete the content from the working directory (WD)?
Sometimes there are artifacts, which mess up the compilation of a specific model.
You can check where it is, using the
GUI, File -> Working Directory -> Copy Path and paste it in the Explorer
Command line typing cd, which returns the path to the WD
Then make sure that there are no important files in the WD (usually .mo files) and finally delete the full content of the directory.
Note: You should ensure that the WD is a local path (otherwise performance can take a serious hit). Besides that it is usually a good idea to have the WD separated form the directory where models are stored.
I have a password protected zip file with 3 folders PFC, STA and SYS. The zip file when loaded for the first time reads all the text files in the PFC folder and display the data onto the screen. I perform some operations on the screeen which generates new files and they are added into the STA and SYS folders and the same initial zip file is updated.
However, when I try to load the same zip file which now should have the all the initial files and folders along with the newly created files in it, it gives me a Wrong CRC Value error. I dont know what am I doing wrong.
We have tried to reproduce the issue by preparing a sample with your scenario. But, we are facing another issue related to password which we will fix in our upcoming release. The sample can be downloaded from the below link .
Sample link : https://www.syncfusion.com/downloads/support/directtrac/general/ze/Password-1299200154.zip
Kindly modify the sample to reproduce the “CRC value error” issue and update us along with input documents. It will help us to analyze further on this and provide you a solution at earliest.
Note : I work for Syncfusion.
You can send your sample or confidential information in mail to, support#syncfusion.com
Regards,
Mohan.
I am running a code that uses the fitsread function to open my fits movies and analyse them. It was working perfectly fine until about a week ago, when, without me doing anything, it started giving the following error whenever I try to run it:
Error using matlab.io.fits.openFile (line 48)
Unable to open file. File might be corrupt or filename might have unsupported
characters.
Error in fitsread>read_image_hdu (line 412)
fptr = fits.openFile(info.Filename);
Error in fitsread (line 125)
data = read_image_hdu(info,1,raw,pixelRegion);
I have tried manually checking the properties of such files using the fitsinfo function and nothing was wrong with the files themselves. I have also tried to re-set the default MATLAB path, delete them from the working folder and re-download them from a central University server where they were originally stored upon acquisition on a microscope, but it didn't help either. A collaborator has tried running the same code on his machine and it works well. I get this same error on both MATLAB versions R2011b and R2015b. It originally used to work on R2011b with the same files.
Thanks in advance to whoever will be able to help!
I need some help with Stata. I'm not sure if this is the right forum, but hopefully somebody can help me.
The problem occur, when I want to use new commands in stata. I will explain it with an example: command outreg. I assume the problem is the version.
Stata Details:
Version 10.1
Unlimited-user Stata for Windows (network) perpetual license (decompressed in C:\Program Files (x86)\Stata)
I downloaded the command ssc install outreg
I tried the new command with the example given here:
http://www.ats.ucla.edu/stat/stata/faq/outreg.htm
After execution, the following error occur, after outreg using test.doc, nolabel replace
MakeSmat(): 3499 _CColJoin() not found
CalcStats(): - function returned error
<istmt>: - function returned error
Stata.com also provide a solution for the problem:
http://www.stata.com/statalist/archive/2011-07/msg01018.html but a restart of stata doesn't work for my problem.
The necessary library (l_cfrmt described in the stata.com link) is also available:
. mata : mata query
Mata settings
set matastrict off
set matalnum off
set mataoptimize on
set matafavor space may be space or speed
set matacache 400 kilobytes
set matalibs lmatabase;lmataado;lmataopt;l_cfrmt
set matamofirst off
But when I search for the usage of the library l_cfrmt (which is necessary for outreg) there occur the following error-message:
. mata : mata desc using l_cfrmt
c:\ado\plus\l\l_cfrmt.mlib from a more recent version of Stata
It looks, if the version, which I loaded via ssc is not compatible with the Version 10.1 of Stata.
Does somebody have any idea how to solve this problem? I search for a few hours now, but I did't find any possible solution.
Regards,
Michael
First, the code you found on the ucla website for -outreg- is not correct -- John Gallup has since made many changes to the latest version of -outreg-, one of which affects your example. (ignoring your mata issue for a moment) This code should be modified to this in order to make it run:
**install latest outreg
ssc install outreg, replace
use http://www.ats.ucla.edu/stat/stata/notes/hsb1, clear
regress read write
outreg using test.doc, novarlabel replace
the code above works on my machine with an updated version of Stata 12 MP and updated -outreg- version 4.12.
Regarding the mata error: It might be the case that the newest -outreg- just might not work with Stata 10.1 - but I wouldn't give up yet. First, make sure your Stata is fully updated (-update query- and -update all-).
Second, follow the advice of the author of -outreg- in this Statalist thread:
http://www.stata.com/statalist/archive/2011-07/msg01014.html
Finally, if you do have a missing mata component/library, as that thread hints at, and cannot follow this advice to correct it, then consider re-installing Stata and/or contacting Stata tech support.