-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What hardware features would you like? #137
Comments
Okay I'll bite (In order of cost/absurdness):
|
Definitely!
could you elaborate a little bit on how this feature would be used?
I am actually writing about NFC at this very moment, and I like it, but I am not a fan of multiple ways of accessing a device.
Definitely a small controlled power supply would be a good feature, and not hard to do.
Honestly, I'd like that. I don't like using serial over USB in this decade, but is not feasible on the current MCU.
I was thinking about moving from the header to included probes with better connector, and using a digital matrix switch to implement that, but they are quite pricey. ICE40 are actually cheaper, so not that crazy of an idea. |
The VPU to VCC is basically about saving a single wire for the instance of quickly hooking up to an i2c module. Right now doing so take a bit more time scrounging for either a breadboard or soldering a wire if the module only has one VCC input. |
allright got it |
Everything I'd like to see is being incorporated into Glasgow : https://github.com/GlasgowEmbedded/glasgow |
Interesting project. Hardware seems really clever. Software too clever. I
don't like the software dependencies, nor the fact that a lot of important
protocols are missing, while there are a lot of niche/hobbyist ones
implemented.
…On Tue, 2 Jun 2020, 16:04 Tom Matthews, ***@***.***> wrote:
Everything I'd like to see is being incorporated into Glasgow :
https://github.com/GlasgowEmbedded/glasgow
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#137 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACFC37V556SEG6OUY4D2W4LRUUIJLANCNFSM4MCJOMEQ>
.
|
Which useful protocols are missing in your opinion?
As far as not liking the fact it uses the ubiquitous Python3 language to program the FPGA, I'd say anyone that has tried to compile a BusPirate firmware with MPLAB and XC-16 would probably prefer the Glasgow. |
1-wire mostly. PICs are horrible to program, this has never been news. But Glasgow requires a working compiler to be used. This means that you can't throw it into the toolbox, forget about it for a year and expect it to work. There is going to be updating and maintenance to do on the computer. So the design fails to meet the criteria for it to be a tool. This is without considering the fact that programming requires quite a few working binaries. chance of stuff breaking increases much faster than linear with the number of binaries. Those binaries are going to be a huge shitshow to run on Windows. And whoever had the idea to program it with their own python-based hardware design language, it has doomed it to the same life as every project where someone decided to both implement a functional goal AND recreate the wheel. That is, they never go as fast as one would have tough, lag behind the competition, then people get bored of wasting their time with no results and everything gets abandoned. To my consideration, that's not a tool, that's a well designed demoboard. |
I think the BusPirate development was pretty doomed too, have you counted the outstanding issues with the community firmware, almost nothing works reliably and is trial and error which firmware works with what :) |
I am pointing towards the hydrabus as my next tool. In fact I'm looking
towards forking the HW in the next months to improve the pinouts and I/O
compatibility.
…On Wed, 3 Jun 2020 at 13:35, Tom Matthews ***@***.***> wrote:
I think the BusPirate development was pretty doomed too, have you counted
the outstanding issues with the community firmware, almost nothing works
reliably and is trial and error which firmware works with what :)
Anyway, I'm not here to bash the BusPirate, I've enjoyed using mine many
times, but I'm afraid it (even the v4) is already an ancient platform now
with very little active development.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#137 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACFC37QYOUXV5MUANBTXOTTRUY7QNANCNFSM4MCJOMEQ>
.
|
I just submitted and issue #142 before reading this IMHO, working on a new hw would be great, but also needs a working realiable and more universal firmware first, I mean, if one could compile and run BusPirate fw in an Arduino (wish it was fast enough), everyone would use it, you just need to wire 4-5 pins from your board. As example I use a lot the Arduino as ISP to program and upload bootloaders to different boards by ICSP, but it lacks the ability do debug. Someone did a first attemp https://github.com/ildar/esp-pirate The glassgow looks great, but is hardware dependant (also very sofisticated and advanced to use an FPGA), and maybe not everyone wants to debug at GHz. |
I really hope there is a way to figure out a cooperative organisation structure that could provide sustainable way to grow and maintain open hardware. But that's a topic for another time perhaps. |
There are many ways, just see many projects here in github that are normally sponsored or have a patreon with many supporters, maybe they are not the most profitable bussiness but at least some can sustain or partially afford it's own continuity, but it has to be constantly maintained, well organized and with a minimum critical mass of users, also a very motivated developer team. If I find some time i would dedicate it to start porting BP firmware to other boards |
@chepo92 please look into the hydrabus, I have researched this topic extensively and it's the best successor |
Thanks for the tip @ddavidebor hydrabus looks very promising, will look after it when I have more budget as a pro tool, besides, it doesn't currently ship to my country. Do you have one? |
No, I don't like their HW, I'm not buying it
But i'm considering making a competing hardware board
…On Wed, 22 Jul 2020 at 19:25, Axel ***@***.***> wrote:
Thanks for the tip @ddavidebor <https://github.com/ddavidebor>
I also found and bought this cheap board FT2232HL
<https://es.aliexpress.com/item/32806818411.html?spm=a2g0s.9042311.0.0.45b263c0BpfIU2>
to test (my objective is something good and cheap, I know it sounds like a
rat, but I think many makers prefer cheap toys to play, explore, learn and
break)
As I read some articles in the net
<https://www.allaboutcircuits.com/technical-articles/getting-started-with-openocd-using-ft2232h-adapter-for-swd-debugging/>
hydrabus looks very promising, will look after it when I have more budget
as a pro tool, besides, it doesn't currently ship to my country. Do you
have one?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#137 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACFC37VL36N2RN7IO4EFB4TR44VKRANCNFSM4MCJOMEQ>
.
|
What about AxiCat? I have no experience with that device but it seems it is similar device like BusPirate but build with AVR MCU... Price is similar to price of BusPirate. https://www.elektor.com/axicat Standard AxiCat is issued with an ATmega164A microcontroller (16kB FLASH/1kB SRAM/0.5kB EEPROM). :-( |
Did you ever progress this alternative board? |
Hello beautiful people.
I work for a big ECAD software house, writing articles.
I would like to make a couple of articles improving the bus pirate V4 hardware.
Which features / improvements / bugfixes would you like ? only hardware-wise
David
The text was updated successfully, but these errors were encountered: