I'm following step by step instructions from the Starter Kit R4 and got to the point of uploading the Blink example to the board. I struggled for a while until I found out that it only works if I press the "Reset" button manually on the board after the upload, which according to the book and what I can find online shouldn't be required.
I see in the verbose output from the IDE that its final call is "reset()", but that doesn't seem to work.
Obviously I can keep going but I'm wondering if I'm already doing something wrong. Online for these symptoms people are talking about faulty boards, soldering reset pins, etc., which seems worrysome / too advanced for me already?!
Figured it out? It seems to have been an issue with the USB cable used. I used a presumably standard Apple USB-C to USB-C cable, but switching to the one provided in the starter kit box made it work. No idea why, though!
Some USB cables are POWER ONLY and some are DATA and POWER. Label each USB cable so you can get the right one. Most "just a USB" cables are power-only.
Nothing wrong, switching to the Serial monitor should do a reset but if it doesn't, just press the button. I almost always press the button 'just because'
Ah, I'd deleted my reply immediately because it didn't actually solve it (not sure how/why you still saw it). It happens even with the Arduino-provided USB cable. Both cables are data-and-power, actually, because the Apple one can do any kind of device data sync, so this is not it.
I also purchased the Uno R4 Starter Kit. Had some troubles with the new IDE 2.3.7 for a few days, now it has been running a few days without hiccup. Though the Chill-o-meter sketch has been a real stinker, giving results that are not expected and varying with uploads.
Read lalubo post stating there have been some defective boards, now wondering if that might be what is happening here… hmmm noticing a firmware 0.6.0 mentioned. Will look into that…
Well, updating firmware did not help. Also have experienced issue with board disconnecting from IDE, unplugging the USB and reconnecting gets it back. Would not think that is a normal thing.