<_whitenotifier-1>
[Glasgow] marcan commented on issue #96: Level shifter state during reconfiguraiton? - https://git.io/fjTu6
<_whitenotifier-1>
[Glasgow] marcan closed issue #96: Level shifter state during reconfiguraiton? - https://git.io/fjTui
<_whitenotifier-1>
[Glasgow] marcan commented on issue #106: Pulls on revC0 are BROKEN and I²C level shifters require replacement - https://git.io/fjTuP
<_whitenotifier-1>
[Glasgow] marcan closed issue #106: Pulls on revC0 are BROKEN and I²C level shifters require replacement - https://git.io/fjTuX
rohitksingh has quit [Ping timeout: 250 seconds]
rohitksingh has joined ##openfpga
azonenberg_work has joined ##openfpga
gsi__ is now known as gsi_
azonenberg_work has quit [Ping timeout: 272 seconds]
Asu has joined ##openfpga
<_whitenotifier-1>
[GlasgowEmbedded/Glasgow] marcan pushed 2 commits to master [+0/-0/±4] https://git.io/fjTz9
<_whitenotifier-1>
[GlasgowEmbedded/Glasgow] marcan d2af97c - revC1: fix old value/datasheet for PCA6408, style fixes
<_whitenotifier-1>
[GlasgowEmbedded/Glasgow] marcan 154ebbd - Make Sync pull-up 1K
<_whitenotifier-1>
[Glasgow] marcan closed issue #104: Indicate 10/12-bit ADC and DAC as functional equivalents to the 8-bit ones - https://git.io/fhjiK
<bubble_buster>
just curious, does anyone know what _whitenotifier-1 is doing to make these messages have a blue highlight background on irccloud? is it like /me? they look kinda like my own messages or messages where someone pings me, never seen that before
<bubble_buster>
also monospace font where other messages are not
<whitequark>
it's called a NOTICE
<TD-Linux>
^
<bubble_buster>
interesting, that's an irc thing? or freenode specific? is there a command for it? is there a mode that allows only _whitenotifier-1 to do it?
<whitequark>
irc thing
<whitequark>
it's in the protocol
<whitequark>
your chat client might or might not have a command
<whitequark>
like this
<whitequark>
i typed "/notice ##openfpga like this"
<bubble_buster>
neat, thanks
<bubble_buster>
test
<hl>
the NOTICE command was added to IRC during its development AFAIK to prevent messaging loops: the rule is that automated messages are supposed to use NOTICE. The idea is that any bot which responds to messages sent to it shouldn't respond automatically to NOTICEs; in this way, this prevents the situation where two bots start messaging one another in an infinite loop, babbling at one another forever
m_w has joined ##openfpga
<hl>
</random-IRC-history-lesson>
<whitequark>
yep
<bubble_buster>
yeah I was gonna ask the history but I felt I had asked too much already :D
<bubble_buster>
reminds me of the CC the whole company and everyone auto replies all story
<m_w>
mithro, was there some magic required to get USB working on the fomu/ice40up5k?
* emeb
listens too
<m_w>
mithro, I am working on an ice40 badge for the fossi latch-up conference and want to ditch the FTDI to keep the cost down
<m_w>
guessing that the frequency of the oscillator is part of the magic
<q3k>
iirc the main problem was that the up5k is slow
<tnt>
m_w: make it 12M
<q3k>
so it was mostly hdl work
<tnt>
q3k: Not really ... the original core was just slow because it was not written with speed in mind, but now there is at least 2 USB cores working just fine on up5k.
<tnt>
m_w: also, input on pin 35
<emeb>
m_w: tnt has a USB core building on up5k and I've gotten it running on my board too. Works OK but needs a soft CPU to drive it (with firmware) so it's not quite so plug-n-play as the TinyFPGA one.
<m_w>
so it is bitbanging USB?
<m_w>
like VUSB?
<emeb>
Nah
<emeb>
It's a full-up honest serdes in HW
<tnt>
m_w: no, it's just the higher level of USB running in the softcore. Pretty much exactly like you find on microcontroller supporting USB. All the low level time critical thing is implemented in hw, but all the higher level is sw based so you can implement any kind of device you want with just sw changes.
<emeb>
But TinyFPGA one has a hard-coded state machine to handle the protocols, while tnt's relies on the CPU to do that.
<tnt>
The orignal bootloader was hardcoded for a CDC ACM connected to a spi bridge and nothing else.
<m_w>
that makes sense
<m_w>
anyone up for a schematic review once I crust in the USB stuff?
* emeb
waves
<tnt>
sure
<m_w>
cool I have been using kicad for the design and will post a PDF for the review on github
<emeb>
fun
<m_w>
should I use a microb USB connector or once of those A types shaped to plug the board straight into your host post?
<q3k>
usb C
<m_w>
ha on a ice40up5k?
<tnt>
C can carry FS
* emeb
only has one USB C cable. :P
<emeb>
only just started getting used to micro and now they change it again.
<emeb>
<tortoise mode>
<tnt>
I still use mini so ...
<emeb>
my favorite mini jack is very easy to hand solder. the micro works best when reflowed so it's more of a PITA to build.
<bubble_buster>
I only buy things with usb c ports. can't wait for TinyFPGA EX :D
<mietek>
tnt: remember our conversation a few days ago?
<mietek>
tnt: you said "any nmos", so i got a couple BS170
<mietek>
tnt: but i’m not sure if it’s working the same way as i would expect a transistor to work, for an open collector signal
<m_w>
tnt: any specific pins that should be used for USB_P/N?
<emeb>
I just picked a couple that were on the correct side of the part - worked OK w/ tnt's code.
rohitksingh has quit [Ping timeout: 246 seconds]
<tnt>
m_w: you might want to use some in the same IO tile. Not a strict requirement though, just helpful to leave other pins free to use any clock they want.
<tnt>
mietek: I remember. it should work the same-ish.
<mietek>
tnt: i built a simulation in circuitlab.com
<m_w>
tnt: well they are all open now so I will pick two that are adjacent and on the same block
<mietek>
the switch turns on the transistor after half the time, and both voltages go low — so this seems to work
<tnt>
what this simulation doesn't show is your 2n3904 going up in flames.
<mietek>
okay
<mietek>
unfortunately circuitlab doesn’t seem to have a nmos part
<tnt>
I ... can't believe this.
<mietek>
it has MOSFETs and JFETs
<tnt>
nmos = n-channel mosfet ...
<mietek>
yes, and so i replaced the transistor with a MOSFET
<tnt>
yes.
<mietek>
and i can’t reproduce the same behaviour
* m_w
wonders why fomu design files aren't available
<tnt>
Also, jfyi you transitor circuit above is going to catch on fire because a base -> emitter junction on an NPN is basically a diode, so you're shorting your 3v3 to gnd basically which is going to burn as much power in that transistor as your power supply can provide. For transistors you need a reistor on the base to limit the base current.