Tag Archives: bug

The firmware of the connected j-link does not support the following memory access)

directory
1. Encountered
2. Resolution


recently my tutor gave me a project related to UWB, using stm32 chip. When I downloaded The program with Keil5, The J-Link driver detected all that could be done, but ran out of The Firmware of The connected J-link does not support The following memory access. Later consult the elder brother also is to encounter this kind of problem for the first time, then turn to omnipotent Internet, discover also have similar problem.

(you can see that there is already a j-link driver in the device manager)

(Keil5’s magic wand can also be detected, note the DLL)


(download program, two error, mentality explosion)
2. When The firmware of The connected j-link does not support The following memory access, I received a second error (Flash download faied-taget DLL has been cancelled). Therefore, I tried to find out The reason from The DLL.
also refers to a lot of big guys’ solutions, basically is to replace the jlinkarm. DLL under the installation path of Keil5 with jlinkarm. DLL under the j-link installation path. So I tried it myself, and it worked.


(after modifying the DLL, it was ok)

later when using uwb serial port debugging, it was very happy to see that the data could be successfully sent!

Failed to notify ProjectEvaluationListener.afterEvaluate(), but primary configuration failure takes

Failed to notify ProjectEvaluationListener.afterEvaluate(), but primary configuration failure takes precedence.

today with Qt development of android application present such a wrong
Failed to notify ProjectEvaluationListener. AfterEvaluate (), but primary configuration failure takes precedence.
Java lang. IllegalArgumentException: android.buildToolsVersion is missing! 

at com.android.build.gradle.internal.SdkHandler.initTarget(SdkHandler.java:84)
at com.android.build.gradle.BasePlugin.ensureTargetSetup(BasePlugin.groovy:467)
at com.android.build.gradle.BasePlugin.access$0(BasePlugin.groovy)
at com.android.build.gradle.BasePlugin$_createTasks_closure9.doCall(BasePlugin.groovy:372)
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.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:324)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:278)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1016)
at groovy.lang.Closure.call(Closure.java:423)
at org.gradle.listener.ClosureBackedMethodInvocationDispatch.dispatch(ClosureBackedMethodInvocationDispatch.java:40)
at org.gradle.listener.ClosureBackedMethodInvocationDispatch.dispatch(ClosureBackedMethodInvocationDispatch.java:25)
at org.gradle.listener.BroadcastDispatch.dispatch(BroadcastDispatch.java:83)
at org.gradle.listener.BroadcastDispatch.dispatch(BroadcastDispatch.java:31)
at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy12.afterEvaluate(Unknown Source)
at org.gradle.configuration.project.LifecycleProjectEvaluator.notifyAfterEvaluate(LifecycleProjectEvaluator.java:79)
at org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:65)
at org.gradle.api.internal.project.AbstractProject.evaluate(AbstractProject.java:504)
at org.gradle.api.internal.project.AbstractProject.evaluate(AbstractProject.java:83)
at org.gradle.execution.TaskPathProjectEvaluator.configureHierarchy(TaskPathProjectEvaluator.java:42)
at org.gradle.configuration.DefaultBuildConfigurer.configure(DefaultBuildConfigurer.java:35)
at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:129)
at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:106)
at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:86)
at org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:80)
at org.gradle.launcher.cli.ExecuteBuildAction.run(ExecuteBuildAction.java:33)
at org.gradle.launcher.cli.ExecuteBuildAction.run(ExecuteBuildAction.java:24)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:36)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:26)
at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:51)
at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:171)
at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:237)
at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:210)
at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:35)
at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:206)
at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:169)
at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
at org.gradle.launcher.Main.doAction(Main.java:33)
at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
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.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:54)
at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:35)
at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
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.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:33)
at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:130)
at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:48)

FAILURE:构建失败，出现异常

  • Where:
    构建文件’ F:\Qt\Qt5.5.1\Examples\Qt-5.5\widgets\widgets\ Build – analogc锁android_for_armeabi_v7a_gcc_4_8_qt_5_5_1 – debug \android-build\ Build。什么地方出了问题:
    在评估根项目’ android-build ‘时出现了一个问题。

    无效的修订:24.0.0-preview

    运行-stacktrace选项以获取堆栈跟踪。
    运行-stacktrace选项以获取堆栈跟踪。使用-info或-debug选项运行以获得更多日志输出。
    构建失败

    总时间:6.283秒
    构建android包失败!
    -有关更多信息，请使用- verbose运行此命令。
    22:46:03:进程“F: \ Qt \ Qt5.5.1 \ 5.5 \ android_armv7 \ bin \ androiddeployqt。exe”退出,退出代14码。
    错误构建/部署项目analogclock (kit: Android for armeabi-v7a (GCC 4.8, Qt 5.5.1))
    执行步骤” Build Android APK ”

    • Failed to execute goal on project XXXX-api: Could not resolve dependencies for pro

    Failed to execute goal on project XXXX-api: Could not resolve dependencies for pro***************************************************

    today met a maven packaging error, an error message that Could not resolve dependencies for pro * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

    the reason is that the package name path was modified during the migration of the module. Try all kinds of cleanup and finally mention cleanup top level pom. XML

    in a know reply

    execute maven clean, then execute maven install and then repackage the specified module.

    if the package is still wrong, please carefully check the reference package path and the real module package path are consistent;

    Error: java.lang.IllegalArgumentExcept ：Property ‘sqlSessionFactory‘ or ‘sqlSessionTemplate‘ are required

    conclusion: there was an error when the blogger was manually adding jar packages to the maven repository. The error was resolved by removing the dependent folder.

    today to upload in ali cloud vod video, there is a jar package ali did not open source, need to manually introduced, when I was in the jar package is added to the maven, jar package name wrong, lead to the name of the folder and jar package name do not match, and then in the evening, there is a module was first started, to start the other modules, so the error, and then stop and then restart the start up of module, also not line, so I think it’s not code, after a search, see some people say that the JDK jar package might be the problem, I also touched the JDK and thought I had touched maven. Sure enough, once deleted, it was normal 

    
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'eduChapterMapper' defined in file [F:\wmjava\guli_school\target\classes\com\wm\eduService\mapper\EduChapterMapper.class]: Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Property 'sqlSessionFactory' or 'sqlSessionTemplate' are required
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1794)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:594)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:516)
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:324)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:322)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
	at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:276)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1307)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1227)
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:640)
	... 33 common frames omitted
