Spark Photon

Will the new spark photon be compatible?

As we get our Photon in hands, yes, of course

Have you gotten a Photon yet?
I’m getting ‘Code verified’ from the Verify step, but failing with make errors in the Flash step.
Using BLYNK v0.2.1, Spark firmware V0.3.4

I have a Photon and have the same issue. It passes verification in the particle.io compiler (version v0.3.4) but when I go to flash it, errors appear. Below is my result.

In file included from blynk/BlynkSparkCore.h:16:0,
from blynk/BlynkSimpleSparkCore.h:14,
from blynk_for_sparkcore.cpp:18:
blynk/BlynkApiSparkCore.h:72:3: warning: #warning “analogInputToDigitalPin not defined => Named analog pins will not work” [-Wcpp]
#warning “analogInputToDigitalPin not defined => Named analog pins will not work”
^
In file included from blynk/BlynkSparkCore.h:17:0,
from blynk/BlynkSimpleSparkCore.h:14,
from blynk_for_sparkcore.cpp:18:
blynk/BlynkProtocol.h: In member function ‘int BlynkProtocol::readHeader(BlynkHeader&)’:

			This looks like an error in blynk library.
			Would you like to create an issue on GitHub to let the author know?
			
		
		blynk/BlynkProtocol.h:250:34: error: there are no arguments to 'ntohs' that depend on a template parameter, so a declaration of 'ntohs' must be available [-fpermissive]
 hdr.msg_id = ntohs(hdr.msg_id);
                              ^
	



	blynk/BlynkProtocol.h:250:34: note: (if you use '-fpermissive', G++ will accept your code, but allowing the use of an undeclared name is deprecated)




	
		
			This looks like an error in blynk library.
			Would you like to create an issue on GitHub to let the author know?
			
		
		blynk/BlynkProtocol.h:251:34: error: there are no arguments to 'ntohs' that depend on a template parameter, so a declaration of 'ntohs' must be available [-fpermissive]
 hdr.length = ntohs(hdr.length);
                              ^
	



	blynk/BlynkProtocol.h: In member function 'void BlynkProtocol<Transp>::sendCmd(uint8_t, uint16_t, const void*, size_t, const void*, size_t)':




	
		
			This looks like an error in blynk library.
			Would you like to create an issue on GitHub to let the author know?
			
		
		blynk/BlynkProtocol.h:282:27: error: there are no arguments to 'htons' that depend on a template parameter, so a declaration of 'htons' must be available [-fpermissive]
 hdr->msg_id = htons(id);
                       ^
	



	



	
		
			This looks like an error in blynk library.
			Would you like to create an issue on GitHub to let the author know?
			
		
		blynk/BlynkProtocol.h:283:39: error: there are no arguments to 'htons' that depend on a template parameter, so a declaration of 'htons' must be available [-fpermissive]
 hdr->length = htons(length+length2);
                                   ^
	



	blynk/BlynkProtocol.h: In instantiation of 'void BlynkProtocol<Transp>::sendCmd(uint8_t, uint16_t, const void*, size_t, const void*, size_t) [with Transp = BlynkTransportSparkCore; uint8_t = unsigned char; uint16_t = short unsigned int; size_t = unsigned int]':

blynk/WidgetBridge.h:30:78: required from here

			This looks like an error in blynk library.
			Would you like to create an issue on GitHub to let the author know?
			
		
		blynk/BlynkProtocol.h:282:27: error: 'htons' was not declared in this scope
 hdr->msg_id = htons(id);
                       ^
	



	



	
		
			This looks like an error in blynk library.
			Would you like to create an issue on GitHub to let the author know?
			
		
		blynk/BlynkProtocol.h:283:39: error: 'htons' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive]
 hdr->length = htons(length+length2);
                                   ^
	



	blynk/BlynkProtocol.h:282:27: note: 'htons' declared here, later in the translation unit
 hdr->msg_id = htons(id);
                       ^

