@kennethlimcp, But I don’t even see a serial port on Mac in listening mode, even in cool term. I had tried this on Windows, 2 posts ago, based on what @harrisonhjones (I think its this person helping me!) had told me. But did not receive a response from him, yet.
So, not sure what to make of it. We have ordered another photon.
Uber weird. Doesn’t work with Mac and Windows? I saw in your screenshot that particle identify
worked though.
What I would do is to:
- Place my Photon in SAFE mode
- Flash the blink an led firmware using V0.4.4 using the Web IDE
- Modify it to use
Serial.begin(9600)
insetup()
and check that a serial com port opens
@kennethlimcp particle identify works on both windows and mac. “particle serial anything” doesn’t work on mac.
However, on the windows, according to the screenshot above, particle serial list works but not the others.
Hope that makes sense.
Firmware Im running now is v0.3.4. Are you suggesting I first upgrade to V0.4.4 and then modify the script for Blink and LED?
i guess you mean V0.4.3? You should really use something like Coolterm on Mac on Putty on Windows instead.
What are you trying to do with particle serial
actually?
No, SPARK FIRMWARE V0.3.4 (OCT 21)
I just updated it to v0.4.4 or so I think. Not sure how to check the current firmware version. SPARK FIRMWARE V0.3.4 (OCT 21) showed up on Devices and does not anymore.
Anyway, here is a snapshot after upgrading the firmware.
Serial and USB Still doesn’t work. But the LED is blinking alright.
And yes, I have been using CoolTerm on Mac as a check. But mainly Terminal to access serial ports.
I was trying to debug my code to collect data from an amplifier using particle serial monitor which was really helpful. When it failed, I tried exposing a variable and running particle monitor but the delay is 500ms which is substantial when you are reading a digital data.
For particle identify to work, device must be in Listening Mode (blinking blue). You Photon is listed online which means it is breathing cyan and it will not show up as a Serial device
V0.3.4 only applies to the Core and never for the Photon.
Long story short, if you want to use Serial, you need to Serial.begin()
in your code.
Anyways, try flashing this code:
void setup(){
pinMode(D7,OUTPUT);
Serial.begin(9600);
}
void loop() {
digitalWrite(D7, !digitalRead(D7));
Serial.println("test");
delay(200);
}
Ye. you are right. particle identity, setup ,etc works only in listening mode. However, particle serial monitor works in breathing cyan mode.
I have always used Serial.begin(). My code was working fine (just wrong results) and it still works except I can't see the output in Serial anymore. I can access variables using particle monitor but not particle serial monitor because it says it cannot find a device on Serial/USB.
And this is the Terminal result of the code you pasted with the LED blinking every 200ms in breathing cyan mode. Do you think I should type something else in Terminal?
MacBook-Pro-DN:Examples Nik$ particle list
pirate_plumber [440034001047343432313031] (Photon) is online
MacBook-Pro-DN:Examples Nik$ particle serial monitor
! serial: No devices available via serial
MacBook-Pro-DN:Examples Nik$ particle serial list
No devices available via serial
MacBook-Pro-DN:Examples Nik$
Is the LED blinking?
It’s really just down to the USB cable as i don’t see any issue with the code. Try another USB port if you will.
You should see that the led blinks as expected.
Also, I really recommend using Coolterm as mentioned earlier to debug for now.
Yes, like I mentioned above, LED is blinking ever 200 ms like its programmed to .
And I don’t know how to use coolTerm when it doesn’t show the serial port for Photon, only Bluetooth options exist.
I have also tried other ports. Same result.
Hello, I have the exact same issue you had, by any chance did you get to fix it?
Can you place the device in Listening mode and see if it listed as a serial port? Try swapping another cable as well.
Weird stuff…I encounter the same problem. In my case I’m trying to get started with the Programmer Shield…
But to stay on this topic…it seems that after upgrading to OSX El Capitan from OSX Yosemite, my serial monitor stopped working in terminal. The good part is, it still works in Particle Dev (Atom).
With my Photon (firmware ver. 0.4.6) in “listening mode”, this is what I get when trying to access serial monitor through a terminal session:
MacBook-Pro:openocd-0.9.0 Alex$ particle serial monitor
! serial: No devices available via serial
As far as the USB cable goes…it works cause I can get the serial monitor in Particle Dev (same cable).
Also when I place the device in DFU mode and run dfu-util -l
I get:
MacBook-Pro:rgbled Alex$ dfu-util -l
dfu-util 0.8
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org
Deducing device DFU version from functional descriptor length
Found DFU: [2b04:d006] ver=0200, devnum=15, cfg=1, intf=0, alt=1, name="@DCT Flash /0x00000000/01*016Kg", serial="00000000010C"
Found DFU: [2b04:d006] ver=0200, devnum=15, cfg=1, intf=0, alt=0, name="@Internal Flash /0x08000000/03*016Ka,01*016Kg,01*064Kg,07*128Kg", serial="00000000010C"
Found Runtime: [05ac:8286] ver=0151, devnum=6, cfg=1, intf=3, alt=0, name="UNKNOWN", serial="UNKNOWN"
Serial port not working with CLI on El Capitan is a known issue and hopefully fixed soon!
The thing is that I knew there was going to be issues with OSX El Capitan so I wanted to wait and didn’t do the upgrade, I still have OSX Yosemite and still have the same problem
Do sudo npm uninstall -g particle-cli
and sudo npm install -g particle-cli
and it will work now.
Thank you so so much! Will be posting pictures of final result of my new proyect!
I tried reinstalling particle-cli as you suggest above but I was still having the same issue: “! serial: No devices available via serial”.
I don’t have El Capitain installed, I have Yosemite.
But I got it to work again by using a different usb wire.
Hope this can help someone.
Actually you have!
Make sure to use the original spark core cable that was received in the pack.
For some reason it gets the core recognized by the PC. Perhaps it has to do with resistance of the cable wire.
THANKS!