RichardH

Members
  • Content Count

    10
  • Joined

  • Last visited

  1. FYI, I swapped for a new WF32 and it worked like a champ straight out of the box. Also, as I got going, I noticed that the 0023 build from 8/2014 didn't include any of the WiFi examples for the WF32, so I ended up back on the 0150 build from 2/2015. Cheers, Richard
  2. Hi, LariSan. I just installed mpide-0023-macosx-20140821 with the same result. Even rebooted for good measure. The cable I'm using is the mini USB port, not the micro port. Also note that if I just plug the unit into a USB charger I get no lights except a quick blip on the RX/TX LEDs. Yes, the serial port shows up when connected, and disappears when removed. And there's 3.27v on the power bus. Pressing reset has no effect, and removing the DTR reset-enable jumper also does nothing (in case the reset was being held improperly). Thanks, Richard
  3. Hi, LariSan. Thanks for the video. When my board powers up, I don't get any of the green LEDs on the upper-right like yours. I use FDTI adapters regularly in my job, plus I'm concurrently working with several different AVR Arduino boards and Edison. They all work, and at least a few of them are FTDI-based. I initially did not install the drivers provided with MPIDE because they're like 5+ years old, and I've surely installed at least that version, if not more recent from FTDIs site. Nonetheless, when it didn't work, I did install those drivers and tried again with the same results. MacBookPro is 15" Retina, late 2013, OSX 10.9.5. Port is on the left side, and I'd expect it's USB3. Tried a couple generic cables that work on other peripherals. The MPIDE 0023 download hasn't been updated since 8/2014. I downloaded mpide-0150-macosx-20150204-test, which was updated 8 days ago - I presumed that was the latest build. The banner says it's 0023, but the installation file looks like it's 0150. Since the interface is serial, is there a string I can output from a terminal emulator that the boot loader should respond to? Thanks, Richard
  4. Yep, I'd tried the manual reset method with no results. And I'm running the latest 0150 build. I had an FTDI driver previously installed and working elsewhere, but when things didn't work I did try installing the one supplied with MPIDE. ps -ef shows no avrdude running. Even if I plug the board into a wall wart, I get no LD3/LD6 lights. So... presuming I need to reflash the board, I lack a PIC programmer. I don't suppose any of my AVR tools would be useful here (e.g., STK500 dev board)? Thanks, Richard
  5. So, leaping to a conclusion that the boot loader is somehow not present, how could I load it without a picKIT, etc? My gear is all AVR-centric; this is my first PIC platform.
  6. Negative. I only see the LD1/LD2 flickers. No LD3 or LD6 activity. I just checked and the 3.3v rail seems good.
  7. Hi, J. Yes, you're correct - my jumper is on UART, which is the one difference from the reference manual photo. The others are the same, I swear. ;-) Not knowing how the bootloader is supposed to behave, how can I verify if it's present? Does it have any visual indicators (pulsing LEDs, etc.) when it first loads? Can I hit it from a terminal emulator and expect a response?
  8. More detail from a verbose upload log... Binary sketch size: 6676 bytes (of a 520192 byte maximum) [/Applications/mpide.app/Contents/Resources/Java/hardware/tools/avr/bin/avrdude] [-C/Applications/mpide.app/Contents/Resources/Java/hardware/tools/avr/etc/avrdude.conf] [-v] [-v] [-v] [-v] [-p32MX695F512L] [-cstk500v2] [-P/dev/cu.usbserial-AD01PHTH] [-b115200] [-D] [-Uflash:w:/var/folders/yx/y2mr0_dd0r5cp0vtzl3lxk_w0000gn/T/build626266432486106377.tmp/Blink.cpp.hex:i] avrdude: Version 5.8cvs, compiled on Jan 15 2010 at 17:27:01 Copyright © 2000-2005 Brian Dean, http://www.bdmicro.com/ Copyright © 2007-2009 Joerg Wunsch System wide configuration file is "/Applications/mpide.app/Contents/Resources/Java/hardware/tools/avr/etc/avrdude.conf" User configuration file is "/Users/Richard/.avrduderc" User configuration file does not exist or is not a regular file, skipping Using Port : /dev/cu.usbserial-AD01PHTH Using Programmer : stk500v2 Overriding Baud Rate : 115200 avrdude: Send: . [1b] . [01] . [00] . [01] . [0e] . [01] . [14] avrdude: ser_recv(): programmer is not responding avrdude: stk500_2_ReceiveMessage(): timeout avrdude: Send: . [1b] . [01] . [00] . [01] . [0e] . [01] . [14] avrdude: ser_recv(): programmer is not responding avrdude: stk500_2_ReceiveMessage(): timeout This seems like a basic comms failure / missing bootloader. MPIDE sees the port when connected, I see the TX attempts on the WF32's LED, and MPIDE gets a "avrdude: ser_recv(): read error: Device not configured" when I unplug it - so I'm confident I'm connected to the right driver, and MPIDE is seeing all the way to the FTDI chip. Is 115200 the correct baud rate? I see no option in MPIDE to change it.
  9. I just received a new WF32 and I'm excited to hit the ground running... if I could get to Hello World. I'm using Arduino IDEs for several AVR boards, Edison, etc. and they're working fine on this system (MacBookPro w/ 10.9.5), so I'm comfortable that system, drivers, cables, etc. are OK. I'm using MPIDE 0150. Board and serial port are set. The board is acting like it doesn't have a boot loader. How should it normally behave on power-up from factory, or on reset? On power-up, I see 2 strong TX/RX pulse cycles on LD1/2, then nothing. Trying to load a sketch sees an occasional weak pulse on LD1 (RX?) and nothing going back out - and MPIDE gets avrdude: stk500_2_ReceiveMessage(): timeout Pressing reset gets nothing. Jumper pins are set similar to the photographs in the reference manual, and I've checked the jumper settings for power, JP1. The FTDI is being recognized when connected. How do I unbrick this? Connect an ICSP header and flash a new boot loader? Or have I overlooked something basic here? Thanks, Richard