Project Logs

Collapse

• Spring Clip Update

  Kevin Santo Cappuccio • 3 天前 • 0 comments

  So, you’ve probably noticed that sticking things into the Jumperless’s breadboard contacts isn’t quite as easy or smooth as regular breadboards. Here’s why:

  I was being to cautious with my original design, I was worried those would catch on the underside of the plastic breadboard or hit the walls and not open enough for larger wires. Turns out, that created the issue of leaving too much of a gap for things to get around the clip or catch on the edge.

  So I’m having the spring clip molds updated with a small adjustment:

  I’m just extending the arms by 0.25mm to hopefully act as a better guide for the wires as you stick them in.

  Now they should cover the entire opening to the breadboard and make it much harder to get a wire around it and possibly damage the clip.

  I know this doesn’t help people who already have them, and these probably won’t make it into the next batch being made, so you’ll probably start seeing these Q1 2024. I’ll set up some sort of trade-in program for people who are bothered by it and want the new revision. Or you can just ask me for a set of the new ones when they’re available and I’ll send them to you for free and you can solder in the new ones yourself.

  Anyway, just to take full advantage of my Fusion 360 student license’s free cloud rendering credits, here are a bunch of renders of the new clip revision.

  The reason that making changes to something like this is such a huge deal, is that they’ve made a big custom fourslide mold for this to do all the stamping and bending (here’s a SmarterEveryDay video about this exact process, just pretend everyone working there is Chinese.) So any adjustments to the part require them to CNC out parts of the mold and add extra metal bits on the mating surfaces. It’s an expensive process, this little edit will probably cost me ~$1,500-2,500 (or if I was doing this in the US, ~$60,000.) But it bothers me that it isn’t as perfect as it could be so I think it’s worth it.

  For reference, here’s what I sent to the tooling engineers at Shenzhen Fulimei BBNew DrawingRevisedClipsUpdated.pdf (393.8 KB)

  And the new drawing in case they decide to just make an entirely new mold bbSimpleWider Drawing v1.pdf (350.4 KB)

  And the STL for good measure bbSimpleWiderOpen v2.stl (342.6 KB)

  Let me know how much or little these clips are bothering you. If enough of you really hate it, I could hold up production on this new batch, have them dump the 40,000 clips they’ve made into the nearest wildlife sanctuary, and have them remake them all with this update.

