Search the Community

Showing results for tags 'sdk'.



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 and the WaveForms software
    • 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 97 results

  1. I have developed a project on vivado using IPs of Xilinx, especially microblaze that is a softcore, so i programed microblaze in the SDK, but I want to store my hardware that I made in vivado and the program of the SDK in the non-volatile memory of the board basys3, so each time that I turn on the board basys3, automatically my project start without reprogramming the FPGA using the pc, if you could provide a tutorial step by step how to do that, I would thank you a lot.
  2. I want to implement an analog temperature sensor (LM35) using Microblaze on Vivado, I want to use an IP and i have tried use the XADC but is very complicated its configuration, so my question, Is there some IP that along with Microblaze allow reading of an analog signal?
  3. Hi, Long post warning! Short version question: When using FDwfDigitalInTriggerPositionSet and FDwfDigitalInTriggerSet API functions, is the first sample coincident with the trigger or at the next clock (divided down) tick? I am using the Analog Discovery Board to implement a SPI master interface in Python. I essentially married two examples which come with the SDK: DigitalOut_SPI.py and DigitalIn_Acquisition. It supports both options for CPOL and CPHA. The problem I am facing at the moment is that CPHA=1 is unreliable. It seems that I am not configuring the timing correctly for the input section. I am hoping that someone can tell me where I am going wrong. For reference, the project is hosted in GitHub here: https://github.com/mentaal/DwfSPI For the scenario CPHA=1 and CPOL=0, for MISO, I have the input set to trigger when Slave Select is asserted and the falling edge of SCLK like this: elif self.CPOL == 0 and self.CPHA == 1: dwf.FDwfDigitalInTriggerSet(hdwf, self.SS_mask, 0, 0, self.SCLK_mask) #low, high, rising, falling I have the input divider set to the SCLK frequency. This gives me twice as many bits but I just read every second bit. dwf.FDwfDigitalInDividerSet(hdwf, sclk_divider_ratio) #sample on clk edge to accomodate for CPHA==1 I setup the number of bits to read back like this: # set number of sample to acquire dwf.FDwfDigitalInBufferSizeSet(hdwf, sample_count) # number of samples after trigger dwf.FDwfDigitalInTriggerPositionSet(hdwf, sample_count) For example, using CPHA=1, a successful loopback test looks like this: (writing a single byte of value: 0x55 msb first) > python DwfSPI.py SPI_PINS(MOSI=0, MISO=3, SCLK=1, SS=2) DEBUG:__main__:Version: b'3.3.7' DEBUG:__main__:Number of Devices: 1 DEBUG:__main__:Opening first device DEBUG:__main__:Maximum buffer size is: c_long(4096) DEBUG:__main__:Number of samples collected: 18 INFO:__main__:Sample 0: 2, mosi: 0, miso: 0 INFO:__main__:Sample 1: 0, mosi: 0, miso: 0 INFO:__main__:Sample 2: 11, mosi: 1, miso: 1 INFO:__main__:Sample 3: 9, mosi: 1, miso: 1 INFO:__main__:Sample 4: 2, mosi: 0, miso: 0 INFO:__main__:Sample 5: 0, mosi: 0, miso: 0 INFO:__main__:Sample 6: 11, mosi: 1, miso: 1 INFO:__main__:Sample 7: 9, mosi: 1, miso: 1 INFO:__main__:Sample 8: 2, mosi: 0, miso: 0 INFO:__main__:Sample 9: 0, mosi: 0, miso: 0 INFO:__main__:Sample 10: 11, mosi: 1, miso: 1 INFO:__main__:Sample 11: 9, mosi: 1, miso: 1 INFO:__main__:Sample 12: 2, mosi: 0, miso: 0 INFO:__main__:Sample 13: 0, mosi: 0, miso: 0 INFO:__main__:Sample 14: 11, mosi: 1, miso: 1 INFO:__main__:Sample 15: 9, mosi: 1, miso: 1 INFO:__main__:Sample 16: 4, mosi: 0, miso: 0 INFO:__main__:Sample 17: 4, mosi: 0, miso: 0 0x55 A failure looks like this: > python DwfSPI.py SPI_PINS(MOSI=0, MISO=3, SCLK=1, SS=2) DEBUG:__main__:Version: b'3.3.7' DEBUG:__main__:Number of Devices: 1 DEBUG:__main__:Opening first device DEBUG:__main__:Maximum buffer size is: c_long(4096) DEBUG:__main__:Number of samples collected: 18 INFO:__main__:Sample 0: 2, mosi: 0, miso: 0 INFO:__main__:Sample 1: 0, mosi: 0, miso: 0 INFO:__main__:Sample 2: 3, mosi: 1, miso: 0 INFO:__main__:Sample 3: 9, mosi: 1, miso: 1 INFO:__main__:Sample 4: 10, mosi: 0, miso: 1 INFO:__main__:Sample 5: 0, mosi: 0, miso: 0 INFO:__main__:Sample 6: 3, mosi: 1, miso: 0 INFO:__main__:Sample 7: 9, mosi: 1, miso: 1 INFO:__main__:Sample 8: 10, mosi: 0, miso: 1 INFO:__main__:Sample 9: 0, mosi: 0, miso: 0 INFO:__main__:Sample 10: 3, mosi: 1, miso: 0 INFO:__main__:Sample 11: 9, mosi: 1, miso: 1 INFO:__main__:Sample 12: 10, mosi: 0, miso: 1 INFO:__main__:Sample 13: 0, mosi: 0, miso: 0 INFO:__main__:Sample 14: 3, mosi: 1, miso: 0 INFO:__main__:Sample 15: 9, mosi: 1, miso: 1 INFO:__main__:Sample 16: 12, mosi: 0, miso: 1 INFO:__main__:Sample 17: 4, mosi: 0, miso: 0 0x2a Traceback (most recent call last): File "DwfSPI.py", line 258, in <module> assert returned == [0x55] AssertionError I would have chalked this up to a dodgy hardware setup but when I use CPHA=0, I can run 1000s of frames without error.
  4. Hello, I'm using the AD2 and the waveforms SDK. What I need to do is create a single square pulse, non-repeating. Is it possible with the SDK to do this? In other words, I need it to run for only a single period. Turning the generator on and off in software is just too imprecise. Thanks in advance!
  5. After successfully creating and running the Microblaze example project on my Nexys4DDR, I went on to create the project that walks through how to use the various Pmods. I followed the instructions carefully, and succesfully generate the bitstream and export the HW including bitstream. The SDK launches fine as well. However, when I go to create the new empty application, I receive the following error, "Project cannot be created. Reason: Internal error". When I click on "Details>>" I read the following: Internal Error: Failed to closesw "D:/Projects/FPGA/IPMod1/IPMod1.sdk/pmods_bsp/system.mss" Reason: Cannot close sw design 'D:/Projects/FPGA/IPMod1/IPMod1.sdk/pmods_bsp/system.mss'. Design is not opened in the current session. I notice first and foremost that the pmods_bsp directory doesn't exist under the IPMod1.sdk folder. Of course, this means also that none of the referenced files from that folder exist either. This would seem to be the root of the problem. However, I have no idea why this folder wasn't created nor how to resolve the issue. Any help is appreciated. Dave I also found the following in the SDK.log. I'm not sure if this helps. From what I can tell the generate_bsp process is failing. 11:42:18 ERROR : (XSDB Server)ERROR: [Hsi 55-1545] Problem running tcl command ::sw_standalone_v5_5::post_generate : couldn't execute "mb-ar": invalid argument while executing "exec $archiver -d $libgloss_a _interrupt_handler.o" (procedure "::sw_standalone_v5_5::post_generate" line 18) invoked from within "::sw_standalone_v5_5::post_generate standalone" 11:42:18 ERROR : (XSDB Server)ERROR: [Hsi 55-1443] Error(s) while running TCL procedure post_generate() 11:42:18 ERROR : (XSDB Server)ERROR: [Hsi 55-1450] Error: running generate_bsp. 11:42:18 ERROR : Failed to closesw "D:/Projects/FPGA/IPMod1/IPMod1.sdk/pmods_bsp/system.mss" Reason: Cannot close sw design 'D:/Projects/FPGA/IPMod1/IPMod1.sdk/pmods_bsp/system.mss'. Design is not opened in the current session. 11:42:32 ERROR : (XSDB Server)ERROR: [Hsi 55-1545] Problem running tcl command ::sw_standalone_v5_5::post_generate : couldn't execute "mb-ar": invalid argument while executing "exec $archiver -d $libgloss_a _interrupt_handler.o" (procedure "::sw_standalone_v5_5::post_generate" line 18) invoked from within "::sw_standalone_v5_5::post_generate standalone" 11:42:32 ERROR : (XSDB Server)ERROR: [Hsi 55-1443] Error(s) while running TCL procedure post_generate() 11:42:32 ERROR : (XSDB Server)ERROR: [Hsi 55-1450] Error: running generate_bsp. 11:42:32 ERROR : Failed to closesw "D:/Projects/FPGA/IPMod1/IPMod1.sdk/pmods_bsp/system.mss" Reason: Cannot close sw design 'D:/Projects/FPGA/IPMod1/IPMod1.sdk/pmods_bsp/system.mss'. Design is not opened in the current session. 11:42:56 ERROR : (XSDB Server)ERROR: [Hsi 55-1545] Problem running tcl command ::sw_standalone_v5_5::post_generate : couldn't execute "mb-ar": invalid argument while executing "exec $archiver -d $libgloss_a _interrupt_handler.o" (procedure "::sw_standalone_v5_5::post_generate" line 18) invoked from within "::sw_standalone_v5_5::post_generate standalone" 11:42:56 ERROR : (XSDB Server)ERROR: [Hsi 55-1443] Error(s) while running TCL procedure post_generate() 11:42:56 ERROR : (XSDB Server)ERROR: [Hsi 55-1450] Error: running generate_bsp. 11:42:56 ERROR : Failed to closesw "D:/Projects/FPGA/IPMod1/IPMod1.sdk/pmods_bsp/system.mss" Reason: Cannot close sw design 'D:/Projects/FPGA/IPMod1/IPMod1.sdk/pmods_bsp/system.mss'. Design is not opened in the current session. 11:51:58 ERROR : (XSDB Server)ERROR: [Hsi 55-1545] Problem running tcl command ::sw_standalone_v5_5::post_generate : couldn't execute "mb-ar": invalid argument while executing "exec $archiver -d $libgloss_a _interrupt_handler.o" (procedure "::sw_standalone_v5_5::post_generate" line 18) invoked from within "::sw_standalone_v5_5::post_generate standalone" 11:51:58 ERROR : (XSDB Server)ERROR: [Hsi 55-1443] Error(s) while running TCL procedure post_generate() 11:51:58 ERROR : (XSDB Server)ERROR: [Hsi 55-1450] Error: running generate_bsp. 11:51:58 ERROR : Failed to closesw "D:/Projects/FPGA/IPMod1/IPMod1.sdk/pmods_bsp/system.mss" Reason: Cannot close sw design 'D:/Projects/FPGA/IPMod1/IPMod1.sdk/pmods_bsp/system.mss'. Design is not opened in the current session.
  6. Abish sj

    BOOT IMAGE

    Hi guys, A screen shot as you see below is a SDK projects that has two system_wrapper_hw_platform folder. this program work properly when I program from JTAG, But when I'm trying to create BOOT Image, it's not work. How can I create the boot in this situation? please help me about this problem. thanks.
  7. I just purchased an Analog Discovery and have been enjoying it so far. The OSX Waveforms2105 app works flawlessly. I'm now trying to run the python example code in the SDK in order to write my own software. If I run `DigitalOut_Pins.py`, I get the following: DWF Version: 3.3.5 Opening first device failed to open device Any ideas? Can I debug this in any way? Thanks.
  8. I want to build the DaciDemo project in Visual Studio 2010. Following the recipes given in "Building and Adept SDK Project in Visual Studio.pdf" one has to add all required paths and the additional dependencies (of course at different locations due to the fact that I am using 2010 and the reference doc is 2008), all libraries and other files get nicely attached. Nevertheless, the project won't build. There are 10 Error messages , all of the type: Error 1 error LNK2019: unresolved external symbol __imp__## referenced in function _main c:\....\visual studio 2010\Projects\dacidemo\dacidemo\DaciDemo.obj dacidemo where ## stands for {DmgrClose, DaciDisable, DaciGetBuf, DaciPutBuf, ...} - shortly said: all references to the attached libararies occuring in the project. In the meantime I found out that changing the library path (in Project Property sheet | Linker | C++Directories|) from "lib64 " to "lib" will eliminate 8 of the above 10 errors (even though my platform is Win64 :-) ). Now all external names from "Daci" are resolved but the "Dmgr" references are still left: {DmgrClose,DmgrOpen} The problem is solved: There is an error in the documentation file that comes with the SDK! It is NOT enough to include only depp.h and daci.h in the "additional dependencies" as stated in the documentation but one has to include dmgr.h as well. Obviously, depp.h and daci.h do not include any external symbol to open and close depp resources.
  9. Hello all, I need to use Analog Discovery to capture a trace from board and am completely new to this. The board has program consisting of a timer between the two operations such that after first operation there is significant interval before the next one to make it easily noticeable. I am using the channel 0 pins at the two end points where I can get the trace. The problem I am having is that I want a zoomed capture of the operation only but not sure how to do it. I tried setting the acquisition mode to trigger but it does not seems to work correctly. Can someone please inform me how should I proceed with this? I also tried using python SDK but not much luck on that side either. Have attached screen grabs from Waveform2015 first of which shows the 'peak' I want to zoomed in and the second pic is of my terrible attempt at zooming... Thank you in advance and any help would be truly appreciated.
  10. I'm trying to follow this getting started tutorial for the Zybo board. I'm using Linux OS, and initially I started with Vivado 2015.4, but updated to 2016.2 when the problem appeared. The update didn't fix the problem. When following the tutorial, everything goes as expected until I reach step 9.4: when I create the new application project with the hello world example, the generated BSP files have 32 errors, so the project cannot build. I googled the error, and found tons of forum posts with similar problems. It looks like most of the times the problems disappear if you launch SDK from the OS menu, instead of doing it from Vivado. But that didn't fix the problem for me. I have attached a capture showing the errors. How can I fix this problem?
  11. I am a beginner for the nexys4 DDR board, I follow the step to build the microblaze servers as the link https://reference.digilentinc.com/nexys4-ddr:gsmbs When I run the echo_server on the sdk, I am struggling on the memory mapping problem. java.lang.RuntimeException: Failed to download ELF file Unknown Error Occured Section, 0x80000000-0x8002e173 Not Accessible from Processor I-Side Interface at com.xilinx.sdk.targetmanager.internal.TM.downloadELF(TM.java:686) at com.xilinx.sdk.debug.core.internal.AppRunner.run(AppRunner.java:129) at com.xilinx.sdk.debug.core.XilinxAppLaunchConfigurationDelegate.runApplication(XilinxAppLaunchConfigurationDelegate.java:609) at com.xilinx.sdk.debug.core.XilinxAppLaunchConfigurationDelegate.launch(XilinxAppLaunchConfigurationDelegate.java:296) at com.xilinx.sdk.debug.ui.XilinxAppLaunchDelegateWrapper.launch(XilinxAppLaunchDelegateWrapper.java:31) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018) at org.eclipse.debug.internal.ui.DebugUIPlugin$7.run(DebugUIPlugin.java:1104) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) I don't know what is the I-side interface of the processor. I verily linker script file for memory region mapping as suggested in the tutorial step 9. I am sure I didn't use the BRAM for mapping. So I don't think it is due the out of range memory. And I try to enlarge the stack and heap size as someone suggest could solve this problem, but still got the error message. Here is the message print out from the XMD console. Downloading Program -- C:/FPGA_project/Tutorial/microblaze_tutorial/project_server_memory/project_server_memory.sdk/echo_server/Debug/echo_server.elf section, .vectors.reset: 0x00000000-0x00000007 section, .vectors.sw_exception: 0x00000008-0x0000000f section, .vectors.interrupt: 0x00000010-0x00000017 section, .vectors.hw_exception: 0x00000020-0x00000027 section, .text: 0x80000000-0x8002e177 section, .init: 0x8002e178-0x8002e1b3 section, .fini: 0x8002e1b4-0x8002e1d3 It seems the problem is mapping the .text into that range of memory. attached is the lscript.ld MEMORY { microblaze_0_local_memory_ilmb_bram_if_cntlr_microblaze_0_local_memory_dlmb_bram_if_cntlr : ORIGIN = 0x50, LENGTH = 0x1FB0 mig_7series_0 : ORIGIN = 0x80000000, LENGTH = 0xA000000 } So can anyone explain why we got this problem? and how to solve this efficiently? It seems that everyone got the same error message but have different solution get out. lscript.ld
  12. Hi, I had no Problem to program the qspi from Vivado by following the guide from the resource center. But that only gives me the hardware configuration. I also need to Program the Microblaze from the SDK. In previous projects with the ISE tool I used the iMPACT tool from Xilinx, but that doesn't seem to be available!? What is the best and easiest way to do a full programming (hardware and microblaze software) from the SDK? I am using the Vivado 2015.3 WebPACK with a Nexys4-DDR Board. Thanks party-pansen
  13. Hi, I have been using Xilinx Vivado 2015.4 version and I have an Arty-7 board. Firstly, I created hardware design and launch SDK. sadly something goes to wrong. I get an error message pop-up window. Thank you for your interest.
  14. Hello, I just recently bought a zybo board and was following the digilent tutorial and almost finished the getting started project. However, I cannot make the helloworld.c file after launching the SDK. I can still program the PL side, but if I cannot utilize the PS side. SO now I basically have a standard FPGA until I can get this issue resolved. I have been looking through the xilinx forums too and haven't seen a good solution to this problem. here is an example of the console output and a screenshot of the error message that pops up Building file: ../src/helloworld.c Invoking: ARM gcc compiler arm-xilinx-eabi-gcc -Wall -O0 -g3 -c -fmessage-length=0 -MT"src/helloworld.o" -I../../getting_started_with_ZYBO_bsp/ps7_cortexa9_0/include -MMD -MP -MF"src/helloworld.d" -MT"src/helloworld.d" -o "src/helloworld.o" "../src/helloworld.c" make: *** [src/helloworld.o] Error -1073741502
  15. I’ve just purchased the Analog Discovery 2 last week and everything works fine when using the Waveforms software. I am now trying to use the SDK to customize my own application by using your sample Python code as a starting point. I was able to run AnalogIn_Sample.py file and everything worked as expected. However, when I ran AnalogIO_AnalogDiscovery_Power.py file, the power supply was not turned on. I used a multi-meter to measure the voltage at V+ and V- pins but they all stayed at zero volt. I also tried to modify the parameters in dwf.FDwfAnalogIOChannelNodeSet(hdwf, 0, 0, 1) function but the results were the same. Does the current SDK support all Analog Discovery 2 functions? Thanks.
  16. After some research and homework I came to know that digilent also provide different DCAP or APT dlls, for Software development in windows, along with very small demo projects in VC++ for every APT and the reference manuals, they all comprise to make "Digilent Adept SDK". So I quickly opened the DACI(UART) demo in Visual Studio 2015, in order to communicate with my board over UART, I was able to implement Device Table and get the device name string, I also managed to open the device using DmgrOpen() Funtion and got a interface handle, but i can't seem to get the DaciEnable() to work, and using the DmgrGetLastError tells me that the device(Nexys4-DDR) is not supported for DACI, which is very improbable. Then in hopes of troubleshooting the problem, I check for DmgrGetDtpCount() and I get the value '1', which I think means that there's one way to communicate with the device(which is not very informative), then I try DaciGetPortCount() which returns the value '0' to the pointer variable, which I think implies that there are NO DACI ports, :(. But I can see that while debugging the code, during the DmgrOpen() Function call, VS loads two FTDI dlls, I'm stuck here for a while now. And I hope that this question interests the experts at Digilent Forums, for I think they can see through this problem easily. And I attached the cpp file, which I'm working on. Thanks a lot !! DaciDemo_modified.cpp
  17. Hello everyone, First of all, thanks for all the work digilent engineers have done. Now I meet a problem, hope any one can give me some guide or suggestion. I am now trying to using ucosiii on my basys3 board. But unfortunately, even the simplest "hello world" uart printing example makes the bram overflow. Here is the error information I get from the sdk, region `microblaze_0_local_memory_ilmb_bram_if_cntlr_microblaze_0_local_memory_dlmb_bram_if_cntlr' overflowed by 37440 bytes ucos_project.elf section `.text' will not fit in region `microblaze_0_local_memory_ilmb_bram_if_cntlr_microblaze_0_local_memory_dlmb_bram_if_cntlr' I don't think this tiny example will occupying more than 64kb ram, because I have configure the ram of the microblaze to 32k. It probably some tricky setting I missed. And I totally obey the official tutorial from the following link and the only difference is in the basys3 we do not have a ddr3 memory, but I donot think that is the problem (or maybe ?), because I am now trying a very very small program, 32k is much more than enough (I think). https://doc.micrium.com/display/UCOSXSDK/uCOS+BSP+on+the+MicroBlaze+Tutorial#uCOSBSPontheMicroBlazeTutorial-Step3.AddandconfiguretheMemoryInterfaceGenerator(MIG) Did anyone meet similar problem, please kindly give any comment, Thanks. BTW, my environment is vivado 2015.1 with sdk
  18. I'm using the python version of the Analog Discovery SDK to directly access the device. When I interrogate the device for its analog input ranges, it tells me that it has two: 5.0 and 50.0 volts. If I run the Waveform software I see many more possibilities, many decades of 1-2-5 steps. A 14 bit adc with an input range of 5V has a step of about 300 uV. From this I infer that the extra resolution Waveform provides is not simply a matter of zooming in on the 5V range. Does anyone know what's going on?
  19. Hi, I'm new here with the Zybo and Vivado. I have Vivado 2015.2 and the SDK installed (I think completely) on my Fedora 22 laptop. I've successfully worked my way through the Digilent Zybo Getting Started reference page until I get to the final step of running everything on my Zybo board. When I hit "Program", I get an error dialog telling me the "Program FPGA failed" with a number of troubleshooting hints (board connected properly, proper cable for zynq board, green led when using Xilinx Platform Cable USB) The board is connected to a working USB20. port with a standard USB cable (came with the board). When first plugged in, RX flashes a few times, LD4 is lit and LD10 and LD11 are lit. After the failed programming attempt, LD4 goes out, LD10 and LD11 stay lit. The FTDI chip is found by Linux and enumerated: [[email protected] ~]$ lsusb Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 058f:b003 Alcor Micro Corp. Bus 004 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 004 Device 004: ID 03eb:0902 Atmel Corp. 4-Port Hub Bus 004 Device 007: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO IC Bus 004 Device 005: ID 413c:2003 Dell Computer Corp. Keyboard And it shows up as these serial devices: [[email protected] ~]$ ls -l /dev/serial total 0 drwxr-xr-x. 2 root root 80 Jul 14 11:49 by-id drwxr-xr-x. 2 root root 80 Jul 14 11:49 by-path [[email protected] ~]$ At this point, I'm stumped. I've seen mention of the Digilient Plugin for Zilinx Tools as a solution for some problems but it doesn't appear to apply to Vivado. I'm currently STUMPED! Any thoughts???? Thanks! Rick
  20. Hello, I'm trying to get http://www.digilentinc.com/Data/Products/ATLYS/Atlys_AXI_Web_Server_Demo_v_1_02.zip to work on my Atlys board but I'm running into errors in SDK. After I clean & build, the elfcheck passes: 10:39:52 **** Incremental Build of configuration Debug for project Atlys_Webserver_Demo **** make all 'Building file: ../src/additional_sf_ops.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/additional_sf_ops.d" -MT"src/additional_sf_ops.d" -o "src/additional_sf_ops.o" "../src/additional_sf_ops.c" ../src/additional_sf_ops.c: In function 'hchartoi': ../src/additional_sf_ops.c:837:5: warning: array subscript has type 'char' [-Wchar-subscripts] ../src/additional_sf_ops.c:843:5: warning: array subscript has type 'char' [-Wchar-subscripts] 'Finished building: ../src/additional_sf_ops.c' ' ' 'Building file: ../src/dispatch.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/dispatch.d" -MT"src/dispatch.d" -o "src/dispatch.o" "../src/dispatch.c" ../src/dispatch.c: In function 'print_headers': ../src/dispatch.c:31:9: warning: implicit declaration of function 'print_echo_app_header' [-Wimplicit-function-declaration] ../src/dispatch.c:34:9: warning: implicit declaration of function 'print_rxperf_app_header' [-Wimplicit-function-declaration] ../src/dispatch.c:37:9: warning: implicit declaration of function 'print_txperf_app_header' [-Wimplicit-function-declaration] ../src/dispatch.c:40:9: warning: implicit declaration of function 'print_tftp_app_header' [-Wimplicit-function-declaration] ../src/dispatch.c:43:9: warning: implicit declaration of function 'print_web_app_header' [-Wimplicit-function-declaration] ../src/dispatch.c: In function 'start_applications': ../src/dispatch.c:52:9: warning: implicit declaration of function 'start_echo_application' [-Wimplicit-function-declaration] ../src/dispatch.c:55:9: warning: implicit declaration of function 'start_rxperf_application' [-Wimplicit-function-declaration] ../src/dispatch.c:58:9: warning: implicit declaration of function 'start_txperf_application' [-Wimplicit-function-declaration] ../src/dispatch.c:61:9: warning: implicit declaration of function 'start_tftp_application' [-Wimplicit-function-declaration] ../src/dispatch.c:64:9: warning: implicit declaration of function 'start_web_application' [-Wimplicit-function-declaration] ../src/dispatch.c: In function 'transfer_data': ../src/dispatch.c:71:9: warning: implicit declaration of function 'transfer_echo_data' [-Wimplicit-function-declaration] ../src/dispatch.c:74:9: warning: implicit declaration of function 'transfer_rxperf_data' [-Wimplicit-function-declaration] ../src/dispatch.c:77:9: warning: implicit declaration of function 'transfer_txperf_data' [-Wimplicit-function-declaration] ../src/dispatch.c:80:9: warning: implicit declaration of function 'transfer_tftp_data' [-Wimplicit-function-declaration] ../src/dispatch.c:83:9: warning: implicit declaration of function 'transfer_web_data' [-Wimplicit-function-declaration] ../src/dispatch.c:84:1: warning: control reaches end of non-void function [-Wreturn-type] ../src/dispatch.c: In function 'start_applications': ../src/dispatch.c:65:1: warning: control reaches end of non-void function [-Wreturn-type] 'Finished building: ../src/dispatch.c' ' ' 'Building file: ../src/echo.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/echo.d" -MT"src/echo.d" -o "src/echo.o" "../src/echo.c" 'Finished building: ../src/echo.c' ' ' 'Building file: ../src/http_response.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/http_response.d" -MT"src/http_response.d" -o "src/http_response.o" "../src/http_response.c" ../src/http_response.c: In function 'do_delete_file': ../src/http_response.c:529:12: warning: unused variable 'fd' [-Wunused-variable] ../src/http_response.c: In function 'do_list_file': ../src/http_response.c:729:4: warning: 'return' with no value, in function returning non-void [-Wreturn-type] ../src/http_response.c: In function 'do_http_get': ../src/http_response.c:868:4: warning: 'return' with no value, in function returning non-void [-Wreturn-type] ../src/http_response.c: In function 'data_receive_callback': ../src/http_response.c:353:5: warning: 'pcb' may be used uninitialized in this function [-Wuninitialized] ../src/http_response.c: In function 'do_download_file': ../src/http_response.c:459:7: warning: 'buf' may be used uninitialized in this function [-Wuninitialized] 'Finished building: ../src/http_response.c' ' ' 'Building file: ../src/main.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/main.d" -MT"src/main.d" -o "src/main.o" "../src/main.c" ../src/main.c: In function 'main': ../src/main.c:85:2: warning: implicit declaration of function 'lwip_init' [-Wimplicit-function-declaration] ../src/main.c:96:2: warning: implicit declaration of function 'platform_enable_interrupts' [-Wimplicit-function-declaration] ../src/main.c:116:3: warning: implicit declaration of function 'get_switch_state' [-Wimplicit-function-declaration] ../src/main.c:117:3: warning: implicit declaration of function 'get_pushbutton_state' [-Wimplicit-function-declaration] 'Finished building: ../src/main.c' ' ' 'Building file: ../src/platform.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/platform.d" -MT"src/platform.d" -o "src/platform.o" "../src/platform.c" ../src/platform.c: In function 'timer_callback': ../src/platform.c:50:2: warning: implicit declaration of function 'tcp_fasttmr' [-Wimplicit-function-declaration] ../src/platform.c:54:3: warning: implicit declaration of function 'tcp_slowtmr' [-Wimplicit-function-declaration] ../src/platform.c: In function 'xadapter_timer_handler': ../src/platform.c:62:11: warning: unused variable 'tcsr' [-Wunused-variable] ../src/platform.c:61:12: warning: unused variable 'timer_base' [-Wunused-variable] ../src/platform.c: In function 'init_platform': ../src/platform.c:257:2: warning: implicit declaration of function 'platform_init_fs' [-Wimplicit-function-declaration] 'Finished building: ../src/platform.c' ' ' 'Building file: ../src/platform_fs.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/platform_fs.d" -MT"src/platform_fs.d" -o "src/platform_fs.o" "../src/platform_fs.c" 'Finished building: ../src/platform_fs.c' ' ' 'Building file: ../src/platform_gpio.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/platform_gpio.d" -MT"src/platform_gpio.d" -o "src/platform_gpio.o" "../src/platform_gpio.c" 'Finished building: ../src/platform_gpio.c' ' ' 'Building file: ../src/prot_malloc.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/prot_malloc.d" -MT"src/prot_malloc.d" -o "src/prot_malloc.o" "../src/prot_malloc.c" ../src/prot_malloc.c: In function 'prot_mem_free': ../src/prot_malloc.c:39:1: warning: control reaches end of non-void function [-Wreturn-type] 'Finished building: ../src/prot_malloc.c' ' ' 'Building file: ../src/rxperf.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/rxperf.d" -MT"src/rxperf.d" -o "src/rxperf.o" "../src/rxperf.c" 'Finished building: ../src/rxperf.c' ' ' 'Building file: ../src/tftpserver.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/tftpserver.d" -MT"src/tftpserver.d" -o "src/tftpserver.o" "../src/tftpserver.c" ../src/tftpserver.c:57:8: warning: type defaults to 'int' in declaration of 'tftp_server_started' [-Wimplicit-int] ../src/tftpserver.c: In function 'tftp_process_read': ../src/tftpserver.c:191:13: warning: unused variable 'block' [-Wunused-variable] ../src/tftpserver.c:191:10: warning: unused variable 'n' [-Wunused-variable] ../src/tftpserver.c: In function 'tftp_process_write': ../src/tftpserver.c:276:13: warning: unused variable 'block' [-Wunused-variable] ../src/tftpserver.c:276:10: warning: unused variable 'n' [-Wunused-variable] ../src/tftpserver.c: In function 'start_tftp_application': ../src/tftpserver.c:406:1: warning: control reaches end of non-void function [-Wreturn-type] 'Finished building: ../src/tftpserver.c' ' ' 'Building file: ../src/tftputils.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/tftputils.d" -MT"src/tftputils.d" -o "src/tftputils.o" "../src/tftputils.c" 'Finished building: ../src/tftputils.c' ' ' 'Building file: ../src/txperf.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/txperf.d" -MT"src/txperf.d" -o "src/txperf.o" "../src/txperf.c" 'Finished building: ../src/txperf.c' ' ' 'Building file: ../src/urxperf.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/urxperf.d" -MT"src/urxperf.d" -o "src/urxperf.o" "../src/urxperf.c" 'Finished building: ../src/urxperf.c' ' ' 'Building file: ../src/utxperf.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/utxperf.d" -MT"src/utxperf.d" -o "src/utxperf.o" "../src/utxperf.c" ../src/utxperf.c: In function 'transfer_utxperf_data': ../src/utxperf.c:37:6: warning: unused variable 'copy' [-Wunused-variable] 'Finished building: ../src/utxperf.c' ' ' 'Building file: ../src/web_utils.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/web_utils.d" -MT"src/web_utils.d" -o "src/web_utils.o" "../src/web_utils.c" 'Finished building: ../src/web_utils.c' ' ' 'Building file: ../src/webserver.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/webserver.d" -MT"src/webserver.d" -o "src/webserver.o" "../src/webserver.c" ../src/webserver.c: In function 'http_sent_callback': ../src/webserver.c:86:13: warning: implicit declaration of function 'mfs_file_read' [-Wimplicit-function-declaration] ../src/webserver.c:91:17: warning: implicit declaration of function 'mfs_file_close' [-Wimplicit-function-declaration] ../src/webserver.c: In function 'http_recv_callback': ../src/webserver.c:115:3: warning: 'return' with no value, in function returning non-void [-Wreturn-type] ../src/webserver.c:117:3: warning: 'return' with no value, in function returning non-void [-Wreturn-type] ../src/webserver.c: In function 'start_web_application': ../src/webserver.c:158:2: warning: implicit declaration of function 'platform_init_gpios' [-Wimplicit-function-declaration] 'Finished building: ../src/webserver.c' ' ' 'Building file: ../src/xquad_spi.c' 'Invoking: MicroBlaze gcc compiler' mb-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../standalone_bsp_0/microblaze_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/xquad_spi.d" -MT"src/xquad_spi.d" -o "src/xquad_spi.o" "../src/xquad_spi.c" 'Finished building: ../src/xquad_spi.c' ' ' 'Building target: Atlys_Webserver_Demo.elf' 'Invoking: MicroBlaze gcc linker' mb-gcc -Wl,-T -Wl,../src/lscript.ld -L../../standalone_bsp_0/microblaze_0/lib -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v8.40.b -mno-xl-soft-mul -Wl,--no-relax -Wl,--gc-sections -o "Atlys_Webserver_Demo.elf" ./src/additional_sf_ops.o ./src/dispatch.o ./src/echo.o ./src/http_response.o ./src/main.o ./src/platform.o ./src/platform_fs.o ./src/platform_gpio.o ./src/prot_malloc.o ./src/rxperf.o ./src/tftpserver.o ./src/tftputils.o ./src/txperf.o ./src/urxperf.o ./src/utxperf.o ./src/web_utils.o ./src/webserver.o ./src/xquad_spi.o -Wl,--start-group,-lxil,-lgcc,-lc,--end-group -Wl,--start-group,-lxil,-llwip4,-lgcc,-lc,--end-group 'Finished building target: Atlys_Webserver_Demo.elf' ' ' 'Invoking: MicroBlaze Print Size' mb-size Atlys_Webserver_Demo.elf |tee "Atlys_Webserver_Demo.elf.size" text data bss dec hex filename 172996 1552 34190284 34364832 20c5da0 Atlys_Webserver_Demo.elf 'Finished building: Atlys_Webserver_Demo.elf.size' ' ' 'Invoking: Xilinx ELF Check' elfcheck Atlys_Webserver_Demo.elf -hw ../../hw_platform/system.xml -pe microblaze_0 |tee "Atlys_Webserver_Demo.elf.elfcheck" elfcheck Xilinx EDK 14.7 Build EDK_P.20131013 Copyright (c) 1995-2012 Xilinx, Inc. All rights reserved. Command Line: elfcheck -hw ../../hw_platform/system.xml -pe microblaze_0 Atlys_Webserver_Demo.elf ELF file : Atlys_Webserver_Demo.elf elfcheck passed. 'Finished building: Atlys_Webserver_Demo.elf.elfcheck' ' ' 10:40:03 Build Finished (took 11s.626ms) However when I click program FPGA, I get elfcheck -hw C:/Users/C16Evan.Richter/Desktop/microBlaze/final_project/hw_platform/system.xml -mode bootload -mem BRAM -pe microblaze_0 C:/Users/C16Evan.Richter/Desktop/microBlaze/final_project/Atlys_Webserver_Demo/Debug/Atlys_Webserver_Demo.elf elfcheck Xilinx EDK 14.7 Build EDK_P.20131013 Copyright (c) 1995-2012 Xilinx, Inc. All rights reserved. Command Line: elfcheck -hw C:/Users/C16Evan.Richter/Desktop/microBlaze/final_project/hw_platform/system.xml -mode bootload -mem BRAM -pe microblaze_0 C:/Users/C16Evan.Richter/Desktop/microBlaze/final_project/Atlys_Webserver_Demo/D ebug/Atlys_Webserver_Demo.elf ELF file : C:/Users/C16Evan.Richter/Desktop/microBlaze/final_project/Atlys_Webserver_Demo/D ebug/Atlys_Webserver_Demo.elf ERROR:EDK:3165 - elfcheck failed! The following sections did not fit into Processor BRAM memory: Section .data (0xC002A3D0 - 0xC002A9CF) Section .rodata (0xC0027D04 - 0xC002A3CB) Section .dtors (0xC0027CFC - 0xC0027D03) Section .ctors (0xC0027CF4 - 0xC0027CFB) Section .fini (0xC0027CD4 - 0xC0027CF3) Section .init (0xC0027C98 - 0xC0027CD3) Section .text (0xC0000000 - 0xC0027C97) Try using the linker script generation tools to generate an ELF that maps correctly to your hardware design. Programming the FPGA failed due to errors from elfcheck My lscript.ld file is as follows: /*******************************************************************/ /* */ /* This file is automatically generated by linker script generator.*/ /* */ /* Version: Xilinx EDK 14.3 EDK_P.40xd */ /* */ /* Copyright (c) 2010 Xilinx, Inc. All rights reserved. */ /* */ /* Description : MicroBlaze Linker Script */ /* */ /*******************************************************************/ _STACK_SIZE = DEFINED(_STACK_SIZE) ? _STACK_SIZE : 0x1000000; _HEAP_SIZE = DEFINED(_HEAP_SIZE) ? _HEAP_SIZE : 0x1000000; /* Define Memories in the system */ MEMORY { microblaze_0_i_bram_ctrl_microblaze_0_d_bram_ctrl : ORIGIN = 0x00000050, LENGTH = 0x00007FB0 mcb_ddr2_S0_AXI_BASEADDR : ORIGIN = 0xC0000000, LENGTH = 0x08000000 } /* Specify the default entry point to the program */ ENTRY(_start) /* Define the sections, and where they are mapped in memory */ SECTIONS { .vectors.reset 0x00000000 : { *(.vectors.reset) } .vectors.sw_exception 0x00000008 : { *(.vectors.sw_exception) } .vectors.interrupt 0x00000010 : { *(.vectors.interrupt) } .vectors.hw_exception 0x00000020 : { *(.vectors.hw_exception) } .text : { *(.text) *(.text.*) *(.gnu.linkonce.t.*) } > mcb_ddr2_S0_AXI_BASEADDR .init : { KEEP (*(.init)) } > mcb_ddr2_S0_AXI_BASEADDR .fini : { KEEP (*(.fini)) } > mcb_ddr2_S0_AXI_BASEADDR .ctors : { __CTOR_LIST__ = .; ___CTORS_LIST___ = .; KEEP (*crtbegin.o(.ctors)) KEEP (*(EXCLUDE_FILE(*crtend.o) .ctors)) KEEP (*(SORT(.ctors.*))) KEEP (*(.ctors)) __CTOR_END__ = .; ___CTORS_END___ = .; } > mcb_ddr2_S0_AXI_BASEADDR .dtors : { __DTOR_LIST__ = .; ___DTORS_LIST___ = .; KEEP (*crtbegin.o(.dtors)) KEEP (*(EXCLUDE_FILE(*crtend.o) .dtors)) KEEP (*(SORT(.dtors.*))) KEEP (*(.dtors)) PROVIDE(__DTOR_END__ = .); PROVIDE(___DTORS_END___ = .); } > mcb_ddr2_S0_AXI_BASEADDR .rodata : { __rodata_start = .; *(.rodata) *(.rodata.*) *(.gnu.linkonce.r.*) __rodata_end = .; } > mcb_ddr2_S0_AXI_BASEADDR .sdata2 : { . = ALIGN(8); __sdata2_start = .; *(.sdata2) *(.sdata2.*) *(.gnu.linkonce.s2.*) . = ALIGN(8); __sdata2_end = .; } > mcb_ddr2_S0_AXI_BASEADDR .sbss2 : { __sbss2_start = .; *(.sbss2) *(.sbss2.*) *(.gnu.linkonce.sb2.*) __sbss2_end = .; } > mcb_ddr2_S0_AXI_BASEADDR .data : { . = ALIGN(4); __data_start = .; *(.data) *(.data.*) *(.gnu.linkonce.d.*) __data_end = .; } > mcb_ddr2_S0_AXI_BASEADDR .got : { *(.got) } > mcb_ddr2_S0_AXI_BASEADDR .got1 : { *(.got1) } > mcb_ddr2_S0_AXI_BASEADDR .got2 : { *(.got2) } > mcb_ddr2_S0_AXI_BASEADDR .eh_frame : { *(.eh_frame) } > mcb_ddr2_S0_AXI_BASEADDR .jcr : { *(.jcr) } > mcb_ddr2_S0_AXI_BASEADDR .gcc_except_table : { *(.gcc_except_table) } > mcb_ddr2_S0_AXI_BASEADDR .sdata : { . = ALIGN(8); __sdata_start = .; *(.sdata) *(.sdata.*) *(.gnu.linkonce.s.*) __sdata_end = .; } > mcb_ddr2_S0_AXI_BASEADDR .sbss (NOLOAD) : { . = ALIGN(4); __sbss_start = .; *(.sbss) *(.sbss.*) *(.gnu.linkonce.sb.*) . = ALIGN(8); __sbss_end = .; } > mcb_ddr2_S0_AXI_BASEADDR .tdata : { __tdata_start = .; *(.tdata) *(.tdata.*) *(.gnu.linkonce.td.*) __tdata_end = .; } > mcb_ddr2_S0_AXI_BASEADDR .tbss : { __tbss_start = .; *(.tbss) *(.tbss.*) *(.gnu.linkonce.tb.*) __tbss_end = .; } > mcb_ddr2_S0_AXI_BASEADDR .bss (NOLOAD) : { . = ALIGN(4); __bss_start = .; *(.bss) *(.bss.*) *(.gnu.linkonce.b.*) *(COMMON) . = ALIGN(4); __bss_end = .; } > mcb_ddr2_S0_AXI_BASEADDR _SDA_BASE_ = __sdata_start + ((__sbss_end - __sdata_start) / 2 ); _SDA2_BASE_ = __sdata2_start + ((__sbss2_end - __sdata2_start) / 2 ); /* Generate Stack and Heap definitions */ .heap (NOLOAD) : { . = ALIGN(8); _heap = .; _heap_start = .; . += _HEAP_SIZE; _heap_end = .; } > mcb_ddr2_S0_AXI_BASEADDR .stack (NOLOAD) : { _stack_end = .; . += _STACK_SIZE; . = ALIGN(8); _stack = .; __stack = _stack; } > mcb_ddr2_S0_AXI_BASEADDR _end = .; } I have not modified any files given in the demo. Can someone please help me figure out what to do so that the project compiles and can be programmed on my Atlys board? Thanks
  21. Hello, noob here I just started a project for my university BEng and is based on the chipKit WiFire provided by my supervisor. So far, i felt in love wth MPIDE because is so easy to use and it has all ready for me with 1 exception. The Flowcloud library. For the first 2 months and so I just figured out how to use MPIDE because the boards were from flowcloud so the USB-to-serial cable didn't work so I burned the Bootloader with Digilent's firmware. But now, I lost the Flowcloud app from the PIC chip that my project depends on so much because is required to use a cloud service. Anyhow, my request is: Can someone please tell me how to add the Flowcloud libraries and example codes/functions to work with MPIDE? I really hate MPLAB X because is so complicated and has no examples. Thank you in advance. P.S. I already talked in Flowcloud developer forum about this issue but they told me this is Digilent/chipkit's domain to integrate flowcloud/MPLAB Harmony libraries with MPIDE.
  22. Currently using the SDK with Python on Windows, I took time to compare the Waveform software and the SDK. Everything possible on the first is possible on the second one. Almost everything. I couldn't find a way to start the device (Analog Discovery) with another configuration. I tried to disable the Scope and the AWG, then to ask the maximum buffer size, but I always get 4096. Is it hidden in the dwf.h, dwf.lib or dwf.dll ? Any advice is welcome. Thanks. From the help : Configurations: Select the configuration you want to use for the selected device. The configurations have different device buffer-memory distributions for the instruments and other capabilities, like number of pins or channels. From the Wiki : Default Pattern Generator buffer size is 1kSamples/channel. The WaveForms Device Manager (WaveForms Main Window/Device/Manager) provides alternate FPGA configuration files, with different resources allocation. With no memory allocated to the Scope and AWG, the Pattern Generator buffer size can be chosen to be 16kSamples/channel.