Hello guys. Basically I was experimenting with my MKR1000 and because of the nature of my code(I need multitasking therefore RTOS is best option for me) I started experimenting. Unfortunately programming MKR with FreeRTOS code found for Zero rendered it useless..... Most likely it's a clock issue and USB doesn't get initialized correctly and my board is invisible or sth similar. My question is how to connect SWD probes correctly, erase MKR and write bootloader again?? Or maybe there are some other smarter solutions for this problem. I'm a bit annoyed most likely I wont be able to submit my code to Arduino Challenge because of that
I'm having similar behavior ( on a SAMW25 xplained pro EV kit - it has EDBG on board )
it was Working OK for a long while and then seemed to stop enumerating in USB.
( Windows makes a "USB device plugged in " sound )
Wireshark says its a "malformed USB packet" from the SAMW25 ( MKR1000 bootloader )
I started with the Zero bootloader on this device ( Worked OK, just a different pin map
, then the MKR1000 came out and I switched to that booltoader and it was working great until yesterday when I could not upload anymore and Erasing teh device using EDBG, then loading bootloader again dos not seem to help.
The device doesn't seem to "boot" unless I hold Reset down for a few seconds, the unit goes into a USB mount "loop" ( Windows doesn't get to enumerate a COM port, just makes the USB device plugged in sound repeatedly )
Hi, I have a similar problem with being unable to upload to a 1 day old MKR1000. I have tried both Windows and Mac OS X running IDE1.6.8 and neither will successfully upload a sketch. The Mac says "Forcing reset using 1200bps open/close on port /dev/cu.usbmodemFA141" when I just click upload.
I see the following:
...
Sketch uses 8,488 bytes (3%) of program storage space. Maximum is 262,144 bytes.
Forcing reset using 1200bps open/close on port /dev/cu.usbmodemFA141
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodemFA141, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodemFA141, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodemFA141, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodemFA141, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodemFA141, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodemFA141, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodemFA141, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodemFA141, } => {}
Uploading using selected port: /dev/cu.usbmodemFA141
/Users/me/Library/Arduino15/packages/arduino/tools/bossac/1.6.1-arduino/bossac -i -d --port=cu.usbmodemFA141 -U true -i -e -w -v /var/folders/2w/5dvy0yjx41jc8vcff7twmhsm0000gn/T/build5d23db83bcccc7d9c5a930619292270f.tmp/mkr1k_serial_test.ino.bin -R
Set binary mode
No device found on cu.usbmodemFA141
Send auto-baud
Set binary mode
Some time goes by after I see "Forcing reset"
Then, some more time goes by before I get the set binary mode message after the bossac line.
I have tried variations of holding reset until the IDE says "Uploading" to no avail.
The board is set to "Arduino/Genuino MKR100"
The programmer is AVRRISP mkII
Are there any alternate ways to flash the board so that I might restore it?
I just found this page:
It says to press the reset button twice to put the MKR1000 into boot loader mode.
This worked and allowed me to upload "Blink" So, it appears that I'm back in business able to work with the MKR1000.
I did this sometime after the upload had started. I'm not sure of the exact sequence. Now, it is uploading correctly so I have no way of going back to know exactly when I double-clicked reset. But it did the trick!