• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About bnusbick

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

656 profile views
  1. bnusbick

    Newbie Programming 3 Questions

    By the way, I am using Papilio Loader 2.8.
  2. bnusbick

    Newbie Programming 3 Questions

    Hi Gregg, I don't have the Pro, but do have the Papilio One 250 and Papilio Duo. I use papilio-loader-gui to program them in Linux. In the lower part of the menu, it has the header 'Operations'. I currently have 'Scan', 'Erase', 'Write to', and 'Verify' checked. Underneath 'Write to' there is a drop down menu. I select 'FPGA' for temporary changes, and 'SPI Flash' if I want it to retain the changes after a power cycle.
  3. Hi, I scanned the forum and saw the following thread: which has a link to the following: which says Model No.: YSD-439AY2B-35. I can't guarantee this is the part number, but it has 8 leads on each side, which matches my logicstart megawing.
  4. I entered the following: and it took me there.
  5. bnusbick

    SUMP Logic analyzer not responding

    Try making channel 2 always high and see if OLS still stops working. Blake
  6. bnusbick

    Wishbone version of the Sump Blaze Logic Analyzer

    Both Jawi's OLS client and the one that comes with Designlab 1.07 and 1.08 seem to have the same problem for me.
  7. bnusbick

    Wishbone version of the Sump Blaze Logic Analyzer

    Jack, When I replace the following in result = String.format( "comm:%s;baudrate=%d;bitsperchar=8;parity=none;stopbits=1;flowcontrol=xon_xoff", with: result = String.format( "comm:%s;baudrate=%d;bitsperchar=8;parity=none;stopbits=1;flowcontrol=off", it no longer hangs when I send the test pattern, or when I make channels 0,1, and 4 high on the Papilio One 250K OLS client. Having a logic analyzer hang when it receives 0x13 during data acquistion is very undesirable to me. Blake
  8. bnusbick

    Wishbone version of the Sump Blaze Logic Analyzer

    Hi Jack, I was able to debug the OLS application in Eclipse. When it was hanging, the host was receiving all 1024 characters, but was hanging when the host was in the loop sending CMD_RST five times. It was actually hanging the second time it sent the CMD_RST. When I modified the source so it would only send CMD_RST once, it hung on closing the port (it does this after every data acquisition). Since this seemed to be a driver issue below OLS, I went back to trying to figure out why it hangs when I send a certain sequence. I was able to isolate it the value 0x13, which is the flow control character. If I take the Papilio 250 with the standard OLS client and short channels 0, 1, and 4 to 3.3 volts, it hangs the exact same way (I am only using Channel group 0). I would think the solution would be to get both sides to ignore flow control. Do you have any thoughts on how to achieve this? I am running on Linux, so I don't know if it would display the same behavior on Windows. Blake
  9. bnusbick

    Wishbone version of the Sump Blaze Logic Analyzer

    Jack, When I use the attached test program, if I modify SendIfReady() so it sends a test pattern, the capture completes successfully if I mask out bit 4, but if I don't mask bit 4 out, the capture doesn't complete until I upload new code, at which point it completes and displays the bit 4 value correctly. It is as if it is hanging draw channel-4. I don't see how the value of the data should affect whether the capture completes. I am pretty sure 1024 bytes is the correct amount to send, since if I send less than that with bit 4 masked, the capture won't complete until I upload new code. What would be required to debug the Java LogicSniffer Client program to see if it is in fact receiving all the data? Is there a way I can monitor the serial line to see if it is actually sending all the data? To get it to hang, just modify the following line: Serial.write(test_val++ & 0xef); to: Serial.write(test_val++ & 0xff); I have configured the Logic Sniffer as follows: Connection: Papilio DUO - Wishbone Memory Acquisition: Sampling Rate 5.000 kHz, Channel Groups 0, Recording size 1.00 kB Blake OLS_Client.ino
  10. bnusbick

    Wishbone version of the Sump Blaze Logic Analyzer

    Never mind. Looking at the schematic, I see that only Arduino 0-13 are assigned. When I switch to using 12 and 13, I see the toggles.
  11. bnusbick

    Wishbone version of the Sump Blaze Logic Analyzer

    Jack, When I configure Zpuino GPIOs 14 and 15 as output and try to toggle them, I see no output in OLS_Client.ino. (When I modified the timer example to do the same thing, I did see the GPIOs toggle.) When I looked at the ucf file for the logic analyzer, it just had the 32 logic analyzer inputs and tx and rx. if I want to have additional GPIOs for use by Zpuino, do I need to modify the VHDL code for the wishbone logic analyzer? I am guessing the vanilla Zpuino defines all the GPIOs for use by Zpuino, but the Zpuino used by the logic analyzer takes some of this capability away. Blake
  12. bnusbick

    Wishbone version of the Sump Blaze Logic Analyzer

    Hi Jack, It depends what you mean by getting it to work. I won't list all the tool issues I have that cause ISE to hang when launched from DesignLab, because I seem to have found ways to get around them. Where I stand now: 1) When I regenerate the bit file, it seems to be binary equivalent to the one that in the .zip file, which is encouraging. 2) The capture completes when I use the bit file and choose WB anything less than 256KB memory in the logic analyzer menu. However, when a feed a known frequency such as 100 KHz in, it thinks it is 66 KHz (at least in one attempt). When I load the regular logic analyzer bit file and choose Duo 64K, it correctly sees the frequency as 100 KHz. I am now going to look into the discrepancy. My plan is to add two GPIOs to the arduino sketch and toggle out all the values receive from the serial port, send to the serial port, and read from the wishbone bus out the two GPIOs in SPI fashion. Once I understand how the logic analyzer protocol works, I will start digging into the VHDL code. I will use my Papilio One in logic analyzer mode to view the GPIO toggles. Blake
  13. bnusbick

    Wishbone version of the Sump Blaze Logic Analyzer

    Jack, Thanks for the quick reply. Before reading your reply, I changed the top level to BENCHY_sa_SumpBlaze_LogicAnalyzer32 and it successfully created the programming file. Blake
  14. bnusbick

    Wishbone version of the Sump Blaze Logic Analyzer

    Hi Jack, When I tried to generate a programming file after setting wb_core as top module (which I think is what you suggested in the Back to Basics thread), it gets the following error when running the map: IO Utilization: Number of bonded IOBs: 192 out of 102 188% (OVERMAPPED) Is there something additional I need to do? Blake
  15. bnusbick

    Back to Basics

    Thomas, Thank you for the suggestions. I will look into them. Jack, Thank you for showing me how to build the bit files. When I do this, I get the following errors: Parsing architecture <behavioral> of entity <benchy_wb_sumpblaze_logicanalyzer32>. ERROR:HDLCompiler:1314 - "/home/bn/sandbox/DesignLab-1.0.7/libraries/Wishbone_Sump_LA/BENCHY_wb_SumpBlaze_LogicAnalyzer32.vhd" Line 143: Formal port/generic <run> is not declared in <core> ERROR:HDLCompiler:432 - "/home/bn/sandbox/DesignLab-1.0.7/libraries/Wishbone_Sump_LA/BENCHY_wb_SumpBlaze_LogicAnalyzer32.vhd" Line 129: Formal <exttriggerin> has no actual or default value. INFO:HDLCompiler:1408 - "/home/bn/sandbox/DesignLab-1.0.7/libraries/Benchy/core.vhd" Line 55. exttriggerin is declared here ERROR:HDLCompiler:854 - "/home/bn/sandbox/DesignLab-1.0.7/libraries/Wishbone_Sump_LA/BENCHY_wb_SumpBlaze_LogicAnalyzer32.vhd" Line 49: Unit <behavioral> ignored due to previous errors. VHDL file /home/bn/sandbox/DesignLab-1.0.7/libraries/Wishbone_Sump_LA/BENCHY_wb_SumpBlaze_LogicAnalyzer32.vhd ignored due to errors As Thomas correctly points out, I will never get the hang of this until I put in the time to truly understand ISE, VHDL, and what is necessary to map this to the Papilio boards, so I will try to resolve these errors by myself. However, as Martin points, out, there are lots of very bright people who are not willing to go through all this just to see what FPGAs are all about. Blake