Search results for:

Very nice!
Are there any plans for a website that nicely shows the results of the benchmarks next to each other? The results are all there, but plain json is a bit of an eyesore ;).

I have also been looking at the HM-10 and it does seem to be a drop-in replacement. Not tested just yet as I am still waiting on mine (and will take some time, with Chinese new year and all). One word of caution though: they come in a variety of shapes. I think the one from iMall is a good one, but I have seen plenty on e.g. ebay and aliexpress that are a good bit shorter or with all sorts of extra pins attached.

Not immediately, as at the moment I didn't think it was important to save such code. I just turned all optimisations off. So far, none of the code seems to have any issues with minifying or simple optimisations, so it must have been some very specific code, as you would find in modules. The only thing I notice is that the advanced optimisations screw up your function names, which may not be what you want. If I do find an example in my code in the coming days, I'll be sure to post it here.

I think there are still some issues with minifying the code. I have disabled all optimisations in the web IDE as there have been instances where my code (without modules) did not run when using any of the optimisations. So I would assume that splitting the minification between code and modules will only provide limited relief.

Well, I still use the code example you provided to initialise everything so I think that the waiting is indeed sufficiently dealt with. The baud rate I use has one more 0 than yours, but given that you warn about rates below 1Mhz I assume that this is what you meant.

When the screen isn't working though, I am capable of turning the backlight on and off, so I assume it must be an issue related to the initialisation of the screen.

I still have quite a lot of issues with the PCD8544 display. At times, it just works. And whenever it is working, I can do with it whatever I want. As soon as the power to the Espruino is cut though it's a gamble whether I'll get access to the display again (without changing any of the cables). The only solution seems to be to power down and power up the Espruino repeatedly until it finally starts working again. The only error I get in the latest version is INTERNAL ERROR: Timeout on SPI RX, but I also seem to get this error when the display is working properly, so I don't know if that is of much use ...

PS: sorry, for the empty post at first, something must have gone wrong.

Have fun with your Espruino :). When you hold down BTN1 and then press RST you indeed see the blue and red LED. Don't release BTN1 at this point. Only release RST. This should make the blue LED start glow while the red LED turns off. You can then release BTN1.

To exit this bootloader mode just briefly hit the RST button.

Brilliant, thanks. Hadn't tried that yet and sounds extremely helpful.

But what do you end up with? A firmware, an actual executable program ... ?

Could you elaborate on running it on something else than ARM? How do you compile and run it in such cases?

Well, on Mac I definitely bumped into the need to compile a gcc compiler (there doesn't seem to be a package for that) and a lack of instructions on how to get in onto the boards. I agree that the first steps are easy though :).

Might think about getting it running on my NAS as I believe that is an ARM as well.

If you have a Pi :). I think that the most important part would be step-by-step instructions on the dependencies, how to get the code, how to compile it and how to get in on the boards on *nix systems (Windows might be hard, but maybe cygwin might be of help ...). Some of those steps are still missing or obscure. It's okay if you have a disposable machine to test on, but things such as compiling a gcc version can be messy. Though I think you can get everything running on e.g. OS X using macports, it is a bit too much of a gamble on a production system to test it out.

Another question in the same line: would it be possible to have a version of Espruino that can be run on *nix systems? This would essentially be an implementation of the Javascript version you have. This would make the development on the Javascript engine easier as you don't need to code, flash an external device and only then start testing. I don't know how easy it would be though.

Thanks!

Is it possible on the Espruino to display the code that has been saved using save()?

This will probably have been myself goofing up. I have had issues with the screen since day one, where sometimes it works flawlessly and other times, after reconnecting, I cannot get anything drawn on there. Might just be faulty wiring or something that is the cause (no idea how to check that though), but it definitely sounds like it isn't the software.

I'm not seeing it on all my boards ... Just tried it with another one and there are no issues. I still have the original code lying around so will try that again this evening on the original board (no time now, and code used the screen so need to do some wiring up).

@JumJum the command is analogWrite, so without the dot in between

I have indeed updated to the latest version. My wiring is exactly the same as yours, so I can't think of any reason why digitalWrite wouldn't work! I think it would indeed be best to first update the software and try again.

Hmm, this sounds strange. Could you elaborate a bit more on what you are doing? Do you have the Espruino connected with USB to a PC? What operating system? Are you using the Espruino environment in Chrome? Have you been able to update your Espruino to the latest version?

Finally, do you see the LEDs when you prepare the Espruino to install a new firmware? For this, press and hold the button marked BTN1, then press and release the RST button and finally release BTN1. You should see the lights flashing when you do this. You can then reset the board by pressing the RST button again, which should turn off the blue LED again.

@graf don't worry about the code formatting, it's fine :).
I tried the things you requested, and I got the following results:

with version 1v43
I indeed get 40 as a result, and the sensor is working as expected.
The result of process.env is

={"VERSION":"1v43","BUILD_DATE":"Dec 10 2013","BUILD_TIME":"11:59:35","BOARD":"ESPRUINOBOARD","CHIP":"STM32F103RCT6","CHIP_FAMILY":"STM32F1","FLASH":262144,"RAM":49152}

with version 1v46
ow.search returns [], thus the result of the next queries is undefined and 0. The result of process.env is

={"VERSION":"1v46","BUILD_DATE":"Jan 24 2014","BUILD_TIME":"17:28:16","BOARD":"ESPRUINOBOARD","CHIP":"STM32F103RCT6","CHIP_FAMILY":"STM32F1","FLASH":262144,"RAM":49152}

very odd ... it is reproducible though: if I flash 1v46 on there it all stops, and if I go back to 1v43 again the thermometer once again works ...

Ok, I just verified my assumption.

All wiring as is, I flashed older versions onto the board. Using 1v46 and 1v45 prevents me from reading the signal. Going back to 1v43 and the temperature is measured just fine.

The mystery deepens ... the devices connect to Bluetooth just fine and I can access them using screen. However, piping to either tty or cu causes them to disconnect from Bluetooth ...

That is exactly how it is wired up. I didn't know about the resistor though, but even changing the position doesn't change the result of null.

I changed boards though, to one with 1v43 on it, and then it magically works ... can you confirm the firmware version of your board?

No problem. Mind you, I'm a newbie as well and just learning as I go along. So far though it seems that the Espruino boards are very robust, so I wouldn't worry too much about toasting them ;).

Can I connect a battery to VBAT/GND?
Definitely, I just did it with a 9V battery.

Can I connect the batteries to VBAT/GND while USB is connected to my PC?
It seems like you can. In your previous circuit this was not the case and I can verify that the behaviour is unexpected. It also seems to be dependent on whether that pin is a 3.3V pin or not (which is kind of expected). I have a circuit, much like your previous one, up and running with a LED. It works fine when only connected to the battery (light goes on and off), but when also plugged into USB the light just goes from very bright to slightly less bright. Using the same wiring as when the USB is not connected, while the USB is connected, seems to provide the expected behaviour. This is exactly what you are suggesting and my board hasn't blown up just yet ;)