On Monday, 6 May 2019 19:32:47 UTC+2, justin White wrote: > > Wonder which human readable file you are refering to as the bitfiles are >> the binaries (*.rbf) generated by quartus from the *.vhd and *.sv, *.v >> source files... >> > Was talking about Mesa's .vhd files. > > I'm no electronics expert... The datasheet for my single ended encoder >> says max 30 mA, so I figured 220 ohm at 3.3volts gives max 15mA or so... > > That would be the current handling ability of the encoder's outputs, but > all you have to do is drive an FPGA pin. That takes almost no current to > do. Since you want to make sure that that FPGA pin has a defined state when > it's not being driven you need to pull it toward one side with a resistor. > If you use a strong pullup/down it requires more current to drive it toward > the other side. The 15mA is being wasted through that resistor. 15mA isn't > a big deal but if you have alot of I/O it'll add up. >
Sure the 220 ohms are just for initial test purposes and to make certain I dont pickup noise as I'm running a 2 meter cable from the encoder to the soc. > > If your FULL error message is: >> > It literally just prints out "segmentation fault". I just tried it on one > of my other Linuxcnc machines and if LinuxCNC is running, I can open a new > terminal and cd to the halshow.tcl directory and ./ to execute it just as > if I started it in the GUI. That doesn't work on this image even after > using the export command you mentioned. I'll have to try updating the > packages you mentioned and see if that helps. > > you cannot update directly to the -cnc -hal machinekit packages I think... best way is to remove the old packages with sudo apt purge then sudo apt autoremove You may get some complaints (when installing the new packages) about yapps, when installing solution is to uninstall/purge that package also. I'm still trying to find some info on some of the "tags" used in the hm2 > vhd files, I don't suppose this is documeted somewhere? > > Have you whached the presentation Charles linked to ? > I see the "capsense" tags but I'm not sure what that is, something Cramps > related? > Capsense is a new touch sensor core I have added not mesa related..(You can safely ignore that). > > Some of the Mesa PWM implementations are a 3 pin deal with an enable and > direction pin. The MK configs only seem to use the "PWMAOutPin" per unit. > Looking at a top level vhd file it appears that the PWMBDirPin, and > PWMCEnaPin are there. I suppose it's just a matter of including these pins > in that unit? > As Charles stated earlier this is complicated stuff to understand and the options are vast. You have to be more verbose as to what you are aiming to get up and running. I only have the info you have provided in this thread and I have no idea of what your goal is. There is a NANOADCTag listed in the ModuleIDs but I haven't found any usage > of it other than that. Is that just a placeholder or does it have an > implementation? > The xxx_Cramps (quartus project) configs are the only current configs that provide ADC functionality straight into the Hal, the tags are there so that the hostmot2 soc hal driver can pick them up if needed. With the DE0_Nano_SoC board the (xxx_CRAMPS) ADC functionality works as it is supposed to, for some mystical reason this is not the case with my 2 DE!0_Nano boards, so I'm trying to debug this issue currently. Even though you may have written this earlier (someplace else) I would be great for me if you can place a description or a link as to what you are aiming to accomplish, so that I then can come up with more presice answers pointing you in the right direction. Best wishes Michael Brown -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
