I am using IAR Embedded Workbench IDE to develop an embedded solution for the Renesas RL78/G13. I am able to compile and run the project in debug mode. Now I would like to burn the program to flash in release mode. Can someone tell me how to do this?
Maybe the answer is a little bit late, but another option straight from IAR is to go to Make [F7 key] the project and the go to Menu Project -> Download -> Download active application.
Be carefull that the Reset line of the microncontroller is free so nothing sets it to OV, which will stop the microcontroller from running
IAR version for RL78 1.40.1
Certainly, you can use the Renesas Flash Programmer for downloading the hex file into the microcontroller. The Renesas flash Programmer install package, you can get from the website from supplier.
Related
we want to write a VSCode debug extension for remote debugging PL/I source code on the mainframe.
We use IBM's z/OS Explorer, but we don't want to start this heavy Eclipse bundle for debugging (everything else is done in this VSCode extension).
We "wiresharked" the communication with IBM's z/OS Explorer, so it would be no problem to send and receive tcp packages according what the debugger (running on the mainframe) needs.
But we don't understand how debugging could work in a VSCode extension.
Now it is working as following:
Write a dataset on the mainframe
Submit a job with the program you want to debug
When the z/OS Explorer is started, debugging is starting.
What is needed to
1.) init vscode debugging functions
2.) send start command via tcp
3.) receive and display the information via tcp
4.) start, stop and breakpoint functionalities
Any examples etc. would be helpful, thank you!
The only way you will be able to do this is with WAZi developer. You MUST have the IBM Debugger installed on the z/OS, and that is a licensable program. Yes, you could write a debugger on your own, but the cost/benefit grossly exceeds the price of IBM's licenses.
Here's the details on debugging with WAZi
https://www.ibm.com/docs/en/developer-for-zos/15.0.0?topic=code-debugging-applications
I have a project for Xilinx Zynq (Cortex A9). I want to be able to step-by-step debug the application in KDevelop. I know that xilinx has XSCT but I don't understand how can I get KDevelop to work in step-by-step code debugging mode for my processor?
I can advise you to learn how to do this from the terminal first and deal with the work of gdb-server. And also get a suitable make/cmake file.
Has anyone managed to connect a MicroBlaze instantiated in a Xilinx FPGA to anything other than the Xilinx tools (SDK or Vitis) for download and debugging?
I'm targeting a VCU29 and have licenses from Xilinx for Vivado etc; I have already extracted the libraries, source and GCC tools and constructed a makefile that will build my applications.
I'm resigned to using Vitis to load the initial bitfile but would really like to download the code and operate the JTAG from a tool that better matches SW development flow - Eclipse with OpenOCD? Perhaps over the built-in USB->Serial->JTAG interface? I believe I'd be content with just the interface offered through GDB.
I'd really like to know if anyone has tried this with either success or failure or maybe has one of those "Why don't you just..." lateral thinking ways of solving the problem.
Yes, my team does not use Vitis or SDK to build, deploy, or connect to MicroBlazes.
If you generate your BSP and a linker script with Vitis, you can then build using mb-gcc and link with mb-ld directly. To get these into your PATH, just source the settings script that Xilinx provides with their tools in <Vitis_root>/settings64.sh.
As for loading and debugging - if you source the same script, then you will have access to xsdb. Once you have XVC running (i.e. connecting to your board with Vivado HW manager), then you can launch xsdb and inside run connect or connect -xvc-url <host>::<port> if you are running on a different host. While connected, you can run targets to identify your MicroBlaze, and then select the MicroBlaze with target 5.
While you have the MicroBlaze selected, you can load <path to elf> and run a number of debugging commands. Just run help while connected to see your options.
I'm a newbie at maya c++ API making.
I made a byte of maya c++ api to my computer with Visual studio.
My .mll filetype worked well on my computer with devkit using mel(loadPlugin ~~).
But when the code is run on other computer, it doesn't work. I get the error:
//Error: line 2: Unable to dynamically load : C:/Users/user/Documents/maya/2018/scripts/outOfcameraAPI.mll
Someone told me to bring the dll file to other computer, but I can't understand yet.
I'm sure this is very easy to fix for someone but it is making me crazy. If somebody who reads this knows how to fix, please let me know. Thanks for reading.
These types of error have two reasons in most cases: 1. Build in debug mode, not release mode. Debug mode will rely on debug libraries which are only available if the development environment is installed on the computer, e.g. VisualStudio. 2. The plugin needs an additional library, e.g. a alembic reader will need the alembic library.
I recently got a nrf51 bluetooth module and I am trying to debug it with Eclipse Mars. I installed the required toolchain as well as OpenOCD (I am using STLink v2 to debug the board).
While running openOCD and arm-none-eabi-gdb in console, everything works fine. The OpenOCD server starts up and I am able to connect with the gdb tool.
However, when trying to start a debug session with Eclipse, it throws the error "Exception occurred during launch. Reason: Program file does not exist". The build process finishes normally. It's the first time I used Eclipse for C/C++ development and the first time after years I used Eclipse at all so I don't even have an idea what could be wrong.
I tried messing around with the project settings without luck. Can anyone give me a hint?
I should mention, I used an already existing Makefile since I tried compiling one of the nordic SDK examples. I Changed it so the resulting files are ready for debugging.
In past I've used Segger's Jlink programmer and the JlinkExe (A pre-built binary) for Linux platform to program Nordic Bluetooth module such as NRF51 and it worked seamlessly. There are some very good documentation on using GNU toolchain with NRF51 series SOC and in case you get your hands on Segger's Jlink, I would recommend you to use that for programming. Meanwhile, this thread in the Nordic's developer zone seem to be very much similar to your problem. Maybe you'll be find some clues there.