Search Results (Searched for: )
- nartburg
- nartburg
27 Jun 2024 16:59
mesa 7i96s failed to parse Module Descriptor 7 was created by nartburg
mesa 7i96s failed to parse Module Descriptor 7
Category: Driver Boards
Dear Forum,
I just connected a new Mesa 7i09s confugured the network -- got contact with the card -- executed Pncconf Wizard -- tryed to execute Linuxcnc and got:
..
..
hm2-eth:discovered 7I96S
hm2/hm2_7i96s.0: Low Level init 0.15
board fails HM2 registration
..
..
..
DEBUG FILE INFO:
Note: Using POSIX realtime
hm2/hm2_7i96s.0: num_sserials references 2 instances, but only 1 are available, not loading driver
hm2/hm2:7i96s.0: failed to parse Module Descriptor 7
hm2_eth: rtapi_app_main: Invalid argument(-22)
./ww1.hal9: waitpid failed /usr/bin/rtapi_app hm_eth
..
..
..
please advise
with kind regards
I just connected a new Mesa 7i09s confugured the network -- got contact with the card -- executed Pncconf Wizard -- tryed to execute Linuxcnc and got:
..
..
hm2-eth:discovered 7I96S
hm2/hm2_7i96s.0: Low Level init 0.15
board fails HM2 registration
..
..
..
DEBUG FILE INFO:
Note: Using POSIX realtime
hm2/hm2_7i96s.0: num_sserials references 2 instances, but only 1 are available, not loading driver
hm2/hm2:7i96s.0: failed to parse Module Descriptor 7
hm2_eth: rtapi_app_main: Invalid argument(-22)
./ww1.hal9: waitpid failed /usr/bin/rtapi_app hm_eth
..
..
..
please advise
with kind regards
- B.Reilly01
- B.Reilly01
27 Jun 2024 16:22 - 27 Jun 2024 16:26
Replied by B.Reilly01 on topic Spindle/router won't run
Spindle/router won't run
Category: Installing LinuxCNC
Could you post your HAL and INI files?
EDIT: I see now you're using a controller I'm unfamiliar with, but hopefully can still help. What VFD are you running? Which Unity controller is it?
EDIT: I see now you're using a controller I'm unfamiliar with, but hopefully can still help. What VFD are you running? Which Unity controller is it?
- jimmyrig
- jimmyrig
27 Jun 2024 15:26
Replied by jimmyrig on topic when an inch isn't
when an inch isn't
Category: Installing LinuxCNC
A quick way to get a rough idea of the problem
Jog your machine to one side
Using a tape measure from your spindle/head/whatever put a block a known distance near the end of your travel.
Tell the machine to go that location.
If it way overshoots or undershoots you have a "steps per inch" problem. Change your steps accordingly. 1.016*24in = 24.38in ...... This would be very noticable with the above method.
If it's almost spot on. E.g. 24.016 Then it's probably a backlash or squaring issue. Could also be a gearing issue if your are using a rack and pinion with that low of a step count.
Jog your machine to one side
Using a tape measure from your spindle/head/whatever put a block a known distance near the end of your travel.
Tell the machine to go that location.
If it way overshoots or undershoots you have a "steps per inch" problem. Change your steps accordingly. 1.016*24in = 24.38in ...... This would be very noticable with the above method.
If it's almost spot on. E.g. 24.016 Then it's probably a backlash or squaring issue. Could also be a gearing issue if your are using a rack and pinion with that low of a step count.
- scotth
- scotth
27 Jun 2024 15:19
Replied by scotth on topic when an inch isn't
when an inch isn't
Category: Installing LinuxCNC
Remember that the distance between London and Paris is the same whether you represent it in kilometers or miles. The only difference is the way you slice it.
- tommylight
27 Jun 2024 15:10
Replied by tommylight on topic Ubuntu install
Ubuntu install
Category: Installing LinuxCNC
@cncproject2024
NO Double posting!!!
Just wasted 7 minutes to fix this mess as you used the same tittle for both topics.
NO Double posting!!!
Just wasted 7 minutes to fix this mess as you used the same tittle for both topics.
- scotth
- scotth
27 Jun 2024 14:54
Replied by scotth on topic when an inch isn't
when an inch isn't
Category: Installing LinuxCNC
Look at geometry and lost motion.
- Cant do this anymore bye all
27 Jun 2024 14:36
Replied by Cant do this anymore bye all on topic LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)
LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)
Category: Computers and Hardware
I can do that in the morning, it’s just approaching half past midnight Down Under.
What I’ll do I’ll get everything together and put it on my github, schematics for my boards and everything I have on the FPGA, everything is a bit scattered ATM.
You realise if theory that the Mesa 7c81 and 7i90 could run the Spartan6 version of the rio firmware ? Both have SPI interfaces and the 7i90 when it was last in stock was about 50 USD plus delivery.
I’ve also got one the colorlight RV901T boards, spartan6 based I could test as well.
Seriously I’ve been struggling a bit with “chasing the black dog” recently but this has given me something to get my teeth into, once again many many thanks.
What I’ll do I’ll get everything together and put it on my github, schematics for my boards and everything I have on the FPGA, everything is a bit scattered ATM.
You realise if theory that the Mesa 7c81 and 7i90 could run the Spartan6 version of the rio firmware ? Both have SPI interfaces and the 7i90 when it was last in stock was about 50 USD plus delivery.
I’ve also got one the colorlight RV901T boards, spartan6 based I could test as well.
Seriously I’ve been struggling a bit with “chasing the black dog” recently but this has given me something to get my teeth into, once again many many thanks.
- chrisfischer
- chrisfischer
27 Jun 2024 14:33
Replied by chrisfischer on topic Anyone figured out how to get Trinamic's TMC5160 drivers working with LinuxCNC?
Anyone figured out how to get Trinamic's TMC5160 drivers working with LinuxCNC?
Category: Driver Boards
I'm looking to see if anyone has used the trinamic drivers for stall guard to detect skipped steps during the cut but also to do sensorless homing. I'm surprised I don't see anyone mention this.
- Lcvette
27 Jun 2024 14:23
Replied by Lcvette on topic ProbeBasic backplot issue?
ProbeBasic backplot issue?
Category: QtPyVCP
i can verify, taking a look! thanks for the report!Hello,
when I start the probe_basic_lathe simulation and change the view, I get an error in the file vtk_backplot.py.
I have installed the latest LCNC 2.9 ISO.
- meister
- meister
27 Jun 2024 14:09 - 27 Jun 2024 14:10
Replied by meister on topic LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)
LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)
Category: Computers and Hardware
if you can send me more info's of this board (cant find any).
then i can complete the board-config (clock pin and crystal-speed).
and if you have the pinout's of your interface-board, i can build a simple config
with some stepper outputs and digital-IO's + SPI interface
then i can complete the board-config (clock pin and crystal-speed).
and if you have the pinout's of your interface-board, i can build a simple config
with some stepper outputs and digital-IO's + SPI interface
- Cant do this anymore bye all
27 Jun 2024 13:16
Replied by Cant do this anymore bye all on topic Ubuntu install
Ubuntu install
Category: Installing LinuxCNC
You can download the latest Linucnc image, write to a USB stick and then boot from it and run a Live session without having to install anything.
Later you can install it to the laptop.
Best way to install is from the Linuxcnc image written to a USB stick. When booting from it the opening menu will give you the option of running a Live session or installing Linuxcnc (this will install Debian Bookworm OS all setup for Linuxcnc), you'll find the installer is the Debian Bookworm installer. After the installation has run its course you'll have brand new installation of Debian Bookworm with the required kernel & Linuxcnc ready to go.
Whilst you can use one of the install ISO from Debian and do a plain vanilla install, then install Linuxcnc it's not the easiest route compared to the above mentioned method.
But. Here comes the advanced portion
Now if you are have some free space on the Ubuntu partition, say at least 16GB and can shrink the partition with gparted you can install Linuxcnc along side Ubuntu. To begin with I wouldn't install Debian from a Debian disk, I'd install it from the usb stick you have written the Linuxcnc image to..
The easiest way to shrink a partition is to use www.system-rescue.org/
Boot after you have written the image to s USB stick, type startx to start the gui, then run gparted to shrink the Ubuntu partition if there is the room. GParted is pretty intuitive and I've never had a failure, but it may be best to backup at least your home directory first if there is anything "mission critical".
Tho as has been said before Laptops aren't the best, not really recommended actually, for machine control. But to get an idea of how it works and even testing gcode via one of the simulation configs it will be fine.
Later you can install it to the laptop.
Best way to install is from the Linuxcnc image written to a USB stick. When booting from it the opening menu will give you the option of running a Live session or installing Linuxcnc (this will install Debian Bookworm OS all setup for Linuxcnc), you'll find the installer is the Debian Bookworm installer. After the installation has run its course you'll have brand new installation of Debian Bookworm with the required kernel & Linuxcnc ready to go.
Whilst you can use one of the install ISO from Debian and do a plain vanilla install, then install Linuxcnc it's not the easiest route compared to the above mentioned method.
But. Here comes the advanced portion
Now if you are have some free space on the Ubuntu partition, say at least 16GB and can shrink the partition with gparted you can install Linuxcnc along side Ubuntu. To begin with I wouldn't install Debian from a Debian disk, I'd install it from the usb stick you have written the Linuxcnc image to..
The easiest way to shrink a partition is to use www.system-rescue.org/
Boot after you have written the image to s USB stick, type startx to start the gui, then run gparted to shrink the Ubuntu partition if there is the room. GParted is pretty intuitive and I've never had a failure, but it may be best to backup at least your home directory first if there is anything "mission critical".
Tho as has been said before Laptops aren't the best, not really recommended actually, for machine control. But to get an idea of how it works and even testing gcode via one of the simulation configs it will be fine.
- meister
- meister
27 Jun 2024 13:09
Replied by meister on topic LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)
LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)
Category: Computers and Hardware
you are right, i see, but no panic 
github.com/multigcs/riocore/blob/main/ri...boards/Spartan6.json
github.com/multigcs/riocore/blob/main/ri...an6/config-test.json

