Advanced Search

On Xilinx you can edit the .ucf file and add the "PULLDOWN" constraint 
but the I/O pins will float during powerup/configuration.

For 50 pin cards, it's much easier to just reverse the pullup resistors
and the GPIO will be guaranteed to be low at all times (and with a known
pulldown resistance)
 

low-blip wrote:

Did you figure it out? I want to use a Rust library in my VCP, but I only know how to install it as a package in a virtual environment.
 

Oh gosh, I can't remember! It's been so long since I worked on that project! I’m definitely using a venv, but I'm not sure I was able to switch the Python interpreter.

I was looking at upgrading my J1900 brix to a brix with an i7-5775 and 16gr of ram. Is this a fool’s errand or will this help future proof my system?

ps I snagged a BRIX with a i7-5775 for a killer deal so it’s on its way. 

What do you mean after configuration?
After loading firmware from flash memory?
When you powering fpga the firmware loads almost immediately...
How to enable xilinx weak internal pulldowns?

Update your subroutines folder and add the var file parameters per the instructions on the splash page. Will fix your issue. Use the sim config folder for reference.

Thank you very much. I will look at your guide.

tommylight wrote:

3 Probably because QtDragon does not use the same enable pin as GmoccaPy, although if that is the case, i would really insist on fixing that in QtDragon.
Can you upload config files for both GUI's?
 

hattest Du schon Zeit mal einen Blick auf meine Konfiguration zu werfen ?

Have you had time to take a look at my configuration ?

 

To invert a GPIO input, you use the inverted pin, for example:

hm2_7i95.0.gpio.054.in_not

thank you,

you are right, i think there is already a driver available for my vfd, after some googling around i found this,
github.com/araisrobo/linuxcnc/tree/maste.../user_comps/vfdb_vfd

linuxcnc.org/docs/2.7/html/man/man1/vfdb_vfd.1.html

In the lspci command:

lspci | grep -i eth

The | is a vertical bar character (pipe) not an uppercase i
 

After the series of errors I decided to update. But I guess I've had this kernel before. During the update the system showed some errors... I'll try to investigate tomorrow.

Hey,
are the probing parameters supposed to be reset after every pc restart or should they stay in the .var file.

For some reason after a pc restart they always revert to very old settings that i set long time ago.

Bst regards

Nils

Update the kernel to at least 6.8.n, preferably 6.12.n.

I wonder, why was the kernel not updated for the 2.9.4 ISO????
6.1.n kernel has huge latency and networking issues that are frankly getting to damn tiresome to read about them daily for nearly two years.
I have 6.8.n and 6.10.n on laptops without any issues.

Thanks for joining. Here's what it showed.

moriseiki@debian:~$ sudo chrt -f 99 ping -i .001 -q -c 60000 10.10.10.10
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.

--- 10.10.10.10 ping statistics ---
60000 packets transmitted, 60000 received, 0% packet loss, time 59999ms
rtt min/avg/max/mdev = 0.065/0.074/0.241/0.007 ms
moriseiki@debian:~$ lspci I grep -i eth
Usage: lspci [<switches>]

Basic display modes:
-mm        Produce machine-readable output (single -m for an obsolete format)
-t        Show bus tree

Display options:
-v        Be verbose (-vv or -vvv for higher verbosity)
-k        Show kernel drivers handling each device
-x        Show hex-dump of the standard part of the config space
-xxx        Show hex-dump of the whole config space (dangerous; root only)
-xxxx        Show hex-dump of the 4096-byte extended config space (root only)
-b        Bus-centric view (addresses and IRQ's as seen by the bus)
-D        Always show domain numbers
-P        Display bridge path in addition to bus and device number
-PP        Display bus path in addition to bus and device number

Resolving of device ID's to names:
-n        Show numeric ID's
-nn        Show both textual and numeric ID's (names & numbers)
-q        Query the PCI ID database for unknown ID's via DNS
-qq        As above, but re-query locally cached entries
-Q        Query the PCI ID database for all ID's via DNS

Selection of devices:
-s [[<domain>]:]<bus>]:][<slot>][.[<func>    Show only devices in selected slots
-d [<vendor>]:[<device>][:<class>]        Show only devices with specified ID's

Other options:
-i <file>    Use specified ID database instead of eth
-p <file>    Look up kernel modules in a given file instead of default modules.pcimap
-M        Enable `bus mapping' mode (dangerous; root only)

PCI access options:
-A <method>    Use the specified PCI access method (see `-A help' for a list)
-O <par>=<val>    Set PCI access parameter (see `-O help' for a list)
-G        Enable PCI access debugging
-H <mode>    Use direct hardware access (<mode> = 1 or 2)
-F <file>    Read PCI configuration dump from a given file