DIY Mutable Unsuccessful Builds

[cordoba899]

Evening friends,
I think I traced down my error to a short caused by a connection from one thonkiconn hole to ground. It seems to be caused directly under the jack, on the other side of the pcb, so no super easy fix sadly. Does someone have tips on how to best desolder jacks? I have a hot air station if that helps. I read that one way is to just cut the jacks with pliers and then remove the stem as usual - is there a better way? Cheers!

[Altitude909]

Evening friends,
I think I traced down my error to a short caused by a connection from one thonkiconn hole to ground. It seems to be caused directly under the jack, on the other side of the pcb, so no super easy fix sadly. Does someone have tips on how to best desolder jacks? I have a hot air station if that helps. I read that one way is to just cut the jacks with pliers and then remove the stem as usual - is there a better way? Cheers!

Set the hot ar to 325C and heat the back of the jack until it lifts out EASILY. do NOT try to force it out, once it reflows it should pretty much drop out

[Mu Meson]

TIts currently broken on windows10 (i just tried it on a clean machine) and there is no reverting to Vbox 5 since windows now blocks that as a security hazard. The current Vagrant and virtualbox combination do not work out of the box. I managed to fix it somehow and havent touched it since but I cant tell you how i did it. I was some permission thing, if you boot the VM through virtualbox and watch where is craps out, that should point you in the right direction.

I completely reinstalled the environment - vagrant, git, VirtualBox, all of it.. I even managed to downgrade the VirtualBox to 5.2.44 - perhaps I could do this because I have Windows LTSC Enterprise 10 V1809 and it is less locked down. Of course this may mean I have a different weird problem that 'normal' Windows does not have. When I run up the VM in GUI mode I get this :

I have full rights to the /vagrant directory and am running the command box as an administrator



I think I need to accept vagrant /destroy ... vagrant up and waiting ten minutes .. it's not the end of the world but now I have spent a whole day trying to fix it..

[Altitude909]

yeah, i spent two. I should have written down what the fix was, but clearly its due to that "An error occurred while mounting /vagrant" bit

It was something with the guest permissions. Maybe try this: https://github.com/dotless-de/vagrant-vbguest

[funkytransport]

I was thinking that at first, these dual colour LEDs are quite sensitive to the currents going into each colour to make them look sufficiently distinct. But, Plaits only ever lights one colour at a time during normal operation.

You did get common anode ones, right? Pretty much all other modules run common cathodes, I missed that myself before.

FIXED!

both these modules had booted into colourblind mode first. very strange. all working now.

[mossa]

(I’ve managed to lock STM32s when messing around with eg the serial ports or doing silly things with them in hardware). You can use openocd try something like this:

init
reset halt
stm32f4x unlock 0
reset halt
exit

Ive been trying to figure out how to use openocd since im a noob with programming. I created a file called ocd-unlock.cfg which contained the code you provided. However the target file has some errors in it and im unsure how it can be fixed. Any ideas how I can solve this or am I doing it all wrong? (Couldn't find a single useful tutorial out there)

[Spastic_Colon]

Any thoughts appreciated

Hey all, Trying to get to the bottom of a couple of issues with my Stages build. Output 3, and 4 LEDs are non responsive. I've tested them with a multimeter and both work as they should. I've also got some strange voltages going on. All outputs are kicking out around 10v, except for output 3 which is approximately 5v. I have successfully flashed the STM, and the module enters calibration mode as it should. i've checked and confirmed continuity on N$6, N$9, N$10 and N$43 pins from the LED driver. Some photos below for references.

I did wonder if I've perhaps misread something, or made a mistake from Forest Caver's excellent flashing and calibration notes that might explain the voltages, but have triple checked and I believe I'm following them to the letter.

Just wondering if anyone else has experienced any similar weird behavior with their builds? Thanks a million in advance for any ideas, pointers, or general comments if you think I'm missing anything glaringly obvious!

[bawbag]

Take a look at the parts I highlighted. Seems like a dry joint and a couple of under-soldered connections

[Mu Meson]

yeah, i spent two. I should have written down what the fix was, but clearly its due to that "An error occurred while mounting /vagrant" bit

It was something with the guest permissions. Maybe try this: https://github.com/dotless-de/vagrant-vbguest

Nope VBGUEST didn't fix it, and neither did loading the file system drivers that get mentioned in the same thread...

However yey I fixed it ..

After building the VAGRANT environment, when the VAGRANT VM is booted the first time (which is the only time it works, thereafter the VM fails because it can't mount /VAGRANT) at the end of the boot sequence there is a message telling you that Ubuntu is out of date and inviting you to update it. I didn't do that because I was worried I might rip up dependencies inside the environment. However, if you run the update it fixes the /VAGRANT mount problem and the environment still seems to work. I have built some source and flashed a Branches and it looks good. This is with all the latest versions of Virtual Box and Vagrant loaded.

[Altitude909]

Well shit. I didnt do that either for the same reason. Will confirm over here..

*edit

confirmed

I think that actually was the fix I used here the first time since it remember it taking forever to upgrade

[atari5200]

I have a Plancks that I think I've borked, looking for a little troubleshooting advice.

Since I'm a dummy I installed the MB1S rectifier backwards and plugged in my otherwise meticulously constructed module...obviously it didn't work, and once I unplugged it and gave it a once over I realized what I had done. I popped in a new MB1S just to be on the safe side and tried it again and still no go. I'm just measuring about 1V on the + terminal of the MB1S, and 11.9ish V on the - terminal which I assume that is close enough for my purposes so it seems the + side is the issue.
This is a densely populated board and has a lot of components, any thoughts on where I should start troubleshooting? There are no shorts in the power section but something is clearly fried due to my previous mistake. Before I replace all the other power components any idea how I can narrow it down? I'm getting pretty much the same measurements at the other positive voltage regulators. Beyond the power section, is it likely the IC chips are fried as well due to my initial mistake?

EDIT: I think my biggest issue is that I'm not sure how to start troubleshooting when I'm getting incorrect readings everywhere, even the new parts that I replaced so I assume they *should* be working correctly...

[Spastic_Colon]

Take a look at the parts I highlighted. Seems like a dry joint and a couple of under-soldered connections

I’ll give it the once over tomorrow. Thanks for taking the time