Jump to content
  • 0

Arduino IDE wiFire Rev D not responding


Gareth O'Brien

Question

I've been using chipkitCore with a Rev C without problem.

I went to test the same code on my "spare" board which turns out to be a Rev D.

I've uninstalled chipkitCore upgraded to digilentCore - which got me a little further. But now when I attempt to flash Blink to the board, it fails as follows and locks up the COM port requiring a PC reboot.

Any ideas?

Thanks,

Gareth.
 

Sketch uses 10568 bytes (0%) of program storage space. Maximum is 2080768 bytes.
Global variables use 3116 bytes (0%) of dynamic memory, leaving 521172 bytes for local variables. Maximum is 524288 bytes.
DigilentPGM V1.00
Digilent Copyright 2016
Written by Keith Vogel
02 March 2018 12:37:10 o'clock GMT

Comm Port: COM12
Baud rate set to: 115200
IO Exception, unable to send message
Unable to signon, this does not look like a bootloader
Error 0x1f at ../src/termios.c(1321): A device attached to the system is not fuError 0x5 at ../src/termios.c(512): Access is denied.


Error 0x5 at ../src/termios.c(2723): Access is denied.


Error 0x5 at ../src/termios.c(512): Access is denied.


Error 0x5 at ../src/termios.c(2723): Access is denied.


Error 0x5 at ../src/termios.c(512): Access is denied.


Error 0x5 at ../src/termios.c(2723): Access is denied.


Error 0x5 at ../src/termios.c(512): Access is denied.


Error 0x5 at ../src/termios.c(2723): Access is denied.


Error 0x5 at ../src/termios.c(512): Access is denied.


Error 0x5 at ../src/termios.c(2723): Access is denied.


Error 0x5 at ../src/termios.c(512): Access is denied.


Error 0x5 at ../src/termios.c(2723): Access is denied.


Error 0x5 at ../src/termios.c(512): Access is denied.


Error 0x5 at ../src/termios.c(2723): Access is denied.


Error 0x5 at ../src/termios.c(512): Access is denied.


Error 0x5 at ../src/termios.c(2723): Access is denied.


Error 0x5 at ../src/termios.c(512): Access is denied.


Error 0x5 at ../src/termios.c(2723): Access is denied.

 

Link to comment
Share on other sites

5 answers to this question

Recommended Posts

More info ...

Without restart I switched to the Rev C board and disconnected the Rev D. The ran the same upload from Arduino IDE (of Blink sketch) without problem:

Build options changed, rebuilding all
Archiving built core (caching) in: C:\Users\GARETH~1\AppData\Local\Temp\arduino_cache_241205\core\core_Digilent_pic32_chipkit_WiFire_5a4b65856f6a05ce50cc47394aaacc92.a
Sketch uses 10568 bytes (0%) of program storage space. Maximum is 2080768 bytes.
Global variables use 3116 bytes (0%) of dynamic memory, leaving 521172 bytes for local variables. Maximum is 524288 bytes.
DigilentPGM V1.00
Digilent Copyright 2016
Written by Keith Vogel
02 March 2018 12:52:07 o'clock GMT

Comm Port: COM6
Baud rate set to: 115200
Bootloader only supports STK500v2

Processing HEX file: C:\Users\GARETH~1\AppData\Local\Temp\arduino_build_736819/Blink.ino.hex
Opened HEX file: C:\Users\GARETH~1\AppData\Local\Temp\arduino_build_736819\Blink.ino.hex
Successfully processed HEX file: C:\Users\GARETH~1\AppData\Local\Temp\arduino_build_736819/Blink.ino.hex
Program block size: 256 bytes
Number of blocks: 46
Program size: 11776 bytes
HEX file processing time: 0s 16ms

Starting Programming:  0123456789 0123456789 0123456789 0123456789 012345
Program time: 1s 592ms

Starting Verification: 0123456789 0123456789 0123456789 0123456789 012345
There were 0 validation errors
Verification time: 1s 778ms

End of Program

 

Link to comment
Share on other sites

Hi JColvin,

It seems the problem is no the lack of the bootloader.

I have got to the point where I can upload code once. The code executes without problem.  If I then attempt to upload again, so for example during debugging this is iterative, then I get:

Uploading 'MliMonitor' to 'Digilent WiFIRE(Rev D)' using 'COM12'
DigilentPGM V1.00
Digilent Copyright 2016
Written by Keith Vogel
08 March 2018 12:33:41 o'clock GMT
Comm Port: COM12
Baud rate set to: 115200
TimedOut waiting for Serial Response
Unable to signon, this does not look like a bootloader
    The upload process has finished.

Note: I briefly see red leds at the usb connector as though it is receiving but then nothing.

If I unplug from USB, everything resets and I can upload again ... once!

My workaround is to get everything working on a RevC board (which works fine) and then flash the result to the RevD. Which of course only works because I have both.

Gareth.

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...