• Jumperless Has Exploded

  Kevin Santo Cappuccio • 10/10/2023 at 01:32 • 0 comments

  So, apparently YouTube has deemed my Hackaday Prize entry video worthy to show to basically everyone ever. 

  Well, half of everyone...

  C'mon ladies and User-specified people, don't make my analytics look like a drawing of a dick. Jeez, we really need to work on getting more women into engineering, if you're a non-male reading this who isn't into engineering (seems unlikely given we're on Hackaday), it's really super fun, I promise.

  Anyway, now the Jumperless is backordered for a while

  So now this isn't so much an engineering thing as much as a manufacturing/logistics project. Which is also pretty interesting so I'm going to write a bit about it here. This should also be posted on Manufacturingandlogisticsaday.

  I have 50 coming in next week, which when I ordered them seemed like a lot. Now I'm working on getting an order together for 500, and I told them to hurry so I can hopefully get them in before Supercon. 

  The unknown variable is the spring clip manufacturer, Shenzhen Fulimei Technology Co. LTD. Their lead time is usually around a month, but they've been very helpful and awesome to deal with so they might be able to rush it a bit. Each board uses 80 clips, so for an order of 500, I'm going to need 40k of these things, it's crazy that I've been having to use engineering notation for real life objects lately.

  I was originally having these made by JLCPCB, and they always do great work. But they're kind of too big to be bothered with finals assembly stuff. So I turned to Elecrow. The reason I went to them was because we had already swapped boards, they reached out to sell the Jumperless in their store as a partner seller, and they had given me a couple TFT display boards to review. So I could just look at the board they sent and the manufacturing seemed pretty legit, and they could grab a Jumperless to make sure it looks like the ones from JLC.

  I was kind of worried about quality, those LEDs on the Jumperless have pads that are soooo close together, so the reflow has to be perfect. Normally you'd just turn the LEDs 90 degrees and they have a lot of clearance, but I wanted the long rectangular lens to line up with the slot in the clips. 

  I learned how touchy this was when I ordered the first batch from JLC. It was interesting that the main 4 layer PCBs were fine, while the 2 layer wishbone boards had a bunch of shorts. It seems like they build the more complex boards to higher standards, which makes perfect sense. And they had no places to probe for shorts on the wishbones.

  Here I am trying to reflow these back to life unsuccessfully
  

  Yes I melted the hell out of the lenses, I shoulda used a hot plate, but they were trash anyway. So I just redesigned this board with the LEDs rotated 90 degrees, which is the correct way.

  The point of all this, it's sketchy to switch suppliers, especially when you just YOLO a bunch of DRC violations. Let's hope they're good, but I have a lot of faith in Elecrow. Any board assembly house willing to take sandpaper to a bunch of clear LEDs to diffuse them for me clearly takes some pride in their work.

  I know what you may be wondering, will I have a bunch of these available at Supercon? The answer is hell yes.

  I have 7k spring clips right now, so worst case, I'll have them ship me a bunch of kits and you can assemble them yourself in The Alley.

  The advantage of dealing with me in person is that I'm a total softie who genuinely hates money, so if $300 is a lot to you and you seem cool, it's very easy to get me to give you one for free. Just use this verbal discount code, "Hey, I want one of these but can't really afford it." Boom, now you're a bonafide social-engineering hacker.

  ---

  To the Hackaday Prize judges or anyone else committed to reading all the text of this project, I'm sorry you had to read through my extremely long-winded ramblings. As a reward for getting through it, here's a picture of my dog (Quark will be at Supercon,...

  Read more »

• Ṭ̴̯̿̂h̶̫̏̀ę̵̙̒ ̷̩̉C̴̖̞̀͝ọ̵̬̎̔ḓ̵̓e̸̥̞̓̓ part 5 - The Wokwi Bridge App

  Kevin Santo Cappuccio • 10/04/2023 at 17:07 • 0 comments

  Table of Contents  (bolded ones are in this project log)

  • General terms - the names I've decided to call things
  • What's being stored - how the overall state is stored
  • Pathfinding - how we find valid paths for each connection
  • Controlling the switches - how we send that data to the CH446Qs
  • LEDs - how we choose unique colors for each net
  • The Wokwi bridge app - how we scrape the Wokwi page for updates

  
  So, I didn't know Python, but it sounded like the easiest way to scrape a webpage with Beautiful Soup. Coming from C, it really makes you appreciate the hardline greybeards that have strong opinions about what the language should and shouldn't be. Because Python is a mess. But I learned it anyway.

  What the app actually does

  Most of the parsing and stuff is done on the Jumperless itself. Mainly because I wanted it to be relatively app-agnostic, and because I'm way more comfortable with C++. So really all the app is doing is:

  • Using BeautifulSoup to scrape the webpage source of the Wokwi project every quarter of a second
  • Pulling out the diagram.json section of the page
  • Seeing if it's any different from the last diagram.json it pulled
  • If so, parses that down into a list of connections
  • Sends an 'f' over serial to put the Jumperless in "load preFormatted node list" mode
  • Then sends those parsed connections over serial

  Here's what the diagram.json looks like

  We don't actually care about most of the stuff in that json file, so we just parse out the things that are important. The parsed connections look like this

  11-105,
  13-105,
  13-46,
  15-44,
  43-100,
  100-2,
  100-2,
  45-25,
  38-44,
  32-44,
  22-24,
  20-19,
  21-23,

  The numbers in the 100 range are special functions, 100 = GND, 103 = 3.3V, 105 = 5V, etc.

  There's actually the same parser on the Jumperless itself, which I wrote first and then ported to Python. So you could just paste the whole diagram.json into the serial terminal and the Jumperless will figure it out. The main reason I'm doing parsing on the computer is that the serial buffers can fill up and it makes the updates feel less "snappy".

  Other things the app does

  When you open the app, it uses pySerial to look at all the things connected to USB. If one of them has Jumperless as the device descriptor, it automatically connects to that one and then moves along to prompting you for the Wokwi project link.

  It became annoying to paste the link in every time so now it stores links as a text file and lets you just select from a list if you're opening a project you've used before 

  The bridge app also has its own menu accessed by typing "menu", which is useful if you want to switch projects without closing and reopening the app.

  I guess it's kinda confusing, because the menu on top is coming directly from the Jumperless, while the bridge app menu is coming from the app itself. Hopefully the indenting and spacing hints at that fact. 

  Most of the code in the bridge app is just fighting with pySerial to keep the connection open and not crash when it gets unplugged. Especially when developing on this, I needed it to not crash when I flash new code onto the Jumperless from VScode/PlatformIO. So yeah, that works and it's very convenient.

  How I got it to run in a persistent terminal window is a bit of a hack. When you open the app, it actually just opens a bash script that launches the real app

  And here are the entire contents of jumperlesswokibridge

  #!/bin/bash
  # This is the launcher for OSX, this way the app will be opened
  # when you double click it from the apps folder
  open -n /Applications/jumperlesswokwibridge.app/Contents/MacOS/jumperlesswokwibridge_cli

   jumperlesswokwibridge_cli is where the real app is. The reason I had to do this is typically, when you open an app on a Mac, it just runs a script like this and then immediately closes that window. This is just to get around the closing part.

  Packaging

  This was kind of a nightmare, at first I was using pyInstaller but...

  Read more »

• "Any sufficiently extra technology is indistinguishable from a Barbie-Oppenheimer crossover meme" - Glittering USB Cables

  Kevin Santo Cappuccio • 09/29/2023 at 20:26 • 0 comments

  So Jumperless has a pretty specific color scheme, and it would be a shame to ship them with boring USB cables. 

  I figured I had to include a cable because USB Mini is pretty uncommon nowadays, even though it's the best USB port ever made, and I refuse to change my mind on that.
  

  Why not USB-C?

  I like USB-C, but sending regular USB 2.0 over a USB-C port feels like lying to me. It just comes off as janky if you're not using any of the extra functionality. 

  And also, I'm scared. If the Raspberry Pi Foundation screwed it up, I'm worried I might too. It's just unnecessary complexity that isn't really needed here.

  Why am I wasting time doing this?

  Because I came up with the idea while I was drinking, and decided that I should announce it publicly right then so I couldn't back out. 

  "Any sufficiently extra technology is indistinguishable from a Barbie-Oppenheimer crossover meme"
  
  I'm drunk and therefore decided that every Jumperless will come with a pink glittery USB Mini cable, and now I'm committing to it publicly so I can't change my mind. pic.twitter.com/CrqglTC6Si
  — Kevin Santo Cappuccio (@arabidsquid) July 8, 2023
  

  Anyway, I'm glad I did. I think it adds to the experience of opening a Jumperless. Every one I box up, I do it with the mentality of "I can't wait to see the look on their  face when they open this, they're gonna get so many retail-based endorphins shot right into their friggin' brain." And I hope they throw this box in the closet with all the Apple boxes everyone refuses to throw away. 
  

  If you want to do this yourself

  I tried a bunch of way more complicated ways to do these in batches like this

  and this

  But as it turns out, it's much easier to just do these one at a time. 

  First I mask off the metal ends of the cable with masking tape, then stretch them for a few days so they're less "kinky" with rubber bands. 

  This is the paint I'm using. It's the kind that bonds to plastic.

  Then I just hang them up and spray them, and while they're still wet, I dip them though my glitter pile. If you don't have a huge pile of glitter in your workshop at all times, what are you even doing with your life?

  Then I let them dry for like an hour, so the paint isn't fully cured. And go along and squish the glitter into the cable with my fingers really hard so the glitter lays flat and isn't so rough. Then rub all the extra glitter off with my fingers for a while. This gives them a nice smooth finish that kinda feels like a snake, instead of sandpaper. 

  Here's a long video of that whole process. 

  Woo, gittery USB cables. Now here's what all the stuff inside a Jumperless box looks like:

• Doom and Some Other Less-Trivial Demos

  Kevin Santo Cappuccio • 09/20/2023 at 20:25 • 0 comments

  A lot of these shots will be cut into the Hackaday Prize entry video, but I'm gonna post them here anyway so I don't feel like I've wasted time making these if I decide some of them don't fit.

  Doom Over a Jumperless

  Doom is the most click-baity demo you can do. And I support it (even though I suck at actually playing Doom)

  Someone on Twitter asked if the crosspoint switches would interfere with fast data signals. The answer is no, they won't, they're rated to 50MHz at 3dB rolloff. The physical breadboard will have a much larger effect at those frequencies, so if it works on a regular breadboard, it should work on a Jumperless (wrt frequency, current and voltage have their own limits). 

  This is the awesome project doom-nano which is stripped down enough to run on an ATMEGA328P at ~15 fps. Note that the enemies don't die when I shoot them, that hasn't been implemented yet.

  The nerd-sniper who got me actually was asking about SPI displays, I didn't have a Arduino Nano ESP32 at the time, but I will today (thanks Amazon). So expect a demo of real doom running on a color display soon. 

  16x2 LCD

  And my video light Fuck mask gets its time in the spotlight.

  Making this one revealed a bug in the routing code here it wasn't checking the other end of the "bounces" in certain arrangements. So yeah, 2 days of debugging for a 22 second video, that's approaching Kubrick's shooting-to-runtime ratio.

  Some 7400-Series Logic Stuff

  Here I threw together a random logic circuit with the chips I had laying around, and used a 555 as the clock source. Near the end, I take out the 555 and use the Jumperless's DAC making a square wave as the clock. Which might be useful if you're building just part of something and you don't want to screw around with the clock source.

  There's a simple text-based wave generator menu that I'm using to control the frequency and stuff. It looks like this.

  On the Wokwi project I had a potentiometer connected to the blue clock line, that's what tells the Jumperless that I want a DAC connected there.

  This is the same circuit again:

  Magic Flames Released

  This is the silly intro shot, same circuit as above (and part of it is redundant).
  
  Obviously, circuits don't blow up like that when you cut one wire. So let's look behind the curtain and see what I did 

  It's cigarette filter wrapped in NiChrome wire and submersed in a foil tray filled with vape juice hidden behind the breadboard then hooked up to a big 12V lead-acid battery when I wanted it to go off. I'm actually just cutting the 5V power in the video.

  This is what it looked like afterwards 

  Ha. 

  I also tried just cutting 2 jumpers connected to the leads of the lead-acid battery, but the sparks weren't dramatic enough and too quick to be shot on video. 

  Another attempt was made by emptying out the powder from a bullet and igniting it, but modern smokeless powder is, well, smokeless. Like really surprisingly so. I even mixed it with sugar and Ammonium Dichromate but it never really looked right. So vape juice it was!

  Crosspoint Superzoom

  This is just to give people a but of an understanding of what's going on inside a crosspoint switch. Not really a demo, but it was made so people understand that the Jumpeless isn't reading and simulating your signals, just passing them through an analog CMOS switch.

  If you want to play with that crosspoint demo in Falstad, here's the link to that circuit.

  And the transistor-level analog CMOS switch is here.

  Rail Selector Switch

  This is a fun little shot of the supply rails being switched in stop motion. 

  Anyway, I think that's all the video I have for now. But stay tuned for the Hackaday Prize entry video where I cut all this together and talk at you.

• Getting Started Using Your Jumperless

  Kevin Santo Cappuccio • 09/06/2023 at 17:26 • 0 comments

  Cool, so you have this super sexy object now. How do turn it into an actual prototyping tool? The answer is software.

  After you've unboxed (and maybe assembled) your Jumperless, we're going to need a way to talk to it. 

  Now, the Jumperless is very open and will accept netlists from any program with some basic formatting, if you hate Wokwi and want to use something else, this project log should give you an idea of what format it accepts over serial so you can write your own Bridge to any software you like. But for now, I'm focusing on Wokwi because I think it's better to have solid support for one workflow than shitty support for a bunch.

  First, we need to download the App and latest firmware here.

  Updating The Firmware

  I ship these with the latest firmware installed, so if you just received your Jumperless in the mail, you can skip the firmware update. But I usually push minor fixes to that firmware.uf2 file every few days, so it's probably worth doing anyway.

  On your Jumperless, there will be a little button on the opposite side of the USB port. This is the USB Boot button and works exactly the same as a Raspberry Pi Pico.  

  1. Hold the USB Boot button and plug the Jumperless into your computer. 
  

  2. A drive should pop up called RPI-RP2. Drag the firmware.uf2 file into it and it should reset and you're done!

  Installing the App

  I'm showing this on a fresh install of macOS, but Windows should be roughly the same.

  1. On the releases page, download JumperlessWokwiBridgeMacOS.zip (or the .exe for windows) and firmware.uf2
  

  2. It should automatically unzip in your downloads folder. Note that this won't run correctly from anywhere but your Applications folder, so drag it there.

  3. Click it to try to run it. Unless you've set your security setting to allow apps from anywhere, it's going to complain.

  4. Click Cancel and go to  Settings > Privacy and Security > scroll down and click Open Anyway

  5. It's going to complain again and just click Open

  Hot tip: run 

  sudo spctl --master-disable

  in Terminal to give you another checkbox for Anywhere under Settings > Privacy and Security > Allow Apps From. And you won't have to go through this again for other shoddy software.

  6. If everything goes well, you should now be presented with a Terminal window like this

  Note that on MacOS, it should just autodetect and connect to the Jumperless if it's plugged in when you start the app, if not, just plug it in and type 'r' to rescan the ports until it finds it. 

  Okay, now the app is set up, what do we paste into there to connect to our Wokwi project?

  Getting Wokwi Set Up

  You'll need a stable link to your Wokwi project, and it will only make one when you're signed in and have saved your project to "My Projects". After that the links are saved in a text file in the JumperlessWokwiBridge app and you'll be able to select projects you've used before from a list.

  1. Go to wokwi.com
  2. Click Sign Up/Sign In and enter your email (or use Google or Github)
     
  3. Click the link they email you to sign in
     
     
  4. Click Go To Your Projects, then New Project > Arduino Nano
     
     
     
  5. Click Save and give your project a name
      (note that the URL has now changed to a unique link)
  6. Click blue “+” (top center) to Add New Part and scroll down to Half Breadboard and click it
       It will put it somewhere random, so click somewhere that’s not a hole to drag it.
     
  7. Open the JumperlessWokwiBridge App and resize the windows so you can see both
     (on mac it will autodetect the port if it’s plugged in, on windows you’ll need to select the COM port here first, if the Jumperless wasn’t connected when you opened the app, press ‘r’ the Enter to rescan the ports)
  8. Copy the URL of the Wokwi project you just made
     
  9. Paste that URL into the Bridge App window and press Enter
     
     
  10. Name the project and hit Enter (it will save the link so next time you’ll only need to choose it from...

  Read more »

• Ṭ̴̯̿̂h̶̫̏̀ę̵̙̒ ̷̩̉C̴̖̞̀͝ọ̵̬̎̔ḓ̵̓e̸̥̞̓̓ part 4 - Picking Colors and Putting Them On Your Retinas

  Kevin Santo Cappuccio • 09/04/2023 at 18:00 • 1 comment

  Table of Contents  (bolded ones are in this project log)

  • General terms - the names I've decided to call things
  • What's being stored - how the overall state is stored
  • Pathfinding - how we find valid paths for each connection
  • Controlling the switches - how we send that data to the CH446Qs
  • LEDs - how we choose unique colors for each net
  • The Wokwi bridge app - how we scrape the Wokwi page for updates

  If you're wondering why you feel a strange sexual attraction to this board, I can give you a hint...

  I didn't want to do the LEDs at first because it seemed a bit out-of-scope. But after using the prototype board without them, I found that it involved a lot of counting rows to find where you're connecting things. And that gets pretty tedious. 

  Around the same time, I had ended my month-long search for anyone who sells just the metal spring clips from a breadboard and resigned to having custom spring clips made by Shenzhen Fulimei Technology Co. LTD. 

  Hot tip for makers that want a bunch of some thing custom made using a non-so-common process: put your drawings and requirements up on made-in-china.com, you'll get a ton of quotes within days and just pick your favorite. 

  I'm glad I did, because using this thing is sooo much smoother now, you really only have to look at the board for the first connection and then everything else can just be counted as an offset from there. Also, the new versions of the breadboard shell have every 5th embossed number raised (which is actually super weird on breadboards because they count from 1, so there's 3 holes between 1 and 5, and 4 holes between the rest, enjoy being bothered by that forever) which makes it even easier to locate where you're connecting stuff.

  How the colors are chosen

  It would be really cool if the colors would correspond to the colors in the Wokwi diagram, but there's a couple of problems with that.

  First:

  All the wires default to green, and having to select a unique color for each wire is kind of a pain in the current version of Wokwi. I know they'll eventually work on something to change this, but their voting system of which features they should work on next shows it's a fairly low priority.

  The other issue is this:

  Currently, they only support 15 HTML colors. So having only 15 different possible nets with unique colors (fewer, because black, grey, and brown wouldn't really show up on RGBs)

  So we're just gonna pick our own colors.

  The special nets have hard-coded colors, they are as follows:

    rgbColor specialNetColors[8] = {      
    {00, 00, 00},
     {0x00, 0xFF, 0x30},    //GND     - Green 
     {0xFF, 0x41, 0x14},    //5V     - Red leaning towards orange {0xFF, 0x10, 0x40},    //3.3v    - Red leaning towards purple 
     {0xeF, 0x78, 0x7a},    //DAC 0-5V- Pinkish White  (changes brightness and hue based on output magnitude) 
     {0xeF, 0x40, 0x7f},    //DAC +-8V- Purplish White (changes brightness based on output magnitude, hue for positive or negative) 
     {0xFF, 0xff, 0xff},    //Current Sense+ - Yellow 
     {0xff, 0xFF, 0xff}};   //Current Sense- - Blue 
     
     rgbColor railColors[4] = { 
      {0xFF, 0x32, 0x30},    //GND - Green 
      {0x00, 0xFF, 0x30},    //5V - Red 
      {0xFF, 0x32, 0x30},    //GND - Green 
      {0x00, 0xFF, 0x30}};   //5V - Red
  

  Here's what those look like:

  Note the bottom rail is 3.3V, top rail is 5V. pot1-sig is DAC 0, pot2-sig is DAC1.

  The colors are saved at full brightness and scaled down to the default brightness or the brightness you set in the menu when they're displayed.

  For the other nets, here's the general algorithm:

  • Get the number of unique nets and divide that by 255 (that's the full color wheel in the NeoPixel Library) to get a color distance
  • Check if the hue at (color distance * 1) is the too close to any of the special nets
    • If it is, add 1 to the number of unique nets and calculate a new color distance, then try again with an offset (color distance/2)
  • If not, set that hue for the net and check the next net at (color distance * 2) etc...

  Here's how...

  Read more »

• Ṭ̴̯̿̂h̶̫̏̀ę̵̙̒ ̷̩̉C̴̖̞̀͝ọ̵̬̎̔ḓ̵̓e̸̥̞̓̓ part 3 - Driving the CH446Qs

  Kevin Santo Cappuccio • 08/30/2023 at 03:14 • 0 comments

  Table of Contents  (bolded ones are in this project log)

  • General terms - the names I've decided to call things
  • What's being stored - how the overall state is stored
  • File Parsing - how we fill in those arrays
  • Pathfinding - how we find valid paths for each connection
  • Controlling the crosspoint switches - how we send that data to the CH446Qs
  • LEDs - how we choose unique colors for each net
  • The Wokwi bridge app - how we scrape the Wokwi page for updates

  
  Controlling the Crosspoint Switches

  What crosspoint switches crave

  Okay, so now we have all our paths filled out with what chips need to have which X and Y inputs connected to make the magic happen.

  The CH446Qs are basically clones of the MT8816, except for one important difference, they accept serial addressing. The datasheet is kinda vague about how, but it turns out it's just a kinda weird version of SPI. 

  Basically, all the chips see the same data signal, and whichever one sees a pulse on the STB when the last bit comes in will connect or disconnect the selected X and Y inputs. The state of the DAT line when the Strobe comes in determines whether it's connecting or disconnecting. That stretched out clock line shows that it doesn't care about real time, which comes in handy.

  PIO State Machine

  So I have to do something that's kinda like SPI but not quite, this looks like a job for the RP2040 PIO State Machines.

  Even knowing assembly, the learning curve for writing a PIO program is steep. The documentation is really hit-or-miss, the examples are uncommented and written like they're playing code golf, insanely terse. Like these people do realize you can name variables after what they do, right? And these are the Official examples in the datasheet. Anyway after a few days of staring at what looks like gibberish, it starts to click.

  I copied the SPI.pio example and edited it from there. Let me try to explain some of the things I learned to hopefully make it easier for you to write a PIO program in the future. 

  I'm just compiling this with the online pioasm compiler and then pasting the compiled code into spi.pio.h
  

  https://wokwi.com/tools/pioasm

  Here's where we are:

  ;this is basically spi but it sets a system IRQ on the last bit to allow the chip select pulse to happen
  
  
  
  .program spi_ch446_multi_cs
  .side_set 1
  
  .wrap_target
  bitloop:
  
      out pins, 1        side 0x0 [2]
      
      nop                side 0x1 [2]
  
      jmp x-- bitloop    side 0x1
  
      out pins, 1        side 0x1
  
      mov x, y           side 0x1
  
      irq  0             side 0x1
      
      wait 0 irq 0 rel   side 0x1
      
      jmp !osre bitloop  side 0x0
  
  public entry_point:                 ; Must set X,Y to n-2 before starting!
  
  
      pull ifempty       side 0x0 [1] ; Block with CSn high (minimum 2 cycles)
      
      nop                side 0x0 [1]; CSn front porch
  
  
  .wrap
  
  

  What wasn't explained well is what the hell a sideset pin is. Basically you do your normal-ish assembly code on the left, and then each operation also affects the sideset pin on the right. It's kind of a hack to allow you to control 2 pins in a single clock cycle. In this case, the sideset pin is attached to the CLK, and pins, 1 is DAT.
  

  So, whats going on is that in the regular code, I'm sending a byte to the sm register with this line
  

  pio_sm_put(pio, sm, chAddress);

  (the last bit of chAddress is set to 1 or 0 depending if I want to connect or disconnect)

  and that pull ifempty will pull in a byte to the working register and send it out one bit at a time while toggling the clock. When it's out of data to send, it triggers a system interrupt request that can be seen outside of the PIO state machine and I deal with it in an ISR in CH446Q.cpp

  At this point, here's where we are in the timing diagram:

  Now we need to select the correct CS line to make the right chip make the connection

  void isrFromPio(void)
  {
    switch (chipSelect)
    {
    case CHIP_A:
    {
      digitalWriteFast(CS_A, HIGH);
      break;
    }
    case CHIP_B:
    {
      digitalWriteFast(CS_B, HIGH);
      break;
    }
    case CHIP_C:
    {
      digitalWriteFast(CS_C, HIGH);
      break;
    }
    case CHIP_D:
    {
   digitalWriteFast(CS_D,...

  Read more »

• Ṭ̴̯̿̂h̶̫̏̀ę̵̙̒ ̷̩̉C̴̖̞̀͝ọ̵̬̎̔ḓ̵̓e̸̥̞̓̓ part 2 - Pathfinding

  Kevin Santo Cappuccio • 08/25/2023 at 01:37 • 0 comments

  Table of Contents  (bolded ones are in this project log)
  

  • General terms - the names I've decided to call things
  • What's being stored - how the overall state is stored
  • File Parsing - how we fill in those arrays
  • Pathfinding - how we find valid paths for each connection
  • Controlling the crosspoint switches - how we send that data to the CH446Qs
  • LEDs - how we choose unique colors for each net
  • The Wokwi bridge app - how we scrape the Wokwi page for updates

  Pathfinding

  This is the really tricky part. I probably wrote all this code about 4 times, trashed it and started over from scratch with only the lessons learned from the last attempt. Earlier versions would add connections one at a time, but you'd end up in weird states because it has no knowledge of what other paths it needs to make room for. So the final version here clears the connections from the last update, takes in all the connections to be made, and finds paths for the whole board every time you add a new wire. All the old connections usually follow the same paths as last time unless they need to be nudged over to make room for some other path, and the actual connection won't be interrupted at all.

   Here's the schematic of just the crosspoints, the Nano header, and the breadboard.

  If you look closely, you'll see that there generally 2 connections (I'm calling these 2 connections Lanes between each breadboard chip, except for the chip that is across from it on the breadboard. And every breadboard chip has one connection to each of the special function chips. The pins on the Nano header has a connection to 2 special function chips (interleaved to make it easier to connect continuous pairs of pins to the breadboard).

  Here's the high level outline of what NetsToChipConnections.cpp is doing

  • Sorts all the paths by Net This sort of sets priority, lower net numbers (so all the special function nets) will be picked first and are more likely to have direct connections chosen
  • For each path, find the start and end chips
    • If there are multiple candidates (Nano header pins will have 2) store both
    • If both start and end chips have candidates in common, choose that chip (this would make it a bounce)
    • Assign node and path types (BB to BB, NANO to BB, BB to SF, etc...)
    • Sort a list of chips from least to most crowded (by how many connections that chip has used)
    • Resolve the candidate chips by going down the sorted list of chips and picking the less crowded chip
    • Search for a direct path between those 2 chips
      • If there isn't one, swap to the other candidate chips and search again
      • If one of the nodes is a special function with multiple options swap the nodes with their equivalents and search again
      • If there still isn't a direct path, set the altPathNeeded flag and move on At this point, any paths that have a simple direct connection should be done, now we need to deal with the ones that don't
  • Resolve alt paths, if the altPathNeeded flag is set
    • Search through all the other chips until you find one that has a direct connection to both the start and end chips
      • If one chip is connected to the X inputs and the other the Y inputs, set that connection on chip[2] and x[2] y[2]
      • If they're both on X or both on Y, set the sameChip flag and the x[3] or y[3] as -2 to denote that that connection is a bounce and it doesn't matter which pin is chosen, as long as it's available
  • Resolve uncommitted hops, anything set as -2 gets a random unconnected pin assigned to it at the very end so it doesn't take up connection space

  There's a lot more subtlety to this but if I go into any more detail you might as well just read the code itself. It will all be in the file NetsToChipConnections.cpp, and if you're running it on a Jumperless or just an RP2040, you can set the Chip Connections and Chip Connections Alt debug flags and it will show you everything it's doing in a somewhat nicely formatted way. There are comments in the code but there are a lot of nested array things that can get pretty confusing, if...

  Read more »

• Ṭ̴̯̿̂h̶̫̏̀ę̵̙̒ ̷̩̉C̴̖̞̀͝ọ̵̬̎̔ḓ̵̓e̸̥̞̓̓

  Kevin Santo Cappuccio • 08/18/2023 at 18:11 • 0 comments

  I'm going to do a high-level explanation of what the code in the Jumperless is actually doing. There's a lot going on and it's in a bunch of separate files so I think it will be helpful for people who what to understand or improve upon it.

  Table of Contents  (bolded ones are in this project log)

  • General terms - the names I've decided to call things
  • What's being stored - how the overall state is stored
  • File Parsing - how we fill in those arrays
  • Pathfinding - how we find valid paths for each connection
  • Controlling the crosspoint switches - how we send that data to the CH446Qs
  • LEDs - how we choose unique colors for each net
  • The Wokwi bridge app - how we scrape the Wokwi page for updates

  This is going to be really long and so I'll be filling out parts as I finish them in no particular order.

  General terms

  I've made up terms for things here that may or may not be the formal definition, so I should probably let you know what I chose.

  Breadboard Chips - This refers to the 8 CH446Q crosspoint switches (labeled A-H) that have their Y pins connected to the breadboard. This excludes Chip L which actually has it's X pins connected to the 4 corners of the board (rows 1, 30, 31 (b1), 60 (b30))

  Special Function Chips - This refers to the 4 crosspoints (labeled I-L) that connect to everything else; the Nano header, power supplies, DACs, GPIO from the RP2040, etc...

  Nodes - Also used synonymously with Row especially when it's on the breadboard or Nano Header. And end point to a bridge

  Bridges - Just 2 nodes that should be connected

  Nets - Groups of nodes and bridges that should all be electrically connected to each other

  Bounce - Sometimes there won't be an available path directly from one node to another, so in this case it will pick another chip with a free path to the start and end chips and "bounce" through it.

  Paths - Similar to a bridge, except that it contains data for how that bridge is connected. So it will have which chips and which X and X pins are needed to make the connection

  Defines

  You'll see a lot of these, they're all in JumperlessDefinesRP2040.h. But the point of this whole this is so you don't have to dig through the code, so I'll put the abridged version here:

  #define CHIP_A 0
  ...
  #define CHIP_L 11
  
  
  #define t1  1
  ...
  #define t30 30
  
  #define b1  31
  ...
  #define b30 60
  
  
  #define NANO_D0  70 //these are completely arbitrary
  ...
  #define NANO_A7  93
  
  
  #define GND  100 #define SUPPLY_3V3  103
  #define SUPPLY_5V  105
  
  #define DAC0_5V  106 #define DAC1_8V  107
  
  #define CURRENT_SENSE_PLUS  108
  #define CURRENT_SENSE_MINUS  109
  
  #define ADC0_5V 110
  #define ADC1_5V 111
  #define ADC2_5V 112
  #define ADC3_8V 113
  
  #define EMPTY_NET 127
  
  

  What's being stored

  There are a few big arrays of structs that store the overall state of everything. Here are the main ones:

  chipStatus

  This stores the actual hardware layout of each of the 12 crosspoint switches, like what is physically connected where and whether that path is being used. In the code it's and array called ch[12] and it's in MatrixStateRP2040.h

  //the struct
  struct chipStatus{
  int chipNumber;
  char chipChar;
  int8_t xStatus[16]; //store the bb row or nano conn this is eventually connected to so they can be stacked if conns are redundant
  int8_t yStatus[8];  //store the row/nano it's connected to
  const int8_t xMap[16];
  const int8_t yMap[8];
  };
  
  //the array of those structs
  struct chipStatus ch[12] = {  {0,'A',  {-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1}, // x status  {-1,-1,-1,-1,-1,-1,-1,-1}, //y status  {CHIP_I, CHIP_J, CHIP_B, CHIP_B, CHIP_C, CHIP_C, CHIP_D, CHIP_D, CHIP_E, CHIP_K, CHIP_F, CHIP_F, CHIP_G, CHIP_G, CHIP_H, CHIP_H},//X MAP constant  {CHIP_L,  t2,t3, t4, t5, t6, t7, t8}},  // Y MAP constant
  ... {10,'K', {-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1}, // x status {-1,-1,-1,-1,-1,-1,-1,-1}, //y status {NANO_A0, NANO_A1, NANO_A2, NANO_A3, NANO_D2, NANO_D3, NANO_D4, NANO_D5,...

  Read more »

View all 11 project logs