SparkFun Electronics Commentsurn:uuid:214d0e4e-f1b1-d287-ce26-ac5b4c9f82492024-03-29T05:25:14-06:00SparkFun ElectronicsGearJammer on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)GearJammerurn:uuid:35a00544-be8b-6821-57c8-3c02ec0945892021-09-22T18:10:08-06:00<p>I think the hookup guide is misleading. I changed the jumper to 3.3V. It tells you to select 3.3V 8Mhz micro pro in the Arduino IDE. But that bricked my board. Also my reset button wasn't working outta the box. I couldn't figure out why the reset trick wasn't resetting the processor. I manually jumpered the reset and that worked but couldn't get it to hit bootloader mode correctly still. Then I ran the BAT file the instructions point you to but that never worked either. I finally cleaned the reset button and it started working again. Then I could do the double click and recover the board. I changed the setting back to 5V 16Mhz and the sketch loads and runs fine now. Very frustrating process to get through. Hopefully this helps someone else.</p>
canonicaltom on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)canonicaltomurn:uuid:cbcd4b6f-9a82-9fb9-cfad-104836dad1f32021-08-08T03:54:35-06:00<p>I had a similar issue with the board, which I ultimately fixed. Out of the box, USB wasn't working at all, but I hooked up an AVR programmer and could get the blink program running. Still, none of the USB-related sketches would run and the serial port never showed up. Due to the nature of the USB 3 connector I couldn't test it directly, but I did hook up a microUSB board to the pads under the board. Same issue though, error logs complaining about enumeration errors. Spent an hour digging through forums to find that the 5.1k resistors were almost certainly the problem, and that this design is bad. Very, very carefully shorted them (what are they, 0402?) with wire, as suggested, fired it up, and everything worked fine. Would have preferred to replace them with 22 ohm resistors but I already spent so much time just getting this board into the state it's supposed to be in from SFE, I just didn't want to deal with it anymore.</p>
platypusfriend on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)platypusfriendurn:uuid:3823307d-df95-3850-dc9c-ae36bbedfbeb2021-04-02T09:40:50-06:00<p>How are people mounting these? Adhesive velcro? Glue?</p>
Nate on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)Nateurn:uuid:bc43b2e7-59f4-7627-50f4-106f748b3c1d2021-01-05T09:45:48-07:00<p>The CAD files are probably not going to be updated anytime soon as other projects and products have our burning attention.<p>Good eyes wrt USBC branch. For this product, it got a bit messy. The Pro Micro C 'revision' turned out the be very popular with the original maintaining is popularity. We are trying to maintain master for folks that still have or want to purchase the microB connector version.</p></p>
Gigahawk on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)Gigahawkurn:uuid:756f14ca-a0f2-99cf-4079-e68fd32670752021-01-03T04:15:29-07:00<p>Are the CAD files ever going to get updated?
I want a 3D model of this board to integrate into a project I'm working on and was just going to generate one from the EAGLE CAD, but it looks like the files in the USBC branch are still for the old Micro-B variant of the pro micro and haven't been updated for nearly a year.
The commit history looks like there was attempts to update the files, but I assume they were just incorrectly committed?<p>EDIT: nvm, didn't realize the USBC branch wasn't the main branch, is there a reason master is kept out of date?</p></p>
Customer #434194 on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)Customer #434194urn:uuid:e9eff1aa-756b-4a48-d66c-aaa621c578e82020-11-30T08:21:56-07:00<p>Note: I have found that connecting the ProMicro to a USB 3.0 port will often, if not always, brick the board. The setup guide provides info on how to de-brick the board, but it's not a trivial task. I recommend always using USB 2.0.</p>
santaimpersonator on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)santaimpersonatorurn:uuid:f02ae45a-c409-68bf-e20e-7a30d25a3f032020-08-19T18:54:22-06:00<p>I think if you submit a "request" through the issues tab in the GitHub repository and state your case... that might be a more visible platform for the engineers to take into consideration, if we have a revision of the board. That being said, there are a limited number of pins that can be broken out for such a small form factor, so I think it was a trade off the engineer had to make.</p>
Chiel on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)Chielurn:uuid:4d045f72-1f09-817f-14ef-586f6f8904b72020-08-11T11:20:57-06:00<p>The one thing i find disappointing is the lack of PC7 being broken out. Would have made my life a bit easier at using Timer4 to it's fullest, oh well. time to learn how to work with the invert !OC4A pin and implement a work-around. Shouldn't be hard. Luckily i don't need those PWM pins in sync. Though may have to keep in mind in future. Timer4 really is the reason i want to use the ATmega32u4 as it can take its clock of the PLL used to generate 96Mhz for USB. Allowing for the kind of PWM frequency normally only seen on 96mhz ARM controllers!<p>BTW: Have you guys ever noticed the Typo in the graphical datasheets? For years OC4A is on it as OCA4.</p></p>
santaimpersonator on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)santaimpersonatorurn:uuid:6fcb9ee7-14ba-e70f-c45d-79008004785c2020-05-27T10:48:53-06:00<p>Hi there, it sounds like you are looking for <a href="https://www.sparkfun.com/technical_assistance" rel="nofollow">technical assistance</a>. Please use the link in the banner above, to get started with posting a topic in our <a href="https://forum.sparkfun.com/" rel="nofollow">forums</a>. Our technical support team will do their best to assist you.</p>
Customer #1595185 on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)Customer #1595185urn:uuid:b88ab387-93bd-faa1-47ae-ce888079702b2020-04-30T22:52:04-06:00<p>Does anyone know what boot loader this uses?</p>
Funda on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)Fundaurn:uuid:7e24b509-d428-76ef-3e7a-62371d239c0e2020-04-13T11:45:39-06:00<p>Hey there. It looks like we found your forum post. We will look into this issue and assist you as soon as possible. Cheers!</p>
Customer #400974 on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)Customer #400974urn:uuid:44c15247-e3d3-021e-a951-183225be1b682020-04-11T16:10:53-06:00<p>Bricked two of these trying get the drivers right. The information was there I just misapplied it. Got it right on the third try. Tried the de-bricking procedures in docs with no luck.</p>
keen101 on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)keen101urn:uuid:d79a5b49-8fe2-2284-d082-153e5938469c2020-04-09T02:04:41-06:00<p>will there be a 3.3V /8MHz version? According to this guide 8MHz is recommended for 3.3V for projects where low power consumption is key.<p>(https://learn.sparkfun.com/tutorials/reducing-arduino-power-consumption)
"reducing the clock speed of the microcontroller can shave a few milliamps off the supply current. "</p></p>
falkenad on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)falkenadurn:uuid:14bae876-d5cc-e52a-2123-4a25ed8a63082020-02-13T09:30:50-07:00<p>Will there be a 3.3V / 8MHz version? I know there's a jumper for 3.3V operation, but there are applications where having it run at an 8MHz frequency is preferential.</p>
Quazar on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)Quazarurn:uuid:73849f36-2401-2f18-4268-aa24d8098c2b2020-02-10T12:54:36-07:00<p>Nice board - I will definitely be picking up a few for embedding into other projects!<p>One bit of feedback: I don't see level shifters on the Qwiic port, which is fine for I2C since that is an open drain arrangement and VIL, VIH, and VOL are all suitable for 3.3V devices.</p><p>However, a programming error could configure PD0 or PD1 as outputs driven high. In that case, the voltage on the Qwiic SDA/SCL lines would go up to near Vcc. The spec sheet says VOH is ≥ 4.2V @10mA if Vcc is 5V, and presumably it would go ≥ 5.2V if you run Vcc all the way to the limit.</p><p>It is worth documenting this assumption, since a programming error could cause the Qwiic bus to go out-of-spec and potentially damage sensitive I2C devices.</p></p>
Nate on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)Nateurn:uuid:b2c271e4-6a78-6e88-baaf-89b44a4262c72020-02-10T11:20:35-07:00<p>Good feedback! Thanks! Agreed. We'll try to get those out on a future rev.</p>
Nate on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)Nateurn:uuid:d45f99ae-bcc7-523c-04d2-5e7083368e862020-02-10T11:20:05-07:00<p>Yep. We're overclocking it (out of spec) at 16MHz/3.3V. We've done this on a few thousand units and haven't seen issues but your mileage may vary.</p>
Customer #736640 on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)Customer #736640urn:uuid:11882905-e13e-73e3-8a52-5f68c0f0a3bb2020-02-07T22:43:08-07:00<p>if you set the solder-jumper to 3.3V operation the ATMEGA 32U4 still runs on 16MHz ?
According to the Datasheet the max. allowed clock-frequency for 3.3V operation is 8MHz</p>
c38749 on DEV-15795 - SparkFun Qwiic Pro Micro - USB-C (ATmega32U4)c38749urn:uuid:ccf411bb-4bbf-788f-c052-41f11a81e3a02020-02-07T06:47:33-07:00<p>Please Break out PF1(ADC1) and PF0(ADC0) to pads on the board surface! They have functions like differential ADC that are not on any other pins.</p>