Page 1 of 1
Using Swordfish With MikroBUS Click Adapter Boards
Posted: Sun Jan 06, 2019 3:16 pm
by Jerry Messina
I've recently been playing around with some of the mikroE Click boards. These are really handy for putting together prototypes and one-of systems.
I put some example code on the
user modules wiki if anyone wants to give it a shot.
Right now it's mostly just simple code to check out the I2C, SPI, and UART mikroBUS connections, but it'd be nice to do a family of libraries.
There are a LOT of boards to pick from... anyone interested? If so, what would you like to see?
Re: Using Swordfish With MikroBUS Click Adapter Boards
Posted: Wed Jan 09, 2019 5:46 pm
by bitfogav
Thanks for sharing this information Jerry, I've got several Click boards from LED displays to some sensors I been meaning to play with, I'll have to dig them out
Re: Using Swordfish With MikroBUS Click Adapter Boards
Posted: Thu Jan 10, 2019 11:11 am
by Jerry Messina
Do you know how you're going to interface to them?
One of the hardest parts I found was trying to match up the mikrobus pin mappings vs the devices on some of the development boards.
I couldn't find one overall winner... each seemed to have their own pros and cons.
Re: Using Swordfish With MikroBUS Click Adapter Boards
Posted: Fri Jan 11, 2019 5:47 pm
by bitfogav
I have the MikroE UNO Click shield and a Firewing PIC18 board Jerry, I haven't looked at the corresponding pin mappings yet though.
If all the pin mappings doesn't match up then I might make my own UNO Shield for the Firewing PIC18 board, which I'll be happy to share or at least share the PCB Gerber files
Are these the only problematic issues?
1.mikroBUS uart is connected to UART1, which is normally used by the FW18 USB-UART main board.
2.mikroBUS INT_D2 and INT_D3 signals connect to the FW18 board ICSP RB7 and RB6 pins, so using the ICD is problematic.
Re: Using Swordfish With MikroBUS Click Adapter Boards
Posted: Fri Jan 11, 2019 6:49 pm
by Jerry Messina
So far that's all I've run across. If you do the mods I documented to the mikroe UNO shield it "fixes" both those issues, but I've only tried a few modules so I don't know what else may be problematic (no PWM or ADC for example).
The UART one is the biggest headache. I didn't want to loose the FW USB-UART (since that's the main way to communicate to the boards),
and I couldn't find a good generic way of remapping/reconnecting the pins so that you could use UART2 for the mikrobus UART without losing something else.
Device-wise, the 26/27K40 (and Q10) were the best choices I've found. They have two uarts and two mssp modules, and a pretty flexible PPS mapping.
If you come up with something better I'm all ears!
btw - I know I didn't document all the various options very well, so if it gets confusing yell.