I have downloaded Latest version of Eclipse, ARM build tools. But my ARM vendor details are not present in CMSIS pack. I am working on Cortex M4, the code is compiled successfully. The linker file is provided by vendor.
The issue I am facing are:
1) The DEVICE field in Project/Properties/C C++ Build/Settings is empty.
- What need to be done to get the device details.
- Only Vendor can fill up this part or programmer can do it
2) Which debugging part should I use?
- GDB Hardware debugging
- GDB open ocd debugging
- GDB J-Link debugging
Code is compiled successfully but I can't program/debug my board.
Majority of the tutorials are based on STM32.
But as my ARM Vendor doesn't have CMSIS PACK' in this case what needs to done?
Related
I followed a blog titled Creating an Electron Application for the Raspberry Pi, regarding starting an Electron app in Raspberry Pi using the Buster OS and got it to compile.
But when it came to building the application, using the electron-builder, I keep getting the error of cannot execute... after running the command electron-builder --dir --armv7l --linux deb and can't figure what the issue is. I've attached the error
Sorry to be 6 months late to the party, but I also just tried to create an Electron app to run on the Raspberry Pi.
It turns out that while Electron runs fine on Arm processors, there are a bunch of problems with building an Electron app via electron-builder on an Arm processor.
The error that you are seeing is just the opening of the rabbit-hole.
Most of the issues appear to be due to electron-builder having apparently been implemented on an x86 machine, with no real care having been taken to make sure that it works on any other architecture - x86 is just pretty-much assumed.
So, for me, the answer was to build the Arm target on an x86 Linux machine, using exactly the same command-line that you used.
So far, I have found that I can build for OS X and Windows on OS X, for Linux x86, Linux Arm, OS X, and Windows on Linux x86. I don't have Windows machine, so I'm not sure what actually works there.
Code signing is yet another rabbit hole....
I start generate code in STM32cubeMX, and i got this message "The Firmware Package(STM32Cube FW_F4 V1.11.0)or one of its dependencies requiredby the Project is not available in your STM32CubeMX Repository". Can enyone tell me how to throw in?
This message indicates that the necessary firmware (for STM32F4 family) not installed. Under GNU/Linux with the newest CubeMX a possibility appears with this message enables install the appropriate firmware. If it is not your case first upgrade your CubeMX and after you need install the additional software (in your case STM32CubeF4) for your microcontroller. You can install it form the CubeMX Help/Install New Libraries.
You can read more detailed information from the STM32CubeMX homepage and under the STM32CubeF4 link on the page.
I was trying to play with several tiny operating systems in an emulator but got stuck with Contiki in QEMU. Ideally the compiled executable should be run as a kernel in QEMU. For all OS's I was playing with I used this simple command to run executables in QEMU:
qemu-system-platform -nographic -kernel compiled_executable
In the case of Contiki, QEMU freezes regardless of any target platform the executables are compiled for, even for target platform "native", which according to the documentation, is built with "x86 gcc".
I also tried ARM-based platforms with the same freezing issues. If I specify a correct CPU model (e.g. cortex-m3 for cc2538dk), I received a segmentation fault instead.
I am wondering if I was missing any steps to cause the QEMU to freeze. Does it mean that the compiled executable cannot be treated as kernels (yet), unless I provide some QEMU-specific codes to initialize QEMU as a "board" for Contiki?
The native platform is used to build a "natively" (i.e. on Linux or other OS) executable image of Contiki - an userland app, rather than an OS kernel.
I am running Nsight Eclipse edition on my MacBook PRO (OS X 10.8.2, mountain lion, CUDA 5.0, GT650M)
and I am getting a strange error each time I try to start the debugger in Nsight.
In the console I get: Coalescing of the CUDA commands output is off. and an error screen.
Here is a screenshot of the error:
I went through the Nsight documentation and found this line:
GPUs used to run X11 (on Linux) or Aqua (on Mac) cannot be used to
debug CUDA applications in Nsight Eclipse Edition. Consult cuda-gdb
documentation for details.
Does this mean I can't run the debugger form Nsight, but just from terminal?
The message you are seein means the debugger was not properly setup on your system (e.g. it will not even work from the console). Please follow the steps outlined in "Setting Up the Debugger Environment" of the cuda-gdb manual
You will need a two-GPU system to debug a CUDA code using visual debugger. Unfortunately, no Mac laptops qualify even though they have Intel graphics. The issue been the OS can start using NVIDIA GPU at any moment and may hang if the device is suspended on a breakpoint.
Your cuda-gdb is not properly code signed, which is required by the Darwin kernel to debug applications.
Follow this guideline to create a System code sign certificate
http://www.noktec.be/archives/1251
Then, code sign the following binaries (assuming the certificate you created is cuda_gdb)
sudo codesign -s cuda_gdb /usr/local/cuda/bin/cuda-gdb
sudo codesign -s cuda_gdb /usr/local/cuda/bin/cuda-binary-gdb
Also, in order to launch the application, you also need to make sure the DYLD_LIBRARY_PATH contains the cuda runtime library path
DYLB_LIBRARY_PATH /usr/local/cuda/lib
I have set up the board according to the RX cpu example in eclipse, and everything seemed to be working fine till I wanted to get the example running on the board. When I click the option to hardware debug, I get an error saying "Error launching GDB server. Check installation".
Am I to re install eclipse, or the GCC toolchain for the RX cpu, or anything else?
I don't know anything about your specifics (that is Renesas or the RX62N). I do use eclipse for embedded work. Typically on a new platform I would make sure I can build and download a release version first. Once you have that working then see if you can get a Debug build and the debugger running. On the platforms I am used to, you have to put in hooks (typically just a single call) to enable the debugger. For exmple on the NetBurner the debugger can run over the serial port or Ethernet so the call has to specify which version you want to use. I know other platforms use JTAG debuggers etc, Typically a dev kit for the board comes with a manual that details how to get the debugger working. I doubt that you need to reinstall anything you just need to get the configuration set up correctly.