Blog

I've finally emerged from monk mode after locking in to beat Silksong pass my final semester to provide you with updates! Contrary to popular belief, I did not get hit by a truck. (Actually our co-founder did, but she's doing okay now.) Over the past few months, we've been doing a lot of work...

Holy cow it was a crazy week! Open Sauce, tinySwag, TikTok, and more!

🔥 Highlights

• Tested and Prepared 50 tinyCore Kits
• Designed and Built our booth
• Drove 5000 miles to present at Open Sauce!
• Started posting on socials (TikTok, Instagram, YouTube)
• Sold through all of our kits!!
• De...

Here's what's happened at Mr. Industries in the last few weeks:

• Finalized our testing procedures and began soldering and testing units
• Listed our product on Tindie!
• Posted two tinyCore projects on Instructables
• Won the Wearables Instructables contest!
• Gave the website a facelift
• Designed our super secret online coding agent
• Onboarded a Software Engineer :)

Also I'm in Ireland...

If you're keeping count, you'll noticed we missed last week, and that's because we're still a student-run company (until next semester). However, with finals over, we've got a bunch of good updates to share! Here's what happened this week (and last):

• Presented tinyCore via OpenHEG during CU Boulder's Senior Engineering Expo
• Shared our project at CU's ATLAS Expo
• Made some banger new business cards
• Sold and tested more kits
• Refined our Kit of Parts (now with a sweet treat)
• Won a 9k Microgrant from Clear Creek Makerspace!
• Begun editing our "How it's made - tinyCore" Video

In the face of midterms and final projects, we continued to make progress on tinyCore! Here's what happened this week:

• Began testing V2.1 PCBs
• Attended First Pitch Colorado
• Met with more professors for our Fall Cohort
• Presented tinyCore at the Mines Entrepreneurship
• Showcase
• Shipped our first online orders
• GOT ACCEPTED FOR OPEN SAUCE!!

Hey everyone! Welcome to this week's Wednesday Weeknote. Here's what we've been up to:

🔥 Highlights

• Sexy new documentation website
• Presented at the 20th Anniversary Celebration for Clear Creek Makerspace
• Applied to the Underdogs Grant fund by MatrixOwl
• Hand-delivered a tinyCore V2 Starter Kit to a certain YouTuber :sunglasses:
• Our latest shipment of PCBs as arrived! (Next up: Testinggg)

Hey guys! I'll be trying to post periodic/bi-weekly updates on development more frequently in these channels. Here's what happened in the last two weeks. We are rapidly developing the tinyCore as the first element of our project. Revision 2 has been created, with some minor circuit modifications and bug fixes. We've ordered 20 of this board, on 1/14, and we expect the boards to arrive prior to 2/22.

I had Claude write up an I2S Test for a speaker, specifically the MAX98357A. Here's the program it wrote:

Our board needed a custom Arduino library, so I went through and made our own. First I started by copying the adafruit_feather_esp32s3_nopsram folder from:

C:\Users\macge\AppData\Local\Arduino15\packages\esp32\hardware\esp32\3.1.0-RC2\variants

I renamed this file to "iota_core_esp32s3_nopsram". (This is very important to remember, because this name definition must match exactly with the boards.txt file we will edit later.)

Finally got the SD Card working! Turns out the CS Pin is connected to GPIO1, not GPIO2, due to a pin mix-up in the library. Simple software fix, and it's like magic!

Also, I would recommend verifying that you don't have a corrupted Chinese-knockoff SD Card, as this will also cause you headaches and make things more difficult to solve.

For the SD test, we actually used the Arduino SD_Test Example, which worked out of the box (with our custom board library):

Had to find the MAC Addresses of the devices first, so I used this program:

Issues with I2C:

1. I2C PWR is run on a separate bus for low-power functionality, so you must enable I2C_PWR pin, which is GPIO 6! (Pin 10 on the ESP Module)
2. I2C default pins are 22 and 21, which do not work for our board. We are using pins 3 & 4 for SDA/SCL respectively.

Had some issues with Serial Monitor not working, and the device not being recognized, it was confusing to get down, but I solved those issues.

1. ERR light turns on during operation

   Apparently this is normal, ERR LED is connected to GPIO21, which is the Debug pin on the ESP32-S3. This means that it pulls low when it's in debug, and defaults high in regular mode (although this can be overridden in code [TESTED]).