I switched from Mac to Windows and now I'm having problems with connecting to some of my microcontroller boards. (Infineon Aurix Tricore TC275 and Digilent Arty S7).
When I connect the board, it it shown in the device manager, but when I try to flash the project within Aurix Development Studio, it says "DASWRAPPER::No ECF hardware found".
DAS is installed, it also did not discover the board.
I got the same problem with my digilent arty s7 and xilinx vivado suite.
With STM32 Boards and the STM32CubeIDE the download process works.
Is there anybody that got the same issues as me?
I tried Updating Windows, reinstalling DAS and Aurix Development Studio, firewall settings ...
Related
I am a student and have been instructed by the college to use MCU 8051 IDE with SDCC for learning microcontroller programming. I installed this software successfully on many HP devices in college but when I am trying to use it on my home Dell Inspiron 15 3000 laptop following happens:
Starting compiler ...
cd "E:\\Embedded Systems Practical"
sdcc -mmcs51 --iram-size 256 --xram-size 0 --code-size 8192 --nooverlay --noinduction --verbose --debug -V --std-sdcc89 --model-small "prac4.c"
The IDE gets stuck here. Even after aborting the IDE freezes and needs to be restarted. I tried multiple fresh installs on my PC but nothing works.
I brought a pre-compiled version from the college PC to verify that the error is with SDCC and the simulation works perfectly fine.
Can someone help me how to resolve the unknown error?
I bought recently a ST Nucleo F103RB, but I have a problem to download my code on the board.
I'm using Keil µVision for the developement.
Here a screenshot of the configuration for the debug :
Configuration of debug's board on Keil µVision
But if I download or try to go to the settings of the debug Keil stop working and close.
Can anyone help me to solve my problem. ?
I'm just trying to put my code on the Nucleo board.
So I contact the ARM's support and this is their answer about my problem :
Which MDK version do you use? I assume that you use version 5.38, which was released almost two weeks ago. If not, please let me know.
This week we found an issue with the new ST-Link driver, which is included in MDK 5.38. We have seen this with only two customers, and one of my colleagues can duplicate it. We are currently in discussion with ST to find the real reason for this issue.
Because of this and another (even more important) issue, we have withdrawn MDK version 5.38. Currently, you can download MDK 5.37 from our webserver again. See https://www.keil.com/demo/eval/arm.htm
With MDK 5.37 this issue should not exist. Please try and let me know.
We will soon release an MDK version 5.38a. Please don't install this version because it will contain the same ST-Link drivers as the version 5.38.
I was using MDK 5.38 so I've uninstalled MDK 5.38 and Keil µVision, and after reintall Keil µVision and the MDK 5.37. And I can now use the debug ST-Link of the nucleo F103RB.
I am working on a project in VS Code with an nRF52dk and the nRF52805 BLE soc. I changed from segger studios to VS Code but now I get this error: BOARD is not being defined on the CMake command-line in the environment or by the app
Under the nRF connect app and Application I did configure my board nrf52dk_nrf52805 and my device is connected too.
I don't have any experience with CMake files. is there something I might need to change in there or rebuild? I already tried deleting the build folders and doing a pristine build
I keep getting this error with ICD 3 when attempting self test:
Could not connect to the selected hardware tool. Please make sure the tool is not being used by another project in MPLAB X.
The device works fine under Ubuntu 12.04. Mplab can see the ICD3 device because it gets the correct serial number. lsusb reports the same values that Mplab reports as well. I tried running Mplab as root and that made no difference - this is not a permissions problem.
I tried this solution: https://www.microchip.com/forums/m1051283.aspx but it did not work. I also tried to close all projects so I had in the projects bar, and got the same error.
I tried the udevadm as suggested by this comment: https://www.microchip.com/forums/m1083236.aspx an it shows Mplab is trying to talk to the ICD 3:
$ udevadm monitor --property
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[3219.382129] bind /devices/pci0000:00/0000:00:16.2/usb3/3-1/3-1:1.0 (usb)
ACTION=bind
DEVPATH=/devices/pci0000:00/0000:00:16.2/usb3/3-1/3-1:1.0
DEVTYPE=usb_interface
DRIVER=usbfs
INTERFACE=255/0/0
MODALIAS=usb:v04D8p9009d0100dcFFdsc00dp00icFFisc00ip00in00
PRODUCT=4d8/9009/100
SEQNUM=3378
SUBSYSTEM=usb
TYPE=255/0/0
UDEV [3219.387110] bind /devices/pci0000:00/0000:00:16.2/usb3/3-1/3-1:1.0 (usb)
ACTION=bind
DEVPATH=/devices/pci0000:00/0000:00:16.2/usb3/3-1/3-1:1.0
DEVTYPE=usb_interface
DRIVER=usbfs
ID_USB_CLASS_FROM_DATABASE=Vendor Specific Class
ID_VENDOR_FROM_DATABASE=Microchip Technology, Inc.
INTERFACE=255/0/0
MODALIAS=usb:v04D8p9009d0100dcFFdsc00dp00icFFisc00ip00in00
PRODUCT=4d8/9009/100
SEQNUM=3378
SUBSYSTEM=usb
TYPE=255/0/0
USEC_INITIALIZED=3219386787
A few seconds later it unbinds. So far I'm just hearing crickets on the Microchip forum. Anyone else tried using ICD 3 under Ubuntu 18?
Mike
After much head beating, I found that there were a lot of .jar files in the microchip mplab directory. But Java was not installed on my version of Ubuntu. After installing openjdk (and placing the correct device for loop back) I got MPLAB to talk to the ICD 3.
I am really surprised this was not obvious. If you have any MPLAB problems under Ubuntu 18.04, check if java is installed! (sudo apt install default-jre)
I recently downloaded the v3 of the FourQlib [1], build the FourQlib and wanted to test if everything went well.
First of all, my system:
Windows 10 (host) with MinGW, ARM Toolchain, MSYS, ...
Ubuntu 16.04 LTS (Guest) (gcc, arm toolchain, ...)
VirtualBox
STM32F429ZI-Disco
The source [1] includes the directory "FourQ_ARM", when compiling you have to start the "monitor.sh" [2] file in a terminal. Since they (Longa et al.) link to "ttyUSB0" I'll checked, if there is any device registered in Ubuntu. Since my µC ist registered as "stlinkv2_2 I changed this symbolic link "/dev/ttyUSB0 -> /dev/stlinkv2_2".
If I run the monitor.sh, the beginning will turn me in an error:
stty -F /dev/stlinkv2_2
leads to the error "Vorgang nicht zulässig" which means something like "Operation not allowed"
Could someone explain me, why I get this error and how to get this shell-script work?
[1] https://github.com/Microsoft/FourQlib
[2] https://github.com/Microsoft/FourQlib/blob/master/FourQ_ARM/tests_Cortex-M4/monitor.sh
The solution is: Using extra hardware with an old driver. Using TTL to USB-converter.
If someone needs to use the FourQlib on a STM32F407, use their USART and monitoring tools. On different processors you need to choose different USART pins. Those with a display connected allready use those pins.