#linuxcnc Logs
Jan 03 2025
#linuxcnc Calendar
04:17 AM -!- #linuxcnc mode set to +v by ChanServ
07:20 AM rdtsc-w: Using the 3D-printed PETG jig, tipped the frame on its side, then aligned, drilled, and tapped 6x M4x0.7 for the gantry cable-chain. Worked fine. Thinking some medium threadlocker might be warranted on these.
07:29 AM lcnc-relay: <schoch_@> morning
07:33 AM lcnc-relay: <schoch_@> for anyone using RIO, i'm working on getting fully automated customization working. The problem statement is this: "as I hack on hal/ini files my working configs drift far from the rio generated configs and I soon forget what is required and what is a 'hack'. My goal is to be able to easily hack and regenerate. I'm trying to avoid having to add every little change to the json config file and/or have to update the main source code...
07:33 AM lcnc-relay: ... to accommodate customization." I started a discussion here, interested to hear what others may want to see in this space? Maybe we can get Olli to build a hook to my "customizer" so that builds/regeneration incorporates the final customization. https://github.com/multigcs/riocore/discussions/46
07:34 AM lcnc-relay: <schoch_@> right now it can fully regenerate the ini file based on simple templates to add customization back into a generated ini file.
07:36 AM lcnc-relay: <schoch_@> i'm also thinking about how it could make customizing the hal component (riocomp.c) easier using cheetah's templating vs just string lists.
08:09 AM -!- #linuxcnc mode set to +v by ChanServ
08:09 AM -!- #linuxcnc mode set to +v by ChanServ
08:29 AM -!- #linuxcnc mode set to +v by ChanServ
08:40 AM -!- #linuxcnc mode set to +v by ChanServ
08:50 AM -!- #linuxcnc mode set to +v by ChanServ
12:12 PM lcnc-relay: <meisterdippel@> now i have my first Spartan-6 board 🙂 lx9 microboard
12:13 PM lcnc-relay: <meisterdippel@> ok, not very usefull, but i can do test's with it
12:33 PM rdtsc-w: looks pretty nice for a dev board; includes (chip-locked) software extras that otherwise would be pretty expensive
01:04 PM lcnc-relay: <meisterdippel@> my i2c-bus support has become really cool, now i can also control the bus-clock per device
01:04 PM lcnc-relay: verilog is not that bad 🙂 even on a microcontroller it would have been difficult
01:24 PM Unterhausen: zuck hastening the death of the internet by populating Meta sites with AI bots
01:24 PM Tom_L: maybe they'll start talking to each other
01:28 PM roycroft: i read yesterday that an operator of an ai bot is suing someone for copyright infringement for using ai-generated data
01:28 PM roycroft: i've not been interested enough to try to verify that, but it seems plausible to me
01:39 PM Unterhausen: The available LLM's just plagiarized the internet, so that's pretty wild they would sue
01:40 PM Unterhausen: The more specialized the subject, the more likely they are just summarizing the forums on the subject
01:40 PM xxcoder: lol https://www.reddit.com/r/mildlyinfuriating/comments/1hsqe2z/metas_aigenerated_profiles_are_starting_to_show/
01:40 PM xxcoder: talking about ai
01:40 PM Unterhausen: the theory is there are lonely people who won't care they are interacting with bots
01:41 PM Unterhausen: If I see someone I don't know liking my insta posts, I block them immediately
01:42 PM xxcoder: lol reminds me of that time some scammer liked virtually every post I made at facebook last 4 years then tried to friend me
01:43 PM xxcoder: blocked of course
02:33 PM xxcoder: Unterhausen: reminds me of that story where guy who stole a car and robbed a bank, and as he ran out, he found out his stolen car was stolen
02:33 PM xxcoder: he called cops of course
03:02 PM lcnc-relay: <oddname_skane@> well im giving up modbus with my huanyang vfd 😄 0-10v it is instead 😄
03:02 PM lcnc-relay: <ccatlett1984@> got the pi5 rtai image on the pi, omfg this is frustrating for settingup wifi.....
03:03 PM lcnc-relay: <JT> Yo
03:03 PM lcnc-relay: <ccatlett1984@> finally figured it out
03:03 PM lcnc-relay: <oddname_skane@> or rather 0-5V
03:09 PM lcnc-relay: <JT> Looks like some winter crap coming Saturday night
03:21 PM xxcoder: https://media.newyorker.com/photos/590966ed6552fa0be682f085/4:3/w_480%2Cc_limit/Crouch-Boston-Snow.jpg
03:22 PM lcnc-relay: <JT> Ok that is bad
03:22 PM xxcoder: :) well heres been around mid 40s f for a while
03:23 PM xxcoder: very typical winter for here.
03:23 PM lcnc-relay: <JT> Next week high 28 low 14
03:30 PM lcnc-relay: <big_kevin420@> ccatlett1984@: what are you doing with the rtia image?
03:31 PM lcnc-relay: <ccatlett1984@> my mesa 7c80 endeavour
03:32 PM lcnc-relay: <ccatlett1984@> correction, so this is also preempt_rt.....
03:33 PM lcnc-relay: <ccatlett1984@> so help me, if this works, then my original image just had a config issue
03:33 PM lcnc-relay: <ccatlett1984@> vs wrong kernel type
03:41 PM rdtsc-w: thought the kernel type looked right before, but your config seemed to be for RT, unsure why it wouldn't have worked - good luck
03:42 PM lcnc-relay: <ccatlett1984@> i'm more concerened why the new spi driver wasn't working
03:42 PM lcnc-relay: <ccatlett1984@> concerned
03:42 PM lcnc-relay: <ccatlett1984@> building from source now, so will know in a bit
03:44 PM lcnc-relay: <big_kevin420@> k, well, makesure its rt-preempt
03:45 PM lcnc-relay: <big_kevin420@> you keep doing a lot of stuff
03:45 PM lcnc-relay: <big_kevin420@> was the first issue you couldnt connect to the mesa config thing or the linuxcnc
03:59 PM lcnc-relay: <big_kevin420@> ccatlett1984@ i think you might be spinning yopur wheels here
04:00 PM lcnc-relay: <ccatlett1984@> not sure how, this is a debian imag that they say they tested working, and that i'd just need to build from source before testing
04:00 PM lcnc-relay: <ccatlett1984@> img
04:00 PM lcnc-relay: <big_kevin420@> yeah good. the one pcw linked to?
04:00 PM lcnc-relay: <ccatlett1984@> yes
04:00 PM lcnc-relay: <big_kevin420@> ok
04:00 PM lcnc-relay: <big_kevin420@> use that image
04:00 PM lcnc-relay: <big_kevin420@> dont do anythign with the kernel
04:01 PM lcnc-relay: <ccatlett1984@> wasn't planning on it
04:01 PM lcnc-relay: <big_kevin420@> the issue comes when building lcnc and rpi
04:01 PM lcnc-relay: <big_kevin420@> and "connecting" linuxcnc to the kernel
04:02 PM lcnc-relay: <ccatlett1984@> interesting
04:02 PM lcnc-relay: <big_kevin420@> ok so when you are building, i havent built since buster, but its probably gonna be close to the same
04:03 PM lcnc-relay: <big_kevin420@> hmm my build instructions are on dif machine but lets see if i can remember
04:03 PM lcnc-relay: <big_kevin420@> - download the repo
04:04 PM lcnc-relay: <big_kevin420@> cd emc2/debian
04:04 PM lcnc-relay: <big_kevin420@> or what ever you call it
04:04 PM lcnc-relay: <big_kevin420@> cd emc2/debian
04:04 PM lcnc-relay: <big_kevin420@> ./configure -uspace or something like that
04:04 PM lcnc-relay: <ccatlett1984@> yep, ran that
04:04 PM lcnc-relay: <big_kevin420@> just do it like twice or something
04:05 PM lcnc-relay: <ccatlett1984@> did that on my initial build as well, :crosses fingers:
04:05 PM lcnc-relay: <big_kevin420@> do it several times, there were some cases where i would do it once and it wouldnt work
04:05 PM lcnc-relay: <ccatlett1984@> oh lol
04:05 PM lcnc-relay: <big_kevin420@> ok, ithink i missed a step, but we will find out
04:06 PM lcnc-relay: <big_kevin420@> k then backl to emc2/src
04:06 PM lcnc-relay: <big_kevin420@> ./autogen.sh
04:06 PM * Tom_L grabs some popcorn and watches
04:06 PM lcnc-relay: <big_kevin420@> ./configure
04:07 PM lcnc-relay: <big_kevin420@> i think its after configure
04:07 PM lcnc-relay: <big_kevin420@> sroll up, and make sure its gotr something likle
04:07 PM lcnc-relay: <big_kevin420@> 142/142 dependicies
04:07 PM lcnc-relay: <big_kevin420@> if not, i usually ran it again and it worked
04:07 PM lcnc-relay: <big_kevin420@> once it tells you all deps are there
04:08 PM lcnc-relay: <big_kevin420@> make -j4
04:09 PM lcnc-relay: <big_kevin420@> after it makes, it better be fast on rpi5 because im gonna do it after the lcnc debian image downloads
04:09 PM Tom_L: -j4 depends on your cpu
04:09 PM lcnc-relay: <big_kevin420@> shuld be atleast 4 on rpi
04:09 PM lcnc-relay: <big_kevin420@> sometimes ico messes with the build though
04:10 PM lcnc-relay: <ccatlett1984@> i've seen suggestions of 6 for the pi5
04:10 PM lcnc-relay: <big_kevin420@> ok, try 6
04:10 PM lcnc-relay: <big_kevin420@> i havent built rpi5 yet
04:10 PM lcnc-relay: <ccatlett1984@> it's been building, i may have forgotten to tell it not to build docs
04:10 PM lcnc-relay: <big_kevin420@> when it done
04:11 PM lcnc-relay: <big_kevin420@> sudo make setuid
04:11 PM Tom_L: docs take 3x longer
04:12 PM lcnc-relay: <ccatlett1984@> sonofa.... missing a sinlge file for docs build. errored the build
04:12 PM lcnc-relay: <ccatlett1984@> tehehehe
04:13 PM lcnc-relay: <ccatlett1984@> ../docs/src/ar/drivers/mb2hal_HOWTO.ini: No such file or directory
04:13 PM lcnc-relay: <ccatlett1984@> adding the no docs switch
04:13 PM lcnc-relay: <big_kevin420@> wait
04:13 PM lcnc-relay: <big_kevin420@> before ytou rebuild
04:13 PM lcnc-relay: <big_kevin420@> do ./configure
04:13 PM lcnc-relay: <big_kevin420@> and check the deps
04:14 PM lcnc-relay: <big_kevin420@> says it like right after you do it, if its not full, dont bother building
04:19 PM Tom_L: JT-Cave, winter storm watch next 2 days here
04:19 PM Tom_L: power company even sent me a 'we're on standy' notice
04:22 PM lcnc-relay: <ccatlett1984@> configure passed with flying colors
04:22 PM lcnc-relay: <ccatlett1984@> starting rebuild
04:23 PM Tom_L: hope you're writing this all down for a rpi5 wiki
04:23 PM lcnc-relay: <JT> Here too
04:23 PM Tom_L: you on the job?
04:23 PM lcnc-relay: <ccatlett1984@> I'm jotting down notes as I do this
04:23 PM lcnc-relay: <ccatlett1984@> once it's working, i have a spare sd card and will work through step by step to validate i didn't miss anything
04:24 PM lcnc-relay: <JT> Gotta charge the batteries for the generator tonight
04:24 PM Tom_L: i was gonna go start mine and warm it up
04:24 PM Tom_L: haven't had it on in a couple years
04:28 PM lcnc-relay: <JT> I'll run mine tomorrow
04:29 PM lcnc-relay: <JT> Mine is a 2 cylinder diesel
04:30 PM Tom_L: my friend got a 11kw one from a store that closed and has it wired with an aut switch to mains
04:30 PM Tom_L: auto*
04:30 PM Tom_L: iirc runs on propane since he's rural
04:31 PM lcnc-relay: <JT> I have to switch a couple of breakers
04:31 PM Tom_L: same here
04:31 PM lcnc-relay: <JT> Mine came from a police station near St Louis
04:32 PM lcnc-relay: <JT> 3 phase
04:49 PM lcnc-relay: <ccatlett1984@> which of the following deb's do i install?
04:49 PM lcnc-relay: -rw-r--r-- 1 pi pi 9.7M Jan 4 08:31 linuxcnc-uspace-dbgsym_2.10.0~pre0_arm64.deb
04:49 PM lcnc-relay: -rw-r--r-- 1 pi pi 247K Jan 4 08:31 linuxcnc-uspace-dev_2.10.0~pre0_arm64.deb
04:49 PM lcnc-relay: -rw-r--r-- 1 pi pi 29M Jan 4 08:31 linuxcnc-uspace_2.10.0~pre0_arm64.deb
04:49 PM lcnc-relay: <ccatlett1984@> assuming all 3?
04:52 PM lcnc-relay: <roguish> yup, all 3
04:56 PM roycroft: first thou shalt conjure the holy aptitude module. then thou shalt install three debs. no more. no less. three shalt be the number of debs to install, and the number of the installing shalt be three. four shalt thou not installi neither install two, excepting that though then proceedeth to three. five debs is right out.
04:57 PM lcnc-relay: <ccatlett1984@> lol
04:57 PM lcnc-relay: <ccatlett1984@> had to fix a dependency (that the check didn't catch) but installed successfully now
04:57 PM lcnc-relay: <ccatlett1984@> now building latest mesaflash
04:58 PM roycroft: thus spaketh the lord thy linus
05:02 PM lcnc-relay: <ccatlett1984@> mesaflash built successfullly
05:02 PM lcnc-relay: <ccatlett1984@> shutting down and putting into the machine
05:14 PM Tom_L: gen started on the 1st pull after 2 yrs
05:14 PM Tom_L: ccatlett, the last deb
05:15 PM Tom_L: first is debug sym 2nd is dev which would be ok
05:16 PM Tom_L: last is the user one
05:16 PM Tom_L: i wouldn't think you need all 3
05:17 PM lcnc-relay: <ccatlett1984@> so, fun times
05:17 PM lcnc-relay: <ccatlett1984@> mesaflash (latest 3.5.10) can't see the board, but halcmd does
05:17 PM lcnc-relay: <big_kevin420@> ok what driver do you load on mesaflash
05:18 PM lcnc-relay: <big_kevin420@> or whats your command
05:18 PM Tom_L: did you use the right switch for mesaflash?
05:18 PM Tom_L: --help or something will tell you
05:18 PM lcnc-relay: <ccatlett1984@> using the exact switch PCW had me use earlier
05:18 PM lcnc-relay: <ccatlett1984@> sudo mesaflash --device 7c80 --addr /dev/spidev0.0 --spi --readhmid
05:18 PM Tom_L: is /dev/spidev there?
05:19 PM lcnc-relay: <ccatlett1984@> yep, otherwise i don't see how halcmd would see the card
05:19 PM lcnc-relay: <big_kevin420@> sudo mesaflash --device 7c80 --addr /dev/spidev0.0 --spi --readhmid
05:19 PM lcnc-relay: <big_kevin420@> > ?
05:19 PM lcnc-relay: <ccatlett1984@> oh lol, spidev name is different
05:19 PM lcnc-relay: <ccatlett1984@> hang on
05:20 PM lcnc-relay: <ccatlett1984@> /dev/ only has spi10.0
05:20 PM lcnc-relay: <big_kevin420@> ok
05:21 PM lcnc-relay: <ccatlett1984@> nope, get the unexpected cookie error when i change the mesaflash command
05:21 PM lcnc-relay: <big_kevin420@> to 10?
05:21 PM lcnc-relay: <ccatlett1984@> sudo mesaflash --device 7c80 --addr /dev/spidev10.0 --spi --readhmid
05:21 PM lcnc-relay: <big_kevin420@> when you first booted, what did you try first
05:22 PM lcnc-relay: <big_kevin420@> mesa flash or halcmd
05:22 PM lcnc-relay: <ccatlett1984@> mesaflash, before halcmd
05:22 PM lcnc-relay: <big_kevin420@> ok
05:22 PM lcnc-relay: <ccatlett1984@> any ideas?
05:23 PM lcnc-relay: <big_kevin420@> yeah i gotta get my notes off one of these rpi
05:23 PM lcnc-relay: <big_kevin420@> you have kernel spi enabled?
05:23 PM lcnc-relay: <big_kevin420@> i always had a wierd issue with mesaflash and spi
05:23 PM lcnc-relay: <ccatlett1984@> assuming, since i was instructed this was a working image
05:24 PM lcnc-relay: <big_kevin420@> if i went into mesaflash after i went into linuxcnc is would never connect
05:24 PM lcnc-relay: <ccatlett1984@> linuxcnc has not been started since boot
05:24 PM lcnc-relay: <big_kevin420@> well, the hm2 driver i mean specifically
05:24 PM lcnc-relay: <big_kevin420@> if i conneceted to the hm2 driver before spidev driver
05:25 PM Tom_L: pretty sure you load the hm2 driver ahead of the spi one
05:25 PM Tom_L: you need both of them
05:26 PM lcnc-relay: <ccatlett1984@> yes had to load 2 drivers into halcmd for the card to appear
05:32 PM lcnc-relay: <ccatlett1984@> https://forum.linuxcnc.org/27-driver-boards/54899-pi5-mesa-7c80-mesaflash-can-t-see-the-card/317980
05:32 PM lcnc-relay: <ccatlett1984@> updated thread
05:40 PM lcnc-relay: <big_kevin420@> ok so the hm2 driver isnt needed thats what im saying
05:41 PM lcnc-relay: <ccatlett1984@> great, so how do i get mesaflash to use it?
05:41 PM lcnc-relay: <big_kevin420@> and i found the hm2 driver messed with my mesaflash
05:41 PM firephoto__ is now known as firephoto_
05:41 PM lcnc-relay: <ccatlett1984@> ah
05:41 PM lcnc-relay: <big_kevin420@> that spidev0.0 is loading the software driver
05:41 PM lcnc-relay: <big_kevin420@> its odd your getting a bad spi command though
05:41 PM lcnc-relay: <big_kevin420@> well, no command
05:42 PM lcnc-relay: <big_kevin420@> just built mesaflash doing what you did in the thread and i just connected to my 7c81
05:42 PM lcnc-relay: <ccatlett1984@> one thing i just saw
05:42 PM lcnc-relay: <ccatlett1984@> the kernel in this image is 6.1.61-rt15
05:43 PM lcnc-relay: <ccatlett1984@> when i built linuxcnc the ./debian/configure script said uspace
05:43 PM lcnc-relay: <big_kevin420@> yeah thats what we are using
05:43 PM lcnc-relay: <ccatlett1984@> just wanted to validate
05:43 PM lcnc-relay: <big_kevin420@> its a thing i dont understand but it makes a posix realtime
05:44 PM lcnc-relay: <ccatlett1984@> none of the rtai switches listed for the configure command seem to be valid
05:44 PM lcnc-relay: <ccatlett1984@> was going to try rebuilding with the rtai switch
05:44 PM lcnc-relay: <big_kevin420@> rtia isnt really what we want for the external steopgen
05:44 PM lcnc-relay: <ccatlett1984@> since it's something i could try while waiting
05:45 PM lcnc-relay: <ccatlett1984@> that makes sense to me, but wasn't sure of the under-lying modules and how they are inter-related to the different build options
05:45 PM lcnc-relay: <big_kevin420@> i was getting a different error than you, but i had my spi turned off
05:45 PM lcnc-relay: <big_kevin420@> because you dont need it on for linuxcnc related spi
05:46 PM lcnc-relay: <big_kevin420@> but to use spidev you probably do
05:46 PM lcnc-relay: <big_kevin420@> but you arent getting board not foubnd, you are getting bad cookie 000000000
05:47 PM lcnc-relay: <big_kevin420@> the other thing is, if halcmd worked, that means linuxcnc should work
05:47 PM lcnc-relay: <big_kevin420@> if you did halcmd loadrt hm2_spix or something
05:47 PM lcnc-relay: <ccatlett1984@> so, looking at the config.txt in this image, the spi overlay is NOT enabled...
05:48 PM lcnc-relay: <ccatlett1984@> unless vanilla debian does that somewhere else
05:48 PM lcnc-relay: <big_kevin420@> alright, i guess enable it, i think its odd you have a dif error than me, but im not using the lcnc debian build, im using a raspian build
05:49 PM lcnc-relay: <big_kevin420@> but you can also try lcnc
05:49 PM lcnc-relay: <ccatlett1984@> yeah, that's what i was using (the raspbian build)
05:49 PM lcnc-relay: <ccatlett1984@> i dont have a hal file setup at all
05:50 PM lcnc-relay: <ccatlett1984@> need to see the card to generate a basic config
05:50 PM lcnc-relay: <ccatlett1984@> this is a brand new setup entirely
05:50 PM lcnc-relay: <big_kevin420@> ok i guess do the mesaflash first then
05:50 PM lcnc-relay: <big_kevin420@> you sure its raspbian and not debian on the rpi5?
05:51 PM lcnc-relay: <ccatlett1984@> my previous attemp (still on another SD card) was raspbian
05:51 PM lcnc-relay: <ccatlett1984@> this image is debian
05:51 PM lcnc-relay: <big_kevin420@> ok, you might need to restart than after you change it to on
05:51 PM lcnc-relay: <ccatlett1984@> yep, going to try that now
05:52 PM lcnc-relay: <ccatlett1984@> enabled and rebooting
05:58 PM lcnc-relay: <big_kevin420@> whats an easy way i can update this linuxcnc i have now
05:58 PM lcnc-relay: <big_kevin420@> is there like, linuxcnc -- update
05:58 PM lcnc-relay: <big_kevin420@> or something?
05:58 PM lcnc-relay: <big_kevin420@> omg i already know i wont like the answer, it will be hard
06:01 PM lcnc-relay: <ccatlett1984@> build from source, and install package?
06:01 PM lcnc-relay: <ccatlett1984@> 😄
06:02 PM lcnc-relay: <ccatlett1984@> enabling the SPI overlay in /boot/broadcom/config.txt, I now see 3 spi entries in /dev/
06:02 PM lcnc-relay: <ccatlett1984@> mesaflash still doesn't see the card
06:03 PM lcnc-relay: <ccatlett1984@> with the spi overlay enabled, hostmot2 fails to load for halcmd
06:03 PM lcnc-relay: <ccatlett1984@> disabling and rebooting to see if it reverts
06:05 PM Tom_L: when you build linuxcnc from source make sure to remove the installed one
06:05 PM Tom_L: just in case
06:08 PM lcnc-relay: <ccatlett1984@> so, as above, I disabled the spi overlay in config.txt, rebooted, halcmd still fails to load hostmot2
06:08 PM Tom_L: i thought they moved config.txt from broadcom
06:08 PM lcnc-relay: <ccatlett1984@> in raspbian yes, in debian no
06:08 PM Tom_L: i thought in debian - yes
06:08 PM lcnc-relay: <big_kevin420@> yeah i thought debian also
06:09 PM Tom_L: you better double check that
06:09 PM lcnc-relay: <ccatlett1984@> well, if they had, my change wouldn't have done anything
06:09 PM Tom_L: in ras it used to be in broadcom
06:09 PM lcnc-relay: <ccatlett1984@> and it did, and it broke something
06:09 PM lcnc-relay: <big_kevin420@> well, if it made one not work, it is doing something
06:11 PM Tom_L: On Debian 12 (Raspberry Pi OS), the "config.txt" file is located in the "/boot/firmware" directory, meaning the full path is "/boot/firmware/config.txt".
06:12 PM lcnc-relay: <ccatlett1984@> yes, on raspbian
06:12 PM Tom_L: i'm running debian 12 on my rpi4 and that's where it is
06:12 PM lcnc-relay: <ccatlett1984@> this seems to be vanillia debian
06:12 PM lcnc-relay: <ccatlett1984@> the firmware folder doesnt exist at all
06:12 PM roycroft: raspbian is effectively debian 12 now
06:12 PM roycroft: raspbian as a distro is gone
06:13 PM roycroft: it's now "raspberry pi os"
06:13 PM lcnc-relay: <ccatlett1984@> pi@linuxcnc:/$ cd boot
06:13 PM lcnc-relay: pi@linuxcnc:/boot$ ls
06:13 PM lcnc-relay: Image System.map-6.1.61-rt15 broadcom config-6.1.61-rt15 initrd.gz initrd.img-6.1.61-rt15 vmlinuz-6.1.61-rt15
06:14 PM lcnc-relay: <big_kevin420@> do youhave rpi icons all over or no
06:14 PM lcnc-relay: <ccatlett1984@> no
06:14 PM lcnc-relay: <ccatlett1984@> and not wayland
06:14 PM rdtsc: raspi-config may be menu-config in Debian, in case you need that.
06:14 PM lcnc-relay: <ccatlett1984@> so, after reverting halcmd is still borked
06:15 PM Tom_L: ain't this fun??
06:15 PM * rdtsc nudges Tom to share the popcorn!
06:15 PM lcnc-relay: <ccatlett1984@> at least i have step-by-step up to this point now 😉
06:15 PM lcnc-relay: <ccatlett1984@> on section 2 of my onenote for this
06:15 PM Tom_L: been down these rabbit holes a few times
06:16 PM lcnc-relay: <ccatlett1984@> assuming this is spi driver related
06:16 PM rdtsc: those that got this working before... what did they do differently?
06:16 PM lcnc-relay: <ccatlett1984@> i dont think anyone has this working on a 7c80
06:17 PM lcnc-relay: <ccatlett1984@> cornholio has some chinese board flashed with something (i think it's like a 7c81)
06:17 PM rdtsc: well PCW updated mesaflash for it, so presumably he's gotten it to work?
06:17 PM Tom_L: what was that thread that said someone used spi1 instead of spi0 on that
06:17 PM lcnc-relay: <ccatlett1984@> can't do that with the 7c80, it's a solid 40pin cable, that is 1.5" long
06:18 PM lcnc-relay: <big_kevin420@> ok, well lets not confuse the 2 issues
06:18 PM * Tom_L looks at his xacto knife
06:18 PM lcnc-relay: <big_kevin420@> 1 is mesa flash
06:18 PM lcnc-relay: <big_kevin420@> and 1 is lcnc
06:18 PM * rdtsc actually hacked into his 1.5" cable, and pulled out the serial transmit pins - monitoring that for a power latch
06:18 PM lcnc-relay: <ccatlett1984@> i don't think i'm to the lcnc issue yet, this is basic board communication, unless mesaflash is leveraging lcnc modules
06:18 PM Tom_L: big_kevin, the only issue i see is i'm running low on popcorn
06:19 PM lcnc-relay: <big_kevin420@> mesaflash = spidev=just for flash
06:19 PM lcnc-relay: <big_kevin420@> lcnc = hm2_spix and for operating
06:19 PM * rdtsc pops a fresh bag of popcorn
06:19 PM lcnc-relay: <big_kevin420@> you shouldnt have to actually connect to the board for opncconf
06:19 PM lcnc-relay: <ccatlett1984@> so, mesaflash should be "lower level" ?
06:20 PM lcnc-relay: <big_kevin420@> i only needed mesaflash when i was changing daughter cards
06:20 PM Tom_L: ccatlett, i know previously on another board pcw changed the name of the board in mesaflash. you might take a peek at the source for something odd like that
06:20 PM lcnc-relay: <big_kevin420@> 7c80 probably doesnbt hjave a lot of options
06:20 PM Tom_L: make sure the --spi switch is what you think it is
06:20 PM lcnc-relay: <ccatlett1984@> oh dear, going to the repo now, although I hope he would have remembered that in his instructions to me
06:21 PM lcnc-relay: <big_kevin420@> he didnt say anything like that
06:21 PM lcnc-relay: <ccatlett1984@> correct
06:21 PM Tom_L: it was an oversight when he switched fpga and renamed a couple boards iirc
06:21 PM lcnc-relay: <big_kevin420@> i just recreated you instructions
06:21 PM Tom_L: it's a long shot
06:21 PM lcnc-relay: <ccatlett1984@> Cake, you're on a 7c81 though, right?
06:21 PM rdtsc: hmm thinking out loud... sees card but bad cookie - could the firmware be corrupt (and readable in 2.9.3, but not readable in 2.10.x?)
06:21 PM lcnc-relay: <big_kevin420@> so if it was 7c80 specifically, otherwise, the 7c81 connected
06:21 PM lcnc-relay: <big_kevin420@> yeah im using 7c81
06:22 PM lcnc-relay: <ccatlett1984@> kk, worth a look
06:22 PM Tom_L: double check board names in the source
06:24 PM Tom_L: that was actually what brought about 3.5.9
06:24 PM Tom_L: from .8
06:24 PM lcnc-relay: <ccatlett1984@> 7c80 exists
06:25 PM lcnc-relay: <ccatlett1984@> {"7C80", BOARD_MULTI_INTERFACE | BOARD_EPP | BOARD_SPI},
06:25 PM lcnc-relay: {"7C81", BOARD_MULTI_INTERFACE | BOARD_EPP | BOARD_SPI},
06:26 PM lcnc-relay: <big_kevin420@> yeah they were released side by side
06:26 PM lcnc-relay: <ccatlett1984@> OMG
06:26 PM lcnc-relay: <ccatlett1984@> https://forum.linuxcnc.org/27-driver-boards/54899-pi5-mesa-7c80-mesaflash-can-t-see-the-card?start=30
06:26 PM lcnc-relay: <ccatlett1984@> look at the last comment
06:26 PM lcnc-relay: <ccatlett1984@> sonfa
06:26 PM Tom_L: :)
06:26 PM lcnc-relay: <big_kevin420@> hes joking, lets keep trying
06:27 PM * rdtsc pours butter on the popcorn...
06:27 PM rdtsc: ccatlett1984, would you have the hardware to program the FPGA?
06:28 PM lcnc-relay: <ccatlett1984@> the pi4 can see it, so why can't i use that?
06:28 PM Tom_L: i think you just need to reflash it
06:28 PM lcnc-relay: <big_kevin420@> good question
06:28 PM lcnc-relay: <big_kevin420@> lets keep trying
06:28 PM Tom_L: i might be wrong for that situation
06:28 PM lcnc-relay: <ccatlett1984@> or do i just need to make a JTAG cable? lord, last time i did that was to unbrick a WRT-54G
06:28 PM lcnc-relay: <big_kevin420@> some kind of blaster
06:29 PM lcnc-relay: <big_kevin420@> when its fpga, its a blaster i think
06:29 PM Tom_L: no, jtag
06:29 PM lcnc-relay: <ccatlett1984@> getting that will probably be faster than an RMA
06:29 PM Tom_L: i have one
06:29 PM rdtsc: I'm thinking it's one of those low-level programmings that require like the ISE programmer and 14GB of software download to run
06:29 PM lcnc-relay: <ccatlett1984@> 😄
06:29 PM rdtsc: or maybe a blaster, dunno
06:29 PM Tom_L: you might be better off letting PCW do it
06:29 PM Tom_L: is it a spartin6?
06:29 PM rdtsc: gosh, now does mine have this firmware???
06:30 PM * Tom_L watches everyone scramble to check their boards
06:30 PM rdtsc: can't check mine, put a heatsink on it lol
06:30 PM lcnc-relay: <big_kevin420@> im sure he was joking
06:30 PM Tom_L: no
06:30 PM Tom_L: i doubt it
06:30 PM lcnc-relay: <big_kevin420@> hes pushing you to troubleshoot harder
06:30 PM lcnc-relay: <skunkworks8841@> shop is a steady 55F - yay!
06:30 PM rdtsc: PCW doesn't seem to be the joking type... could be wrong though
06:30 PM Tom_L: he doesn't do that
06:31 PM lcnc-relay: <ccatlett1984@> what the actual fuck...... that is not professional at all.
06:31 PM lcnc-relay: <big_kevin420@> hes not joking
06:31 PM lcnc-relay: <ccatlett1984@> if he's joking, he lost a customer for life
06:31 PM lcnc-relay: <ccatlett1984@> i'm dead serious on that
06:31 PM lcnc-relay: <big_kevin420@> hes not joking
06:31 PM Tom_L: no he wouldn't joke about that
06:31 PM lcnc-relay: <big_kevin420@> im bored and dont wanna fix my own junk
06:31 PM rdtsc: congrats SW - when you get it to 72, call us up - we'll bring the beer.
06:31 PM Tom_L: skunkworks, cool
06:31 PM Tom_L: err warm
06:32 PM lcnc-relay: <ccatlett1984@> 72 is too warm for a shop, unless you are laying on concrete floor
06:32 PM lcnc-relay: <big_kevin420@> hes not joking, pwc is the best, and has the paitence of a god
06:32 PM Tom_L: at least i'm glad i had you check
06:32 PM lcnc-relay: <skunkworks8841@> can I say.... I have used probably 20+ mesa boards and have never bricked any?
06:32 PM lcnc-relay: <big_kevin420@> but lets tug at loose threads
06:32 PM Tom_L: does it see it as a 7c80?
06:32 PM lcnc-relay: <big_kevin420@> why did the rpi4 work
06:32 PM lcnc-relay: <ccatlett1984@> the pi4 does
06:33 PM Tom_L: what mesaflash version on it?
06:33 PM lcnc-relay: <ccatlett1984@> latest, also built from source
06:33 PM lcnc-relay: <ccatlett1984@> two days ago, iirc
06:33 PM Tom_L: i always build those from source
06:33 PM Tom_L: and build .10 then too
06:33 PM lcnc-relay: <skunkworks8841@> (but I have never done it over spi)
06:33 PM lcnc-relay: <ccatlett1984@> it's 3.5.10
06:33 PM Tom_L: there is a command that will list the boards but i forget what it is
06:34 PM Tom_L: same here
06:34 PM lcnc-relay: <ccatlett1984@> he replied that it's possible, so going to swap the board back to the pi4 with dead video
06:34 PM Tom_L: enter a wrong board name and it may list them all
06:34 PM Tom_L: yes
06:34 PM Tom_L: mesaflash --device xxx
06:34 PM Tom_L: lists them
06:35 PM Tom_L: 80 & 81 are both there
06:37 PM Tom_L: do you know what the default firmware was for the 7c80 7c81?
06:38 PM lcnc-relay: <big_kevin420@> 7c81 is dif
06:38 PM Tom_L: there shouldn't be too many choices on those boards
06:38 PM lcnc-relay: <big_kevin420@> 7c80, the default firmware is probably all you need
06:38 PM Tom_L: i haven't looked
06:38 PM lcnc-relay: <big_kevin420@> since its purpose built
06:38 PM Tom_L: right
06:39 PM lcnc-relay: <big_kevin420@> i say, wage on ahead
06:40 PM lcnc-relay: <big_kevin420@> wait, your config you already know
06:40 PM lcnc-relay: <big_kevin420@> https://forum.linuxcnc.org/27-driver-boards/54899-pi5-mesa-7c80-mesaflash-can-t-see-the-card?start=10#317839
06:41 PM -!- #linuxcnc mode set to +v by ChanServ
06:42 PM Tom_L: which board does he have?
06:42 PM Tom_L: 80 or 81?
06:42 PM lcnc-relay: <big_kevin420@> 81
06:42 PM lcnc-relay: <big_kevin420@> no
06:42 PM lcnc-relay: <big_kevin420@> 80
06:42 PM Tom_L: that reported the right firmware then ehh?
06:43 PM Tom_L: in his last post, the --fallback is if you brick it
06:44 PM Tom_L: get a successful write on the first one before you do that one
06:44 PM Tom_L: and check the /dev/spidevX.X
06:44 PM lcnc-relay: <big_kevin420@> right i forgot theres multi on it
06:44 PM Tom_L: they all have fallback
06:45 PM Tom_L: If you can reliably access the card on the RPI4, you would
06:45 PM Tom_L: sudo mesaflash --device 7c80 --spi --addr /dev/spidev0.0 --write 7c80d.bit
06:45 PM Tom_L: sudo mesaflash --device 7c80 --spi --addr /dev/spidev0.0 --write 7c80fall.bit --fallback
06:45 PM Tom_L: (7c80d.bit and 7c80fall.bit are in the 7c80.zip file in /configs/hostmot2/)
06:46 PM lcnc-relay: <big_kevin420@> i dont think he has the bad fw thing if its working on rpi4
06:46 PM Tom_L: what you linked showed 7c80 firmware
06:47 PM lcnc-relay: <big_kevin420@> yeah
06:47 PM lcnc-relay: <big_kevin420@> its his thing working on rpi4
06:47 PM Tom_L: but with the rpi5 it may be newer firmware... i dunni
06:47 PM Tom_L: dunno
06:47 PM lcnc-relay: <big_kevin420@> not on the mesa side
06:48 PM lcnc-relay: <big_kevin420@> and besides, i just did mine, i dont even have a useable linuxcnc
06:48 PM Tom_L: you don't need lcnc for that
06:48 PM lcnc-relay: <big_kevin420@> exactly
06:48 PM lcnc-relay: <big_kevin420@> you need the linux spi driver
06:49 PM lcnc-relay: <big_kevin420@> but the linuxcnc driver does work
07:02 PM lcnc-relay: <ccatlett1984@> so, pi4 connected, mesaflash sees the card, identifies correctly
07:03 PM Tom_L: ccatlett, did you see PCW's last post on the thread?
07:04 PM lcnc-relay: <ccatlett1984@> yeah, getting ready to flash the firmware
07:04 PM lcnc-relay: <ccatlett1984@> grabbing the zip file now
07:04 PM Tom_L: verify the main one before you do the fallback
07:04 PM Tom_L: if you even do it
07:04 PM lcnc-relay: <ccatlett1984@> so think i should flash main, attempt with the pi5?
07:05 PM lcnc-relay: <ccatlett1984@> or just verify with the pi4?
07:05 PM Tom_L: verify with the rpi4
07:05 PM Tom_L: then flash fallback
07:05 PM lcnc-relay: <ccatlett1984@> kk, sounds like a plan
07:05 PM Tom_L: verify and do a readhmid
07:05 PM Tom_L: then fallback
07:05 PM lcnc-relay: <ccatlett1984@> i mean, literal worst case, the card gets rma'd at this point
07:05 PM lcnc-relay: <ccatlett1984@> if this works, it will save me the shipping time
07:06 PM Tom_L: yeah if fallback gets borked it's jtag time
07:06 PM Tom_L: i haven't jtag'd one in a long time
07:08 PM Tom_L: but, i kinda don't think that's the problem
07:08 PM lcnc-relay: <ccatlett1984@> https://pastebin.com/kf8iUXQY here is the mesaflash output from the pi4
07:09 PM lcnc-relay: <ccatlett1984@> prior to flash
07:09 PM Tom_L: i think you can save that to file if you want
07:09 PM Tom_L: iirc
07:10 PM lcnc-relay: <ccatlett1984@> i did " >>file.txt"
07:10 PM lcnc-relay: <ccatlett1984@> 😛
07:10 PM Tom_L: no the actual bit file
07:10 PM lcnc-relay: <ccatlett1984@> oh
07:10 PM lcnc-relay: <ccatlett1984@> heh
07:10 PM lcnc-relay: <ccatlett1984@> looking at the repo
07:10 PM Tom_L: i haven't done that in a while either
07:11 PM Tom_L: 7c80d.bit is the default one
07:11 PM lcnc-relay: <ccatlett1984@> yep, --backup-flash
07:11 PM Tom_L: just remember what you call it :)
07:12 PM lcnc-relay: <ccatlett1984@> "7c80_maybe_bad-maybe_not.bin"
07:12 PM lcnc-relay: <ccatlett1984@> 😉
07:12 PM Tom_L: bit
07:12 PM Tom_L: bin is for the new fpga
07:12 PM lcnc-relay: <ccatlett1984@> bah, it's linux, file ext doesnt matter
07:13 PM lcnc-relay: <skunkworks8841@> lol - but humans need extentions...
07:14 PM lcnc-relay: <ccatlett1984@> Board 7C80 doesn't support backup flash.
07:14 PM lcnc-relay: <ccatlett1984@> was worth a try
07:14 PM lcnc-relay: <skunkworks8841@> we are not clairvoyant
07:16 PM lcnc-relay: <ccatlett1984@> primary flashed, reloaded and verified
07:16 PM lcnc-relay: <ccatlett1984@> output looks the same to me
07:17 PM lcnc-relay: <ccatlett1984@> going to flash fallback now
07:17 PM Tom_L: ok
07:20 PM * Tom_L feels a tremor in the earth...
07:20 PM roycroft: maybe cut back on the beans?
07:21 PM lcnc-relay: <ccatlett1984@> card happy
07:22 PM lcnc-relay: <ccatlett1984@> output after flashing: https://pastebin.com/5xm8FHpq
07:22 PM Tom_L: good
07:22 PM lcnc-relay: <ccatlett1984@> waiting on PCW to confirm it looks good, prior to swapping pi's back out to the pi5
07:22 PM Tom_L: looks ok to me
07:24 PM Tom_L: did you do a diff on the 2 file outputs?
07:25 PM lcnc-relay: <ccatlett1984@> they are identical
07:25 PM lcnc-relay: <ccatlett1984@> just pulled them into vscode to compare
07:25 PM Tom_L: i'd try booting the rpi5 then
07:26 PM lcnc-relay: <ccatlett1984@> a swapping i will go
07:27 PM Tom_L: i think we've pretty much determined the board is ok
07:27 PM lcnc-relay: <ccatlett1984@> yeah, that was my thought all along
07:28 PM lcnc-relay: <ccatlett1984@> wonder if the hardware revisions the pi5 has had, are anything to do with this.
07:29 PM lcnc-relay: <big_kevin420@> if it did, its linux kernel side issue
07:38 PM lcnc-relay: <ccatlett1984@> update, pi5 - halcmd - sees card
07:38 PM lcnc-relay: <ccatlett1984@> rebooting the pi, then trying mesaflash
07:39 PM Tom_L: did halcmd see it before?
07:40 PM lcnc-relay: <ccatlett1984@> yes
07:40 PM lcnc-relay: <ccatlett1984@> but at least this confirms we are in at least as good a state as before the flash
07:40 PM Tom_L: how many spi are listed in /dev/spixxx?
07:40 PM lcnc-relay: <ccatlett1984@> post reboot 1
07:41 PM lcnc-relay: <ccatlett1984@> "spidev10.0"
07:41 PM lcnc-relay: <ccatlett1984@> feck
07:43 PM Tom_L: show the mesaflash line
07:44 PM Tom_L: mesaflash --device 7c80 --spi --addr /dev/spidev10.0 --readhmid
07:45 PM Tom_L: forget if you need sudo with spi
07:45 PM Tom_L: you do with pci pcie iirc
07:46 PM lcnc-relay: <ccatlett1984@> pi@linuxcnc:/$ sudo mesaflash --device 7c80 --addr /dev/spidev10.0 --spi --readhmid
07:46 PM lcnc-relay: Unexpected cookie at 0100..0110:
07:46 PM lcnc-relay: ffffffff ffffffff ffffffff
07:46 PM lcnc-relay: No 7C80 board found
07:46 PM lcnc-relay: pi@linuxcnc:/$
07:46 PM Tom_L: what happens if you use --spi /dev/spidev0.0 ?
07:47 PM lcnc-relay: <ccatlett1984@> tried that first 😉
07:47 PM lcnc-relay: <ccatlett1984@> pi@linuxcnc:/$ sudo mesaflash --device 7c80 --addr /dev/spidev0.0 --spi --readhmid
07:47 PM lcnc-relay: [sudo] password for pi:
07:47 PM lcnc-relay: open: No such file or directory
07:47 PM lcnc-relay: No 7C80 board found
07:47 PM lcnc-relay: ... long message truncated: https://jauriarts.org/_heisenbridge/media/jauriarts.org/jDcQXJwazwUGlFVMRmYhmlbq/PE9V7W1hnVQ (9 lines)
07:47 PM lcnc-relay: <ccatlett1984@> don't get the cookie error
07:47 PM Tom_L: so it sees the board
07:47 PM Tom_L: but something is wrong with the driver etc
07:47 PM lcnc-relay: <ccatlett1984@> yeah, some initial communication is being attempted, and blowing up
07:48 PM lcnc-relay: <ccatlett1984@> confirmed mesaflash version is 3.5.10
07:48 PM Tom_L: and you tried --device 7c81 with the same settings for kicks..
07:48 PM lcnc-relay: <ccatlett1984@> eh, why not
07:48 PM lcnc-relay: <ccatlett1984@> 😄
07:48 PM lcnc-relay: <ccatlett1984@> one sec
07:49 PM Tom_L: just no board found is all that will happen
07:49 PM lcnc-relay: <ccatlett1984@> pi@linuxcnc:/$ sudo mesaflash --device 7c81 --addr /dev/spidev10.0 --spi --readhmid
07:49 PM lcnc-relay: Unexpected cookie at 0100..0110:
07:49 PM lcnc-relay: ffffffff ffffffff ffffffff
07:49 PM lcnc-relay: No 7C81 board found
07:49 PM lcnc-relay: pi@linuxcnc:/$
07:49 PM Tom_L: but you still got the cookie error
07:50 PM lcnc-relay: <ccatlett1984@> yeah, i dunno
07:50 PM lcnc-relay: <ccatlett1984@> not my image, soo.....
07:50 PM Tom_L: try /dev/spidev1.0 once
07:50 PM Tom_L: i'm sure it won't work but..
07:51 PM lcnc-relay: <ccatlett1984@> but that doesn't exist in /dev/
07:51 PM Tom_L: neither did 0.0
07:51 PM lcnc-relay: <ccatlett1984@> pi@linuxcnc:/$ sudo mesaflash --device 7c80 --addr /dev/spidev1.0 --spi --readhmid
07:51 PM lcnc-relay: open: No such file or directory
07:51 PM lcnc-relay: No 7C80 board found
07:51 PM lcnc-relay: pi@linuxcnc:/$
07:51 PM lcnc-relay: <ccatlett1984@> no cookie error
07:51 PM Tom_L: so you have the right device, the firmware is right, has to be driver related somehow
07:52 PM Tom_L: rpi4 used the old spi driver
07:52 PM Tom_L: this one is brand new
07:54 PM Tom_L: the others were looking for single digit spi device names 0.0 1.0
07:54 PM Tom_L: surely that wouldn't matter
07:54 PM lcnc-relay: <ccatlett1984@> yep
07:55 PM lcnc-relay: <big_kevin420@> no, they both use spidev for mesaflash
07:55 PM lcnc-relay: <big_kevin420@> so it doesnt matter
07:56 PM Tom_L: does it have only 1 spi channel?
07:56 PM Tom_L: i was thinking it had 2
07:56 PM lcnc-relay: <big_kevin420@> on the rpi no
07:56 PM lcnc-relay: <big_kevin420@> has like 10 now
07:56 PM Tom_L: ok
07:57 PM lcnc-relay: <big_kevin420@> not 10 but more than 2
07:57 PM lcnc-relay: <big_kevin420@> or at leasy 2
07:57 PM Tom_L: his indicated 10.0
07:57 PM lcnc-relay: <big_kevin420@> is the one channel displays nothing, but the other is fffffff
07:57 PM Tom_L: are they all enabled in the rpi5 config?
07:57 PM Tom_L: or is the right one enabled?
07:58 PM lcnc-relay: <ccatlett1984@> it's currently DISABLED in config.txt
07:58 PM lcnc-relay: <ccatlett1984@> so no freaking clue where it is enabled in this image
07:58 PM Tom_L: did you try enabling it in the config?
07:59 PM Tom_L: the driver should override that iirc
08:00 PM lcnc-relay: <ccatlett1984@> yes, that broke things prior to the firmware flashing
08:00 PM lcnc-relay: <ccatlett1984@> but, i did then see 3 spi devices
08:00 PM lcnc-relay: <ccatlett1984@> but, halcmd broke
08:00 PM Tom_L: did you try addressing all 3 devices listed?
08:00 PM lcnc-relay: <ccatlett1984@> yep
08:01 PM lcnc-relay: <ccatlett1984@> well, halcmd doesn't have a facility to do that, afaik
08:01 PM lcnc-relay: <ccatlett1984@> but i did with mesaflash
08:01 PM lcnc-relay: <ccatlett1984@> and this was supposed to be a "pre-configured" image, just clone to sd card, install from source, and go....
08:02 PM Tom_L: too bad you don't have another spi device to test on it
08:02 PM lcnc-relay: <big_kevin420@> thangs happen. not everyone has everything and the rpi5 thing is only really a month old
08:02 PM lcnc-relay: <big_kevin420@> but
08:02 PM Tom_L: i tested my spi with a 7i90
08:02 PM lcnc-relay: <big_kevin420@> its a mesaflash/spidev thing
08:03 PM lcnc-relay: <ccatlett1984@> i fully understand that this is just now "entering supported"
08:03 PM lcnc-relay: <big_kevin420@> but like i keep saying, its just a mesaflash thing
08:03 PM Tom_L: report your findings to PCW and see what he says
08:03 PM lcnc-relay: <big_kevin420@> so i weould just configure your thing and go from there
08:03 PM lcnc-relay: <ccatlett1984@> I already reported the latest on the thread on the forum
08:04 PM Tom_L: ok
08:04 PM Tom_L: about the cookie/
08:04 PM Tom_L: ?
08:06 PM lcnc-relay: <ccatlett1984@> so, now PCW want's me to enable spi in the config.txt
08:06 PM lcnc-relay: <ccatlett1984@> time to grab some output
08:14 PM Tom_L: so spidev0.0 is the only spi channel wired to the 7c80
08:18 PM Tom_L: i would do a full power cycle after your edits
08:23 PM Tom_L: explanation update on the thread too
08:36 PM lcnc-relay: <ccatlett1984@> omfg, enabled spi, and it bloody works now
08:36 PM lcnc-relay: <ccatlett1984@> mesaflash works
08:36 PM lcnc-relay: <ccatlett1984@> "party time"
08:37 PM lcnc-relay: <ccatlett1984@> i wonder if halcmd is broken now
08:38 PM lcnc-relay: <ccatlett1984@> and, it also works
08:38 PM lcnc-relay: <ccatlett1984@> so, this state (prior) to flashing, was broken
08:38 PM lcnc-relay: <ccatlett1984@> and i've been power cycling the board and pi for each iteration
08:39 PM lcnc-relay: <ccatlett1984@> well, at least i have some troubleshooting steps to write up
08:46 PM Tom_L: did you read the last forum post?
08:46 PM Tom_L: kinda explains how each thing works
08:51 PM lcnc-relay: <ccatlett1984@> yep, and replied
08:51 PM lcnc-relay: <ccatlett1984@> I too can be passive agressive
08:51 PM lcnc-relay: <ccatlett1984@> at least the name / avatar are fitting
08:52 PM lcnc-relay: <ccatlett1984@> the "mentioned in multiple places/times" doesn't hold water.
08:52 PM lcnc-relay: I will be making a clear call-out in my write-up on this
09:57 PM lcnc-relay: <ccatlett1984@> Hm, looks like the 7c80 isn't in pncconf
10:07 PM Tom_L: not likely
10:09 PM lcnc-relay: <ccatlett1984@> hrm, what's the "usual" practice, pick something "close", and then hand edit?
10:09 PM Tom_L: yeah
10:09 PM Tom_L: i did my config all manually from some example i found
10:10 PM lcnc-relay: <ccatlett1984@> alrighty, looking to see how painful it would be to add it
10:55 PM lcnc-relay: <big_kevin420@> another thing i wouldnt bother with really
10:55 PM lcnc-relay: <big_kevin420@> theres an option for any card
10:55 PM lcnc-relay: <big_kevin420@> you just change it in the ini file
10:56 PM lcnc-relay: <big_kevin420@> just select the 7i96 or something
10:59 PM lcnc-relay: <big_kevin420@> https://github.com/LinuxCNC/linuxcnc/blob/master/configs/by_interface/mesa/hm2-stepper/7i90-rpi-spi.ini#L192
10:59 PM lcnc-relay: <big_kevin420@> its gonna look something like this
11:53 PM lcnc-relay: <ccatlett1984@> Like, I give it you can bypass it by picking something similar. But as a new person to the project, it makes sense that you would support the cards that are available. Instead of these random hacky things, that are only known through institutional knowledge.
11:54 PM lcnc-relay: <ccatlett1984@> _get_