Altitude

Members
  • Content count

    1,182
  • Joined

  • Last visited

Community Reputation

57 Excellent

4 Followers

About Altitude

  • Rank
    MIDIbox Guru
  • Birthday 02/22/1975

Profile Information

  • Gender Male
  • Location Lansing, MI
  1. any 10 pin female header that style will work, the height on that one wont matter
  2. no compensation needed. I know how these things go. I wish I could have found the actual spot where it was shorting, it definitely wasn't a board problem since I did inspect the underside pins after I cleaned it off  and it worked with the new header so that only leaves the solder bridge and that fits the symptoms.   Checking for shorts to adjacent I/O pins would have identified the issue, might be worthwhile to spot check a couple in inventory to make sure it was just a fluke and not a batch thing. anyway, that's that.  
  3. Solved! And this is some crazy ass shit too: I was friction fitting the core with the mainboard to see if removing the TVS fixed it (it didnt) so the plan was to try the temporary headers like andy suggested with the minimal setup but my trimmed down, solder coated ones were not fitting the sockets i had so I decided just to put new headers on the core, not a big deal, suck out the solder and pull the pins out one at a time.  When I did the first row and pulled off the plastic header there was a fair amount of solder where the plastic was (like it puddled there).  I just ignored it thinking it was from the desolder gun and cleaned it all up but after the clean up, and new headers, it fired right up.  In hindsight, there was way more solder there than should have been, I was sucking out solder through one end and pulling the pin out through the other, what was left there after I removed the plastic was in the shape of the plastic header like a mold, there is no way that came from the desolder gun especially since it sucks solder out or from any other soldering I did since those were on the other side of the header.  I checked all the IO pins for shorts to ground and +5 but NOT to each other which seems to be what was happening here, must have happened in the wave machine when those headers were soldered on at the factory. Just dumb luck i decided to replace those, I would have never found it otherwise, should have taken a picture  
  4. tried 3 different ones
  5. good idea.  I want to triple check everything before I put the core back on.  I use the same diode in a couple device i sell but the list of possible suspects is getting short.
  6. BLM 16x16+X build guide

    was the alt-page thing ever fixed?  so you could scroll up and down in note view?
  7. I cant find anything wrong with the connections on the mainboard, no shorts, no weird resistance.  Here's pics of the core.  Yes I am aware its set to USB (i was testing it without the mainboard)  
  8.   >..Before you desoldered the Waveshare daughterboard, i would have guessed the STM32F4 might have been a dud, maybe bad flash memory... But if it starts up and boots the app when powered by mini USB, that's clearly working. And as you said, it must be some connection to the USB port... I thought that too so I swapped the STM chips and it behaved the same way so it wasnt the chip.  That was further proven when I took the core off and that worked by iteself.  Its something on the mainboard thats hanging it up..   >did you have the onboard Waveshare power switch moved from "USB" to "5V In", when it was installed in the LoopA core? yes.   now that the core is off I'll trace back to the USB socket when I get some time.  Either its something stupid that I missed (likely) or some weird edge case issue (unlikely)
  9. >  Was the v407 breakout actually soldered in? If so, impressive that you managed to get it out so well! Yeah, it wasnt fun.  Hot air FTW  
  10. ok, some more developments. > Could you try to use another computer and another USB cable for uploading? tried it, no change in behavior.  >  could you try to enter bootloader hold mode and try to reflash from there? Just got this tip from Robert. You'd need to populate JPA0 and R101 and R102 on the core board and jumper JPA0 - then you should see the bootloader in MIOS studio and could hopefully try to upload again. Just to clarify, I have always been able to see the bootloader ports and upload code.  It will occasionally (like 1 out 20 times) start the app with the miniusb directly connected to the core otherwise only the main usb goes as far as the bootloader ports showing and accepting an upload but beyond that its not working right, I cant send commands through MIOS studio.  It just does nothing when I enter commands other things i tried: wipe the core, reflash the bootloader with the STlink (no change in behavior) Change the STMF407 (no change) I finally pulled the core off and that tried that by itself and it fired right up with the mini USB (Loopa midi ports available), and normal MIOS Studio terminal behavior so it looks like the issue is somewhere on the main board that's halting the core.  Ive gone over it several times and dont see where the issue is, need a fresh set of eyes.  
  11. Im not sure where to go from here.   1. Power good.  5V and 3.3V where marked 2. rehit all joints on the header, no change 3. Orientation of TVS is correct 4. 22R resistors are fine 5. Tried various USB cables/multiple computers   Other observations:  the app started once.  This was with the mini USB direct to the core, i could not repeat this behavior I can no longer get the miniUSB to do anything, it will start the device since the power led will fade in and out but no USB devices show up nothing is coming out of the midi ports with the main USB connected, I get the upload request over USB and feed back when I send the hex but I cannot send any other console commands to the bootloader (i.e."help" does nothing) Does your core = the STM discovery core? As in does it take the same bootloader?
  12. Tried all those already including reflashing the bootloader. I'll go over the core header again
  13. > could you check if you're using the newest MIOS Studio 2.4.9? Check. >Another idea - are you by chance using a Mac no >connect a mini-USB Cable to the waveshare daughterboard Ok, here's where it gets weird.  That DOES work.  The app will boot and I will get the Loopa ports now.  So that means that the main USB seems to be working but there is something hanging up the core preventing it from starting correctly.    
  14. yeah, its right.  This is weird, its like there is something up with the hex file.
  15. when I'm programming the core, I cant seem to get the program to stick, I see the ports in the MIOS studio, I can query the core, get the upload request and I can send the project hex but after its done and I power cycle it, i'm right back to the bootloader like there is no app, thoughts?   PS: Peter, you should look into a side hustle doing ASMR stuff