Close
0%
0%

Shitty Add-Ons

Stop calling it 'SAO'.

Similar projects worth following
The #badgelife of Defcon 26 will feature badges with badges! Remember the Brain Slug on the Bender Badge from last year? Yeah, like that, only we figured out the most minimal and shittiest implementation so *all* badges can have shitty add-ons.

Known I2C Addresses on Same Bus

To avoid address conflicts, known 7-bit addresses are below. If I2C is utilized on your addon, avoid these.

We recommend exposing I2C-slave address pins via test points or pins/jumpers to allow for reconfiguration in the event of an address conflict. Typically these can be changed by pulling the address pin low or high. Refer to the device's datasheet for further information.

BadgeAddress
AND!XOR DC260x30
AND!XOR DC260x18
MR ROBOT BADGE0x60
MR ROBOT BADGE0xA0 -- Using for Serial EEPROM
Mr Blinky Bling0x42

x-zip-compressed - 1.88 MB - 09/14/2018 at 02:30

Download

kicad_mod - 1.74 kB - 04/06/2018 at 17:51

Download

lib - 455.00 bytes - 04/06/2018 at 17:51

Download

sch - 75.92 kB - 02/14/2018 at 00:58

See BOM
Download

brd - 38.04 kB - 02/14/2018 at 00:58

Download

View all 6 files

  • #badgelife DC26 shitty development board

    Zapp04/06/2018 at 20:44 3 comments

    Want to make your own add-on but all you have is a pile of through hole components and some ideas? Or maybe you're a l33t soldering machine, capable of soldering 200+ pin BGA packages to proto boards. Look no further than the #badgelife DC26 shitty addon development board.

    Of course you should know this meets the extremely high quality standards that all shitty addons are required to meet. Quality is so high, these are not tested prior to production.

    https://oshpark.com/shared_projects/GQSszwbF

  • The design of the Totem is complete

    Benchoff02/14/2018 at 01:02 1 comment

    This is a 'totem' that will hold four add-on badges as implemented in the DC26 shitty add-on standard. There are provisions for two AA batteries (optional, if you want to power them externally), a lanyard hole, and a 1x4 header breaking out VCC, SDA, SCL, and GND. Basically, it's the shittiest thing you can imagine.

    How does this connect to Badge add-ons?

    There you go. Gerbers available in this project. Also available as a shared project on OshPark: https://oshpark.com/shared_projects/uYwa5w3S

View all 2 project logs

  • 1
    Print it

    Have it printed.

  • 2
    Solder it

    Get out your iron and put the parts on

  • 3
    Power it

    Find some batteries in that one drawer that never opens because there's a potato masher or something in there.

View all 4 instructions

Enjoy this project?

Share

Discussions

grey_man wrote 09/07/2018 at 14:00 point

I'm still new to circuit design so trying to wrap my head around I2C and how to use it. If I'm building a shitty add-on can I use the SCL signal as a trigger to blink lights or do I still need a 7555 or is there a better way to do that?

  Are you sure? yes | no

thelogicofpi wrote 09/20/2018 at 16:00 point

there are a lot of ic's that use i2c to communicate, what you want to find is one that is either a GPIO expander or something similar. The mr.meeseeks SAO uses a MCP23017 

  Are you sure? yes | no

thelogicofpi wrote 09/20/2018 at 16:03 point

Then once you connect leds + resistors to each pin. but this is all reliant on the badge knowing what your i2c address is and sending packets that the mcp23017 would interpret into led blinky patterns, ie. sending it binary values which correspond to ascii numbers, but when translated to binary represent each led as a bit of that byte. ie "3" would be 00000011 so whatever was connected to pin 0 and 1 would be on and everything else would be off. :) hope that helps to explain. 

  Are you sure? yes | no

grey_man wrote 09/28/2018 at 07:45 point

That helps a lot. I'm guessing the SAO connector on the official DC26 badge just provides power and doesn't send a blink pattern over the i2c. For a blink pattern I would probably need to have some control over the hosting badge as well, i.e. build my own badge with a SAO and then build my own SAO badges to plug into it? Or are some of the unofficial badges putting out blink patterns I could tap?

  Are you sure? yes | no

Sajin wrote 07/25/2018 at 16:15 point

Created shitty add-on scanner / debugger. This would print over UART all the "Friendly names" for the badges. Tries to read and write to all devices found.  https://github.com/sajingeo/b617/tree/master/gadget_test

  Are you sure? yes | no

oshpark wrote 06/06/2018 at 16:51 point

Please email drew@oshpark.com if anyone would like a batch of add-on's made for no cost.  Drew will be at Defcon and wants to make sure everyone is well stocked with fun add-on's :)

  Are you sure? yes | no

ReanimationXP wrote 02/23/2018 at 10:32 point

So obviously this is shitty, but power's a concern. I'd clarify 3v3 if that's a requirement vs VCC.. VCC is ambiguous and I suspect lots of badges will be 5v VCC.  It's also a lot harder to go back up to 5v than down to 3v3 from 5v.

  Are you sure? yes | no

Benchoff wrote 02/23/2018 at 18:39 point

As far as I can tell, most of the #badgelife badges are going to be 3.3V.  That's what we're settling on, I guess /shrug.

Also, this is the *shitty* addon. If you want guaranteed voltages and the ability to sink a set amount of current, make your own standard. This is the one where we go, 'yeah, that'll probably work.'

  Are you sure? yes | no

AVR wrote 02/22/2018 at 23:34 point

"Find some batteries in that one drawer that never opens because there's a potato masher or something in there." how do you know you've never been to my house lol

  Are you sure? yes | no

Ted Yapo wrote 02/22/2018 at 23:58 point

That's what you think...

  Are you sure? yes | no

Similar Projects

Does this project spark your interest?

Become a member to follow this project and never miss any updates