自动代码生成笔记|simulink建模基础及c2000 dsp代码自动生成笔记二

75 阅读 0 评论 50 点赞

我是靠谱客的博主眯眯眼心情，最近开发中收集的这篇文章主要介绍自动代码生成笔记|simulink建模基础及c2000 dsp代码自动生成笔记二，觉得挺不错的，现在分享给大家，希望可以做个参考。

概述

simulink建模基础及c2000 dsp代码自动生成笔记二

书的第2章讲的是闰年判断，差不多在90/475才开始讲搭建模型并建立 91/475 p82讲的是不同solver的区别，ode45不是哟关于刚性系统，但啥是刚性系统呢？而且说ode45是大多数问题首选算法。。。。ode23适用于轻度刚性的系统/

流水灯模型，，p156,166/475,但为啥是stateflow建模呢。。stateflow貌似是状态图建模？///不对，stateflow的流水灯模型貌似只是在示波器上的，不算我所要的模型。。

p269,直接把Arduino的LCD1602显示屏代码弄到Simulink里了

直接看p277,也就是///但从p284开始讲的都是电机用的28027,不是我要的28335啊

414/475 p404显示了点亮黄灯和红灯的，，但是这就有launchpad tms320f2802x啊，太好了吧。。。但p401 410/475还是用的stateflow来弄的啊。。。C2000 launchpad XL

在这里插入图片描述

C:ProgramDataMATLABSupportPackagesR2018atoolboxtargetsupportpackagestic200
0CCS_Config，用 CCS 打开 f28335.ccxml 文件，并修改为自己仿真器型号保存。
估计还得在CCS修改；；这一步就直接在controlsuite里随便找一个例程弄吧

这里就看不懂了啊

The following error occurred during deployment to your hardware board:
Debug Server Scripting (DSS) error:
*** User inputs:
Target Configuration: C:PROGRA~3MATLABSUPPOR~1R2019btoolboxtargetSUPPOR~1tic2000CCS_CO~1F28335~1.CCX
Program Name: C:UsersthinkDesktopLED___~1.OUT
Board Name: *
CPU Name: unspecified (connect to first CPU)
*** Starting debug session...
*** Debug Session Name: Texas Instruments XDS100v1 USB Emulator_0/C28xx
*** Board Name: Texas Instruments XDS100v1 USB Emulator_0
*** CPU Name: C28xx
*** Connecting to target...
SEVERE: C28xx: Error connecting to the target: (Error -151 @ 0x0) One of the FTDI driver functions used during the connect returned bad status or an error. The cause may be one or more of: no XDS100 is plugged in, invalid XDS100 serial number, blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable. Use the xds100serial command-line utility in the 'common/uscif' folder to verify the XDS100 can be located. (Emulation package 7.0.100.0)
SEVERE: emulation failure occurred
SEVERE: Error connecting to the target: emulation failure occurred
SEVERE: Cannot perform operation, target is not connected.
SEVERE: Error reseting target: Cannot perform operation, target is not connected.
org.mozilla.javascript.WrappedException: Wrapped com.ti.ccstudio.scripting.environment.ScriptingException: Error reseting target: Cannot perform operation, target is not connected. (C:PROGRA~3MATLABSUPPOR~1R2019btoolboxtargetSUPPOR~1tic2000/CCS_CO~1/RUNPRO~2.JS#93)
at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1693)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:160)
at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:204)
at org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:119)
at org.mozilla.javascript.gen.c1._c0(C:PROGRA~3MATLABSUPPOR~1R2019btoolboxtargetSUPPOR~1tic2000/CCS_CO~1/RUNPRO~2.JS:93)
at org.mozilla.javascript.gen.c1.call(C:PROGRA~3MATLABSUPPOR~1R2019btoolboxtargetSUPPOR~1tic2000/CCS_CO~1/RUNPRO~2.JS)
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:340)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2758)
at org.mozilla.javascript.gen.c1.call(C:PROGRA~3MATLABSUPPOR~1R2019btoolboxtargetSUPPOR~1tic2000/CCS_CO~1/RUNPRO~2.JS)
at org.mozilla.javascript.gen.c1.exec(C:PROGRA~3MATLABSUPPOR~1R2019btoolboxtargetSUPPOR~1tic2000/CCS_CO~1/RUNPRO~2.JS)
at org.mozilla.javascript.tools.shell.Main.evaluateScript(Main.java:503)
at org.mozilla.javascript.tools.shell.Main.processFileSecure(Main.java:425)
at org.mozilla.javascript.tools.shell.Main.processFile(Main.java:391)
at org.mozilla.javascript.tools.shell.Main.processSource(Main.java:382)
at org.mozilla.javascript.tools.shell.Main.processFiles(Main.java:179)
at org.mozilla.javascript.tools.shell.Main$IProxy.run(Main.java:100)
at org.mozilla.javascript.Context.call(Context.java:528)
at org.mozilla.javascript.ContextFactory.call(ContextFactory.java:450)
at org.mozilla.javascript.tools.shell.Main.exec(Main.java:162)
at com.ti.ccstudio.apps.internal.scripting.RunScript$1.run(RunScript.java:89)
Caused by: com.ti.ccstudio.scripting.environment.ScriptingException: Error reseting target: Cannot perform operation, target is not connected.
at com.ti.debug.engine.scripting.Target.reset(Target.java:622)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:145)
... 18 more

*** Starting debug session...
*** Debug Session Name: Texas Instruments XDS100v1 USB Emulator_0/C28xx
*** Board Name: Texas Instruments XDS100v1 USB Emulator_0
*** CPU Name: C28xx
*** Connecting to target...
SEVERE: C28xx: Error connecting to the target: (Error -151 @ 0x0) One of the FTDI driver functions used during the connect returned bad status or an error. The cause may be one or more of: no XDS100 is plugged in, invalid XDS100 serial number, blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable. Use the xds100serial command-line utility in the 'common/uscif' folder to verify the XDS100 can be located. (Emulation package 7.0.100.0)