Search the Community

Showing results for tags 'debug'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Scopes & Instruments
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 6 results

  1. Hello, since now, i have only experience in debugging bare metal apps. I will write a linux tcp/ip-server, therefor i must be able to debug my c-code. I have tried the known bare-metal-workflow and instead of Chose "bare-metal" i Chose Linux as operating System. When i start the debugging process then i got the following error: What is a "Linux Agent" and why is it disconnected? Thank you...
  2. I have an Arduino sketch that runs beautifully on a Wi-FIRE Rev C board using the chipkit wifire(Rev C) board that was installed as part of the Digilent core linked on this page https://reference.digilentinc.com/learn/software/tutorials/digilent-core-install/start NOT the chipKIT core identified on chipkit.net page. I created an ELF file of the sketch by building it under Arduino 1.8.2 (NOT MPIDE) with compiler optimization set to zero so that all of my source lines would be preserved, and the -g option. I then fired up MPLAB-X (v 3.61), imported the ELF file and added the the chipKIT bootloader image under the project "Loadables" sources. I can then run the program fine under Debug and even set breakpoints within main.cpp, but I can't set any breakpoints within my sketch code (DSPI_Demo.ino.cpp. Before hitting the "Debug" button in MPLAB-X the BP is fine, but afterwards it is broken. The attached images show some of my sources and the BP behavior. Any thoughts
  3. Hi! I'm a big fan of standard tools, i.e. silicon vendor independent, like the Segger J-Link Programmer-Debugger I've reviewed. The Segger J-Link programmer-debugger lists Microchip PIC32MX and PIC32MZ among the MCUs it supports. Has anyone managed to connect the Segger J-Link and debug against a chipKIT board? Thank you!
  4. Hello together, I'm a student and I am going to buy the Basys3 board. At that nice student price I thought I'd get a Pmod for Debugging like a little screen. I will be programming only hardware circuits and my own processors. As it seems to me, all tutorials for the OLEDrgb Pmod are made for use with the Microblaze which is not something that I plan to do. For that kind of stuff I already have microcontrollers lying around. I want to be able to access the screen / output (maybe only leds are possible for this purpose? and 7 segments?) directly via my hardware like turning on and off LEDs for debugging and maybe also for displaying actual useful information. What would be the best Pmod for this sake? OLED? LCD? Are these even accessible via SystemVerilog? 7 Segment and LEDs should work afaik but the board already has a lot of them... Some examples: Showing which state of an automata I'm in, Showing if my clock is working, Displaying results of a calculation, ... Thank you in advance! Riesenrad
  5. One thing I learnt today was that Vivado has a Virtual I/O IP block, that allows you to see the state of signals deep in your design. You can also use it to inject signals into your design too. I've added a little project to my Wiki which connects the switches and LEDs on the Basys3 to an instance of the Virtual I/O block. http://hamsterworks.co.nz/mediawiki/index.php/Virtual_IO (Connecting to external I/O is not really the target end-use case - it would be perfect for monitoring status signals out of transceivers and memory controllers, or observing the state of misbehaving FSMs)
  6. Hello guys, I followed this tutorial "Embedded linux on zybo" http://www.instructables.com/id/Embedded-Linux-Tutorial-Zybo/ and everything works like a charm, I compiled the linux kernel and u-boot from digilent github, as a next step I said i'll be debugging Linux C apps. I'm trying hard to debug a linux application coded in xilinx SDK (2015.1) according to the follwoing two links: http://www.xilinx.com/support/documentation/sw_manuals/xilinx14_7/SDK_Doc/tasks/sdk_t_linux_application_debugging_system_debugger.htm what happens that when i try to press Debug, i got in the debug perspective .. "Target does not support Processes service" Am i supposed to use different Linux kernel (i.e. Petalinux) or Am is supposed to use different uramdisk ? Please let me know what am i missing???