github.com/multigcs/riocore/blob/main/ri...boards/Spartan6.json
github.com/multigcs/riocore/blob/main/ri...an6/config-test.json
#:/usr/src/riocore$ PYTHONPATH=. python3 bin/rio-generator riocore/configs/Spartan6/config-test.json
loading: riocore/configs/Spartan6/config-test.json
loading board setup: Spartan6
writing gateware to: Output/Spartan6/Gateware
!!! gateware changed: needs to flash |||
loading toolchain ise
writing linuxcnc files to: Output/Spartan6/LinuxCNC
#:/usr/src/riocore/Output/Spartan6/Gateware$ clear ; make clean all
rm -rf rio.ngc rio.ngd rio.ncd parout.ncd rio.bit
cat debouncer.v toggle.v pwmmod.v rio.v > rio-modules.v
echo 'run -ifn rio-modules.v -ifmt Verilog -ofn rio.ngc -top rio -p xc6slx9-3tqg144 -opt_mode Speed -opt_level 1' | xst
Release 14.7 - xst P.20131013 (lin64)
Copyright (c) 1995-2013 Xilinx, Inc. All rights reserved.
-->
TABLE OF CONTENTS
1) Synthesis Options Summary
2) HDL Parsing
3) HDL Elaboration
4) HDL Synthesis
4.1) HDL Synthesis Report
5) Advanced HDL Synthesis
5.1) Advanced HDL Synthesis Report
6) Low Level Synthesis
7) Partition Report
8) Design Summary
8.1) Primitive and Black Box Usage
8.2) Device utilization summary
8.3) Partition Resource Summary
8.4) Timing Report
8.4.1) Clock Information
8.4.2) Asynchronous Control Signals Information
8.4.3) Timing Summary
8.4.4) Timing Details
8.4.5) Cross Clock Domains Report
=========================================================================
* Synthesis Options Summary *
=========================================================================
---- Source Parameters
Input File Name : "rio-modules.v"
Input Format : Verilog
---- Target Parameters
Output File Name : "rio.ngc"
Target Device : xc6slx9-3tqg144
---- Source Options
Top Module Name : rio
---- General Options
Optimization Goal : Speed
Optimization Effort : 1
=========================================================================
=========================================================================
* HDL Parsing *
=========================================================================
Analyzing Verilog file "rio-modules.v" into library work
Parsing module <debouncer>.
Parsing module <toggle>.
Parsing module <pwmmod>.
Parsing module <rio>.
=========================================================================
* HDL Elaboration *
=========================================================================
Elaborating module <rio>.
WARNING:HDLCompiler:872 - "rio-modules.v" Line 94: Using initial value of ESTOP since it is never assigned
WARNING:HDLCompiler:1127 - "rio-modules.v" Line 98: Assignment to ERROR ignored, since the identifier is never used
WARNING:HDLCompiler:1127 - "rio-modules.v" Line 121: Assignment to tx_data ignored, since the identifier is never used
WARNING:HDLCompiler:634 - "rio-modules.v" Line 103: Net <rx_data[7]> does not have a driver.
=========================================================================
* HDL Synthesis *
=========================================================================
Synthesizing Unit <rio>.
Related source file is "/usr/src/riocore/Output/Spartan6/Gateware/rio-modules.v".
BUFFER_SIZE = 16'b0000000000101000
WARNING:Xst:647 - Input <sysclk_in> is never used. This port will be preserved and left unconnected if it belongs to a top-level block or it belongs to a sub-block and the hierarchy of this sub-block is preserved.
WARNING:Xst:653 - Signal <rx_data<7>> is used but never assigned. This sourceless signal will be automatically connected to value GND.
Summary:
no macro.
Unit <rio> synthesized.
=========================================================================
HDL Synthesis Report
Found no macro
=========================================================================
=========================================================================
* Advanced HDL Synthesis *
=========================================================================
=========================================================================
Advanced HDL Synthesis Report
Found no macro
=========================================================================
=========================================================================
* Low Level Synthesis *
=========================================================================
Optimizing unit <rio> ...
Mapping all equations...
Building and optimizing final netlist ...
Found area constraint ratio of 100 (+ 0) on block rio, actual ratio is 0.
Final Macro Processing ...
=========================================================================
Final Register Report
Found no macro
=========================================================================
=========================================================================
* Partition Report *
=========================================================================
Partition Implementation Status
-------------------------------
No Partitions were found in this design.
-------------------------------
=========================================================================
* Design Summary *
=========================================================================
Top Level Output File Name : rio.ngc
Primitive and Black Box Usage:
------------------------------
# BELS : 1
# GND : 1
# IO Buffers : 1
# OBUF : 1
Device utilization summary:
---------------------------
Selected Device : 6slx9tqg144-3
Slice Logic Utilization:
Slice Logic Distribution:
Number of LUT Flip Flop pairs used: 0
Number with an unused Flip Flop: 0 out of 0
Number with an unused LUT: 0 out of 0
Number of fully used LUT-FF pairs: 0 out of 0
Number of unique control sets: 0
IO Utilization:
Number of IOs: 2
Number of bonded IOBs: 1 out of 102 0%
Specific Feature Utilization:
---------------------------
Partition Resource Summary:
---------------------------
No Partitions were found in this design.
---------------------------
=========================================================================
Timing Report
NOTE: THESE TIMING NUMBERS ARE ONLY A SYNTHESIS ESTIMATE.
FOR ACCURATE TIMING INFORMATION PLEASE REFER TO THE TRACE REPORT
GENERATED AFTER PLACE-and-ROUTE.
Clock Information:
------------------
No clock signals found in this design
Asynchronous Control Signals Information:
----------------------------------------
No asynchronous control signals found in this design
Timing Summary:
---------------
Speed Grade: -3
Minimum period: No path found
Minimum input arrival time before clock: No path found
Maximum output required time after clock: No path found
Maximum combinational path delay: No path found
Timing Details:
---------------
All values displayed in nanoseconds (ns)
=========================================================================
Cross Clock Domains Report:
--------------------------
=========================================================================
Total REAL time to Xst completion: 4.00 secs
Total CPU time to Xst completion: 3.96 secs
-->
Total memory usage is 361140 kilobytes
Number of errors : 0 ( 0 filtered)
Number of warnings : 6 ( 0 filtered)
Number of infos : 0 ( 0 filtered)
ngdbuild -p xc6slx9-3tqg144 -uc pins.ucf rio.ngc
Release 14.7 - ngdbuild P.20131013 (lin64)
Copyright (c) 1995-2013 Xilinx, Inc. All rights reserved.
Command Line: /data/opt/Xilinx/14.7/ISE_DS/ISE/bin/lin64/unwrapped/ngdbuild -p
xc6slx9-3tqg144 -uc pins.ucf rio.ngc
Reading NGO file "/usr/src/riocore/Output/Spartan6/Gateware/rio.ngc" ...
Gathering constraint information from source properties...
Done.
Annotating constraints to design from ucf file "pins.ucf" ...
Resolving constraint associations...
Checking Constraint Associations...
Done...
Checking expanded design ...
Partition Implementation Status
-------------------------------
No Partitions were found in this design.
-------------------------------
NGDBUILD Design Results Summary:
Number of errors: 0
Number of warnings: 0
Writing NGD file "rio.ngd" ...
Total REAL time to NGDBUILD completion: 2 sec
Total CPU time to NGDBUILD completion: 2 sec
Writing NGDBUILD log file "rio.bld"...
NGDBUILD done.
map -detail -pr b rio.ngd
Release 14.7 - Map P.20131013 (lin64)
Copyright (c) 1995-2013 Xilinx, Inc. All rights reserved.
Using target part "6slx9tqg144-3".
Mapping design into LUTs...
Writing file rio.ngm...
Running directed packing...
Running delay-based LUT packing...
Updating timing models...
INFO:Map:215 - The Interim Design Summary has been generated in the MAP Report
(.mrp).
Running timing-driven placement...
Total REAL time at the beginning of Placer: 3 secs
Total CPU time at the beginning of Placer: 3 secs
Phase 1.1 Initial Placement Analysis
Phase 1.1 Initial Placement Analysis (Checksum:1f2fb3a9) REAL time: 3 secs
Phase 2.7 Design Feasibility Check
Phase 2.7 Design Feasibility Check (Checksum:1f2fb3a9) REAL time: 3 secs
Phase 3.31 Local Placement Optimization
Phase 3.31 Local Placement Optimization (Checksum:1f2fb3a9) REAL time: 3 secs
Phase 4.2 Initial Placement for Architecture Specific Features
Phase 4.2 Initial Placement for Architecture Specific Features
(Checksum:1f2fb3a9) REAL time: 4 secs
Phase 5.36 Local Placement Optimization
Phase 5.36 Local Placement Optimization (Checksum:1f2fb3a9) REAL time: 4 secs
Phase 6.30 Global Clock Region Assignment
Phase 6.30 Global Clock Region Assignment (Checksum:1f2fb3a9) REAL time: 4 secs
Phase 7.3 Local Placement Optimization
Phase 7.3 Local Placement Optimization (Checksum:1f2fb3a9) REAL time: 4 secs
Phase 8.5 Local Placement Optimization
Phase 8.5 Local Placement Optimization (Checksum:1f2fb3a9) REAL time: 4 secs
Phase 9.8 Global Placement
Phase 9.8 Global Placement (Checksum:1f2fb3a9) REAL time: 4 secs
Phase 10.5 Local Placement Optimization
Phase 10.5 Local Placement Optimization (Checksum:1f2fb3a9) REAL time: 4 secs
Phase 11.18 Placement Optimization
Phase 11.18 Placement Optimization (Checksum:1f2fb3a9) REAL time: 4 secs
Phase 12.5 Local Placement Optimization
Phase 12.5 Local Placement Optimization (Checksum:1f2fb3a9) REAL time: 4 secs
Phase 13.34 Placement Validation
Phase 13.34 Placement Validation (Checksum:1f2fb3a9) REAL time: 4 secs
Total REAL time to Placer completion: 4 secs
Total CPU time to Placer completion: 3 secs
Running post-placement packing...
Writing output files...
Design Summary:
Number of errors: 0
Number of warnings: 0
Slice Logic Utilization:
Number of Slice Registers: 0 out of 11,440 0%
Number of Slice LUTs: 0 out of 5,720 0%
Slice Logic Distribution:
Number of occupied Slices: 0 out of 1,430 0%
Number of MUXCYs used: 0 out of 2,860 0%
Number of LUT Flip Flop pairs used: 0
IO Utilization:
Number of bonded IOBs: 2 out of 102 1%
Number of LOCed IOBs: 2 out of 2 100%
Specific Feature Utilization:
Number of RAMB16BWERs: 0 out of 32 0%
Number of RAMB8BWERs: 0 out of 64 0%
Number of BUFIO2/BUFIO2_2CLKs: 0 out of 32 0%
Number of BUFIO2FB/BUFIO2FB_2CLKs: 0 out of 32 0%
Number of BUFG/BUFGMUXs: 0 out of 16 0%
Number of DCM/DCM_CLKGENs: 0 out of 4 0%
Number of ILOGIC2/ISERDES2s: 0 out of 200 0%
Number of IODELAY2/IODRP2/IODRP2_MCBs: 0 out of 200 0%
Number of OLOGIC2/OSERDES2s: 0 out of 200 0%
Number of BSCANs: 0 out of 4 0%
Number of BUFHs: 0 out of 128 0%
Number of BUFPLLs: 0 out of 8 0%
Number of BUFPLL_MCBs: 0 out of 4 0%
Number of DSP48A1s: 0 out of 16 0%
Number of ICAPs: 0 out of 1 0%
Number of MCBs: 0 out of 2 0%
Number of PCILOGICSEs: 0 out of 2 0%
Number of PLL_ADVs: 0 out of 2 0%
Number of PMVs: 0 out of 1 0%
Number of STARTUPs: 0 out of 1 0%
Number of SUSPEND_SYNCs: 0 out of 1 0%
Average Fanout of Non-Clock Nets: 0.00
Peak Memory Usage: 650 MB
Total REAL time to MAP completion: 4 secs
Total CPU time to MAP completion: 4 secs
Mapping completed.
See MAP report file "rio.mrp" for details.
par -w rio.ncd parout.ncd rio.pcf
Release 14.7 - par P.20131013 (lin64)
Copyright (c) 1995-2013 Xilinx, Inc. All rights reserved.
Constraints file: rio.pcf.
Loading device for application Rf_Device from file '6slx9.nph' in environment /data/opt/Xilinx/14.7/ISE_DS/ISE/.
"rio" is an NCD, version 3.2, device xc6slx9, package tqg144, speed -3
Initializing temperature to 85.000 Celsius. (default - Range: 0.000 to 85.000 Celsius)
Initializing voltage to 1.140 Volts. (default - Range: 1.140 to 1.260 Volts)
INFO:Par:282 - No user timing constraints were detected or you have set the option to ignore timing constraints ("par
-x"). Place and Route will run in "Performance Evaluation Mode" to automatically improve the performance of all
internal clocks in this design. Because there are not defined timing requirements, a timing score will not be
reported in the PAR report in this mode. The PAR timing summary will list the performance achieved for each clock.
Note: For the fastest runtime, set the effort level to "std". For best performance, set the effort level to "high".
Device speed data version: "PRODUCTION 1.23 2013-10-13".
Device Utilization Summary:
Slice Logic Utilization:
Number of Slice Registers: 0 out of 11,440 0%
Number of Slice LUTs: 0 out of 5,720 0%
Slice Logic Distribution:
Number of occupied Slices: 0 out of 1,430 0%
Number of MUXCYs used: 0 out of 2,860 0%
Number of LUT Flip Flop pairs used: 0
IO Utilization:
Number of bonded IOBs: 2 out of 102 1%
Number of LOCed IOBs: 2 out of 2 100%
Specific Feature Utilization:
Number of RAMB16BWERs: 0 out of 32 0%
Number of RAMB8BWERs: 0 out of 64 0%
Number of BUFIO2/BUFIO2_2CLKs: 0 out of 32 0%
Number of BUFIO2FB/BUFIO2FB_2CLKs: 0 out of 32 0%
Number of BUFG/BUFGMUXs: 0 out of 16 0%
Number of DCM/DCM_CLKGENs: 0 out of 4 0%
Number of ILOGIC2/ISERDES2s: 0 out of 200 0%
Number of IODELAY2/IODRP2/IODRP2_MCBs: 0 out of 200 0%
Number of OLOGIC2/OSERDES2s: 0 out of 200 0%
Number of BSCANs: 0 out of 4 0%
Number of BUFHs: 0 out of 128 0%
Number of BUFPLLs: 0 out of 8 0%
Number of BUFPLL_MCBs: 0 out of 4 0%
Number of DSP48A1s: 0 out of 16 0%
Number of ICAPs: 0 out of 1 0%
Number of MCBs: 0 out of 2 0%
Number of PCILOGICSEs: 0 out of 2 0%
Number of PLL_ADVs: 0 out of 2 0%
Number of PMVs: 0 out of 1 0%
Number of STARTUPs: 0 out of 1 0%
Number of SUSPEND_SYNCs: 0 out of 1 0%
Overall effort level (-ol): Standard
Router effort level (-rl): High
Starting initial Timing Analysis. REAL time: 2 secs
Finished initial Timing Analysis. REAL time: 2 secs
WARNING:Par:288 - The signal sysclk_in_IBUF has no load. PAR will not attempt to route this signal.
Starting Router
Phase 1 : 1 unrouted; REAL time: 2 secs
Phase 2 : 1 unrouted; REAL time: 2 secs
Phase 3 : 0 unrouted; REAL time: 3 secs
Phase 4 : 0 unrouted; (Par is working to improve performance) REAL time: 3 secs
Updating file: parout.ncd with current fully routed design.
Phase 5 : 0 unrouted; (Par is working to improve performance) REAL time: 3 secs
Phase 6 : 0 unrouted; (Par is working to improve performance) REAL time: 3 secs
Phase 7 : 0 unrouted; (Par is working to improve performance) REAL time: 3 secs
Phase 8 : 0 unrouted; (Par is working to improve performance) REAL time: 3 secs
Phase 9 : 0 unrouted; (Par is working to improve performance) REAL time: 3 secs
Phase 10 : 0 unrouted; (Par is working to improve performance) REAL time: 3 secs
Total REAL time to Router completion: 3 secs
Total CPU time to Router completion: 3 secs
Partition Implementation Status
-------------------------------
No Partitions were found in this design.
-------------------------------
Generating "PAR" statistics.
INFO:Par:459 - The Clock Report is not displayed in the non timing-driven mode.
Timing Score: 0 (Setup: 0, Hold: 0)
Generating Pad Report.
All signals are completely routed.
WARNING:Par:283 - There are 1 loadless signals in this design. This design will cause Bitgen to issue DRC warnings.
Total REAL time to PAR completion: 3 secs
Total CPU time to PAR completion: 3 secs
Peak Memory Usage: 602 MB
Placer: Placement generated during map.
Routing: Completed - No errors found.
Number of error messages: 0
Number of warning messages: 3
Number of info messages: 2
Writing design to file parout.ncd
PAR done!
#bitgen -w -g StartUpClk:CClk -g CRC:Enable parout.ncd rio.bit rio.pcf
bitgen -w -g StartUpClk:jtagclk -g CRC:Enable parout.ncd rio.bit rio.pcf
Release 14.7 - Bitgen P.20131013 (lin64)
Copyright (c) 1995-2013 Xilinx, Inc. All rights reserved.
Loading device for application Rf_Device from file '6slx9.nph' in environment
/data/opt/Xilinx/14.7/ISE_DS/ISE/.
"rio" is an NCD, version 3.2, device xc6slx9, package tqg144, speed -3
Opened constraints file rio.pcf.
Thu Jun 27 15:03:00 2024
Running DRC.
DRC detected 0 errors and 0 warnings.
Creating bit map...
Saving bit stream in "rio.bit".
Bitstream generation is complete.
cp -v hash_new.txt hash_compiled.txt
'hash_new.txt' -> 'hash_compiled.txt'
- Cant do this anymore bye all
27 Jun 2024 12:59
Replied by Cant do this anymore bye all on topic LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)
LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)
Category: Computers and Hardware
Just had a quick look, seems vivado doesn't support Spartan6, so I guess I'll have to load everything into XISE and create ucf (pin file so suit), hopefully shouldn't be too much trouble. But that's tomorrow's task.
- B.Reilly01
- B.Reilly01
27 Jun 2024 12:57 - 27 Jun 2024 12:58
Replied by B.Reilly01 on topic G54 ON START UP
G54 ON START UP
Category: AXIS
Do you have G54 in the startup G-Code in the INI file? I also suspect since it's not zero'd yet, the machine is in G53 until it finds home - it doesn't actually know where it is for certain, so G54 isn't relevent yet. I may be reading your post incorrectly... Could you post your HAL and INI files? G54 goes here:
[RS274NGC]
RS274NGC_STARTUP_CODE = F10 S300 G20 G17 G40 G49 G54 G64 P0.001 G80 G90 G91.1 G92.1 G94 G97 G98
- B.Reilly01
- B.Reilly01
27 Jun 2024 12:53
Replied by B.Reilly01 on topic 1990s Millport CNC Vertical Mill Revival
1990s Millport CNC Vertical Mill Revival
Category: Show Your Stuff
I work on a late-80's Bridgeport EZTrak 286 machine that runs off a floppy. Sometimes the path of least resistance is NOT the retrofit. Congrats on getting an old beast up and chip slinging. Ultimately, isn't that the goal of all of us?
Time to create page: 0.435 seconds