Caused by: java.lang.IllegalArgumentException: Property 'sqlSessionFactory' or 'sqlSessionTemplate' are required
	at org.springframework.util.Assert.notNull(Assert.java:201)
	at org.mybatis.spring.support.SqlSessionDaoSupport.checkDaoConfig(SqlSessionDaoSupport.java:122)
	at org.mybatis.spring.mapper.MapperFactoryBean.checkDaoConfig(MapperFactoryBean.java:73)
	at org.springframework.dao.support.DaoSupport.afterPropertiesSet(DaoSupport.java:44)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1853)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1790)
	... 43 common frames omitted

    Tensorflow error: module ‘tensorflow’ has no attribute ‘xxx’

    ____tz_zs

    good tensorflow appears suddenly: can import the tensorflow package, but using any module under tensorflow will report a “nonexistence” error.

    such as: using tf.variable to create a Variable also reports AttributeError: module ‘tensorflow’ has no attribute ‘Variable ‘.

    because tensorflow becomes a module without any content (the reason why tensorflow becomes empty is unknown)

    solution: uninstall tensorflow (based on the PIP uninstall tensorflow or PIP uninstall tensorflow-gpu you installed) and reinstall it (based on the PIP install tensorflow or PIP install tensorflow-gpu you installed)

    ps: according to some discussion information found by Google, when tensorflow was installed under Windows, it also appeared that the tensorflow was empty, possibly because of the permission problem.

    add:

    Windows TensorFlow installation: http://blog.csdn.net/tz_zs/article/details/74779953

    making similar discussion: https://github.com/tensorflow/tensorflow/issues/7285

    Solve the problem of unable to locate package python3.6 when upgrading from python3.5 to python3.6 in ubantu16.04

    error as follows: 

    Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package python3.6
E: Couldn't find any package by glob 'python3.6'
E: Couldn't find any package by regex 'python3.6'

    The ppa used by

    is the old version: 

    sudo add-apt-repository ppa:jonathonf/python-3.6

    needs to update ppa: 

    sudo add-apt-repository ppa:deadsnakes/ppa

    and then system update: 

    sudo apt-get update

    Finally, python3.6

    is installed

    sudo apt-get install python3.6

    How to Fix Sklearn ValueError: This solver needs samples of at least 2 classes in the data, but the data

    error cause

    train_sizes, train_scores, test_scores = learning_curve(estimator, X, y, cv=cv, n_jobs=n_jobs, train_sizes=train_sizes, verbose=verbose) #请注意X,y

    solution: </h3 b>

    from sklearn.utils import shuffle
 
X_shuffle, y_shuffle = shuffle(X, y)

    error: </h3 b>

    this is because before shuffling, if a CV is done it is possible to have only one class in the dataset. After the shuffle, the data is shuffled, reducing the possibility of the above situation (that is, if the data set is extremely unbalanced, the above bug may still emerge after the shuffle)

    ImportError: dlopen: cannot load any more object with static TLS

    The

    problem occurs when using import torch.

    is a very weird problem that has been discussed a lot on github, but there is no fundamental solution, and it is not just a problem with torch, but also with tensorflow.

    solution:

    1, switch the order of the call package, for example: 

    import cv2
import torch # 报错
# different order
import torch
import cv2   # ok

    2. However, the above method does not work for me:

    reference: https://github.com/pytorch/pytorch/issues/2083

    using the old brother’s method, which still makes no sense, but it works for me

    How to solve the problem that the project module turns grey in Maven

    wrong project, built to remove reconstruction, suddenly have been project identification, always prompt project can’t find, then see the maven inside of bar on the right, according to project is gray, the diagram below:

    for this reason, find relevant solution and steps are as follows:
    1 file – setting

    2 maven – ignored files, the following figure

    save after 3 o ‘clock, gray disappears inside maven: