mor.paul

Newcomers
  • Content Count

    19
  • Joined

  • Last visited

About mor.paul

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @xc6lx45, @zygot, and all Thank you for your input. As I mentioned earlier, I'm limited in time on this project. I have many things to do besides collecting the data. I managed to borrow a Tektronix TDS 3034 scope and this is much better than the Rigol 1104 I was using. I have stopped looking for an alternative ADC method, I stopped working on the Eclypse z7. Thanks for all the input. I'll up date the results from this project as I get some real data. Paul
  2. As I mentioned earlier, I was unable to the connect PC directly to the Eclypse board a single ethernet cable. Without a router, I used a crossover cable and the following cmd lines. Computer: sudo ifconfig enp3s0 192.168.1.1 netmask 255.255.255.0 up Eclypse: sudo ip a add 192.168.1.100/255.255.255.0 dev eth0 In Xilinx SDK the Linux TCF agent is now working. I'm not sure a cross-over cable is required, but it was recommended when I googled the connection method. Special thanks to my friend at work that showed me how to configure the computers this way. Paul ps. I am still wondering why the demo programs compile, download the board and start running. The bare metal program gets stuck going out of main(), some time after the first function is called. The linux demo is also having a problem, the program is doing something I can not figure out what it is doing?
  3. @lonel, Thank you for the reply to my message. Paul
  4. Also, still having problems getting Xilinx SDK to communicate with linux TCF agent. One of my console reported tcfchan#4 was closed after stopping a process.
  5. I went looking for my boss to ask about a scope. I think he went on holiday... maybe next week? Summer is a weird time to work in Europe. Everyone is on holiday whenever you need something. On a brighter note, I figured out my problems with the compile errors about incorrect header files... I missed the part about copying the image file along with the other files in the zip to a directory on my system. I figured this out when I install V.1 of the image file on my SD card. I guess those files were the ones I needed to reference for the SYSROOT environment in SDK. I no longer get build errors. Now the problem is the bare metal and linux program don't do anything yet. I'll start another thread when I have a question I can't figure out. I normally process my data in MatLab or excel.
  6. @zygot, Thanks for the reply. Yes, I am a little stubborn. I am also in a box because I don't have access to any other equipment. If I can get 128K samples this would capture what I'm looking for. My sample deforms plastically, I'm only concerned about the force signal where the deformation occurs in the first 0.5 ms. What happens to the voltage on the piezo transducer isn't as important to me. Coming in as a visiting researcher has its' positives and negatives. The plus side is I am free to do what ever I want. The minus side is there isn't a lot of money to spend. Also, knowing where find the right people, instruments and where to get things done is some times difficult and time consuming. You are right, I am wasting my time now and I should find a 4 channel oscilloscope. I need to work on my next challenge soldering micro wires to some very small magnetic field sensors and then interfacing them to an analogue input channel. Paul
  7. Yes, I was wondering about this earlier today. The Digilent documentation is very foggy about this. Is there anyone from Digilent that can clarify this for me?? What to type in to reference the image file would be appreciated. Thanks, Paul
  8. Hi, I had this posted in the intro section but I decided to move this question over here. I'm currently working on the SDK connection problem and SDK compiling errors below. This afternoon working on errors related to include paths and errors generated from the header files. I basically think my Xilinx SDK build paths / include files in the project folders are not set right. If I knew what directory the right files were in I'm pretty sure I could the build settings and compile. Here are the files that are having problems: /usr/include/bits/floatn.h:75:70: error: unknown machine mode ‘__TC__’ /usr/include/bits/floatn.h:87:9: error: ‘__float128’ does not name a type; /usr/include/stdlib.h:152:8: error: ‘_Float128’ does not name a type /usr/include/stdlib.h:245:4: error: ‘_Float128’ has not been declared /usr/include/stdlib.h:330:8: error: ‘_Float128’ does not name a type src/zmodlib/ZmodDAC1411/subdir.mk:18: recipe for target 'src/zmodlib/ZmodDAC1411/zmoddac1411.o' You wouldn't think these header files could cause any heartache Time to head out. Thanks, Paul
  9. Thanks, for the input on the scope. I spent this morning working on a monthly report and this afternoon working on errors related to include paths and errors generated from the header files. I basically think my Xilinx SDK paths in the project folders are not set right. If I knew what directory the right files were in I'm pretty sure I could the build settings and compile. Here are the files that are having problems: /usr/include/bits/floatn.h:75:70: error: unknown machine mode ‘__TC__’ /usr/include/bits/floatn.h:87:9: error: ‘__float128’ does not name a type; /usr/include/stdlib.h:152:8: error: ‘_Float128’ does not name a type /usr/include/stdlib.h:245:4: error: ‘_Float128’ has not been declared /usr/include/stdlib.h:330:8: error: ‘_Float128’ does not name a type src/zmodlib/ZmodDAC1411/subdir.mk:18: recipe for target 'src/zmodlib/ZmodDAC1411/zmoddac1411.o' You wouldn't think these header files could cause any heartache Time to head out. Thanks, Paul
  10. Hi Ionel, Thanks for the reply. I am confused about your question. Are you referring to an ethernet cable or a USB cable? Nothing in the instructions I attached and I was following mention an ether net cable. In any event I am connected to the board on the connector referred to the "PROG" and on my case for the board the port is called JTAG & UART. The USB cable is connected directly to the PC USB port. I do wonder if the ethernet port can be used for an ethernet connection in the future. Is there any documentation how to use the ethernet port? Thanks, Paul
  11. @zygot Yeah, I was reading through your posts from the last couple of days. Why would one sell a board that can only handle 3FFF -1 pieces of data. I'm a little confused why this is so.... doesn't the Z7 board have enough memory? I was hoping there would be a way to do DMA 's to move the data out of the capture buffer. Anyways, I've got two more months on my research contract at the Czech Academy of Science. I might need to borrow some equipment from another lab here. Afterwards, I plan on taking a three month vacation and then retiring. Paul
  12. @zygot Thanks for the warning on the repository. I guess I assumed using the cmd for cloning the demos was up to date. I just noticed in the linux demo the program writes to a file, without making a directory or using a fopen() to begin writing to it. I also have not noticed a fclose() for it. I was thought most people open a file, write to it and then close it. I created a directory with a file that the demo plans on writing to. Anyways, I got a good laugh at your observation about git hub. Paul
  13. FYI, I started with windows. I went back to it this morning, but I have not figured out how to recursively reload the github projects. I can only handle one fire at a time. I guess I'll die with ubuntu. Paul
  14. Hi, I took some pictures out of some of my activity reports. Sorry if the quality isn't the best I can do. I usually work in windows, but I'm currently in ubuntu. The system sends a 1000V pulse to the piezo electric transducer. While going to 1000 v the transducer expands 150 microns, after the pulse the system discharges to 0V while contracting. I plan on putting a sample in there that deforms at low forces, while deforming some boundaries move and the magnetic field orientation from the sample changes by 90 degrees. I just need to read the voltage to the piezo actuator, the force transducer and a couple of magneto resistive sensors with the electrical output should change when the magnetic field moves by. Paul
  15. @zygot and @[email protected], Thank you for spending the time to explain some of the terminology. When I have some time to relax I reread your emails again. At the moment I'm thinking about the SDK. I have a mechanical test instrument that works when connected to a scope. My problem is that the number of samples and bits is not quite good enough for me. For me it looked like the Eclypse system would fit the bill, it has 2 ADC boards at 100 MSPs. Based on what I see with the ADC demos is they don't work out of the box. I have loaded and reloaded things, checking my work along the way. Today when I switched to the ADC linux demo, using projects reloaded from the repository I end up with 7 errors and one include path not found. The bare metal demo doesn't seem to have build errors, but when I run it I can not get any output.... It would help if I had a debugger working. I have attached a screen print of the errors. In the next reply I'll post how my system works attached to the scope. Thanks, Paul