<galibert[m]>
I thought it was still under development
<galibert[m]>
Is there a doc somewhere telling how one is supposed to use vio and vsense? I can't find one
<galibert[m]>
Is it just "put the +5V on vio if your signals are 5V, don't use vsense unless you want a continuous measurement of a given voltage"?
<wiebel[m]>
My understanding is that it is up to you, you can use it for the votage mirroring, so put it on the Vcc of the target circuit, still allowing to power a specific part. or use it as a watchdog to chek if the provided voltage get's where it needs to be.
<wiebel[m]>
s/votage/voltage/
<wiebel[m]>
* My understanding is that it is up to you, you can use it for the voltage mirroring, so put it on the Vcc of the target circuit, still allowing to power a specific part, or use it as a watchdog to check if the provided voltage gets where it needs to be.
<galibert[m]>
So I should not connect the +5V of the target circuit to the vio pin?
<wiebel[m]>
It depends on your applet, for selftest you bridge it to Vcc. I have not used it at all, yet.
<wiebel[m]>
I was lucky and had a bmx280 board laying around, still too lazy to solder. ;)
<galibert[m]>
I want to connect to the extension connector of a Yamaha expander, which has midi, i2s-like, and of course gnd and 5V
<wiebel[m]>
I'm sure you can leave out the Vsense until you want to use it in any meaningful way.
<wiebel[m]>
Besides the --mirror-voltage is just a genius way in itself.
<galibert[m]>
So... I should put the 5V on vsense and let the glasgow generate its own 5V?
<wiebel[m]>
You can but you don't need to, simply use Vcc from the glasgow and tell it to use 5V and completely forget about Vsense, simply leave it dangling around.
<wiebel[m]>
At least that's what I did until now.
leper- has joined #glasgow
urjaman has joined #glasgow
embeddedpenguin[ has quit [*.net *.split]
urja has quit [*.net *.split]
leper has quit [*.net *.split]
dx has quit [*.net *.split]
flummer has quit [*.net *.split]
leper- is now known as leper
dx has joined #glasgow
flummer has joined #glasgow
embeddedpenguin[ has joined #glasgow
<galibert[m]>
well, time to make my custom applets now :-)
<fridtjof[m]>
Assembled one of jkominek's breakout boards with some slight modifications to accomodate a generic fx2la :3
<wiebel[m]>
I have connected a bluepill and ran run swd-openocd -V 3.3 tcp:localhost:1337 after that I tried to use target remote localhost:1337 in arm-none-eabi-gdb which was noted by glasgow by ... socket: new connection from [::1]:48182 but then nothing happened in gdb. Any obvious caveat here?
<wiebel[m]>
* use target extended-remote localhost:1337, * connection from \[::1, * [::1\]:48182 but
<wiebel[m]>
* I have connected a bluepill and ran run swd-openocd -V 3.3 tcp:localhost:1337 after that I tried to use target extended-remote localhost:1337 in arm-none-eabi-gdb which was noted by glasgow by ... socket: new connection from [::1]:48182 but then nothing happened in gdb. Any obvious caveat here? Ah I'm sorry I missed the most useful help of the applet itself.
<wiebel[m]>
* I have connected a bluepill and ran run swd-openocd -V 3.3 tcp:localhost:1337 after that I tried to use target extended-remote localhost:1337 in arm-none-eabi-gdb which was noted by glasgow by ... socket: new connection from \[::1\]:48182 but then nothing happened in gdb. Any obvious caveat here? Ah I'm sorry I missed the most useful help of the applet itself.
<wiebel[m]>
To provide something useful: git clone https://github.com/openocd-org/openocd && cd openocd && ./bootstrap && ./configure --enable-remote-bitbang && make && sudo make install