blynk/BlynkProtocol.h: In instantiation of ‘int BlynkProtocol::readHeader(BlynkHeader&) [with Transp = BlynkTransportSparkCore]’:
blynk/BlynkProtocol.h:92:23: required from ‘bool BlynkProtocol::connect() [with Transp = BlynkTransportSparkCore]’
blynk/BlynkProtocol.h:132:22: required from ‘bool BlynkProtocol::run(bool) [with Transp = BlynkTransportSparkCore]’
blynk_for_sparkcore.cpp:68:15: required from here

			This looks like an error in blynk library.
			Would you like to create an issue on GitHub to let the author know?
			
		
		blynk/BlynkProtocol.h:250:34: error: 'ntohs' was not declared in this scope
 hdr.msg_id = ntohs(hdr.msg_id);
                              ^
	



	



	
		
			This looks like an error in blynk library.
			Would you like to create an issue on GitHub to let the author know?
			
		
		blynk/BlynkProtocol.h:251:34: error: 'ntohs' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive]
 hdr.length = ntohs(hdr.length);
                              ^
	



	blynk/BlynkProtocol.h:250:34: note: 'ntohs' declared here, later in the translation unit
 hdr.msg_id = ntohs(hdr.msg_id);
                              ^

In file included from blynk/BlynkSparkCore.h:16:0,
from blynk/BlynkSimpleSparkCore.h:14,
from blynk_for_sparkcore.cpp:18:
blynk/BlynkApiSparkCore.h: At global scope:
blynk/BlynkApiSparkCore.h:28:6: warning: always_inline function might not be inlinable [-Wattributes]
void BlynkApi::processCmd(const void* buff, size_t len)
^
In file included from blynk/BlynkSparkCore.h:17:0,
from blynk/BlynkSimpleSparkCore.h:14,
from blynk_for_sparkcore.cpp:18:
blynk/BlynkProtocol.h:171:6: warning: always_inline function might not be inlinable [-Wattributes]
bool BlynkProtocol::processInput(void)
^
blynk/BlynkProtocol.h:72:6: warning: always_inline function might not be inlinable [-Wattributes]
bool BlynkProtocol::connect()
^
make[1]: *** […/build/target/user/platform-6blynk_for_sparkcore.o] Error 1
make: *** [user] Error 2

Guys, we can’t guarantee Photon support until we get our devices. I’m still waiting for mine to come.

It would be great if it worked out-of-the-box, but usually it doesn’t happen with hardware. Too many variations.
Let’s wait some time.

1 Like

Hope you will get it soon and we will get the upgrade soon too :smile:

The Photon is ready to Blynk on my desk.

1 Like

Hey @Pavel, did you get the Photon?

@Pavel, you should have received your Photon by now. Any updates?

Any updates on Photon support? I would love to start using blynk with mine.

Yes, Photon is on the way to @vshymanskyy so that he can take a look at it. You should also understand that while we truly like this tiny thing, the number of Blynk users working with it is really low, so we have to give it a very low priority.

But we hope that someone from Particle community might start doing smth with Photon support.

2 Likes

@Pavel thanks for the update! I’ll check their forum and see if anyone has made some headway with it.

@Pavel, the number of Blynk users using may be low because they have been waiting for Photon support!!

3 Likes

Do you think it can be also applied to Spark Core users? :slight_smile:

@Pavel, the Core is no longer available and many are already “committed”. However, I believe a number of Cores are sitting out there waiting for a great app like Blynk. I personally want to use many of my Cores with Blynk though I’m waiting on some feature like app "packaging"and such. Now that the Photon is about to get new firmware solving a lot of issues, porting Blynk to will should be very straight forward and worth the effort. Being a Particle Elite, I will gladly promote Blynk to the community - it rocks! :wink:

3 Likes

It will be easy once I get the board… I think I’ll get it in 2 weeks (approx).

2 Likes

New to the Photon, and just found out about Blynk this morning from a post on the Make groups. Super excited to get something going and I would like to use Blynk to have a front end for my photon so I don’t have to write my own webpages… Chalk me up as another vote in increasing the number of Photon users wanting support :grinning: .

Photon is there!
Go and blynk something awesome! :pray:

Proof: https://www.facebook.com/blynkapp/photos/a.765247900232435.1073741828.584389781651582/886123764811514/?type=1&theater

5 Likes

Pavel -
Thanks for the quick response! I will be playing with this tonight :).

Thanks again!

got mine rolling right now hope to see what else we can do with these
VERY nice example setup