Most recent activity
-
- 16 comments
- 5,035 views
-
Yes, I was suprised as well, as previously doing lots of work with these including updating firmware and I've had to problems. Hmm, now I think about it and based on your comment, I may have done the update previously on a Winbows box, not Mac. Might try that as well. I'll also try your suggestion later today.
Thanks. -
Hi All,
I come back to my MDBT42Q project after quite a few months break.
I attempted to update to the latest firmeware but I seemed to have bricked both the MDBT42Q modules I have. I'm using the Web IDE and it seems to go fine but immediately return with this error..."Sorry, the firmeare update has failed.
The rror was: Error: Data object does not match the firmware and hardware requirements, the signature is wrong, or the parsing command failed"I've attached a screen shot.
Note, they connected fine before I tried to flash them. I'm sure I must be doing something silly.
Anyone know how to recover from this.
By the way, I'm on Mac, in case that matter.Regards,
Marco -
-
I'm using a MDBT42.
I have an iphone app which connects over BLE and can receive data from the MDBT42 over UART.
On the MDBT42 I use the print statement to send a load of byte in ASCII format, i.e. I send literal 'FF' for 255. In the iphone app I have to decode the ASCII characters received to generate a byte array which is then decoded again into a set of glucose readings.This all works fine, but there must be a better way to send just a big byte array without having to decode ASCII characeters in the iphone app.
Any ideas? I'm sure I've missed something obvious here.
Thanks,
Marco -
- 8 comments
- 2,738 views
-
Thanks for this tips. I'll certainly take a look at these suggestions.
I'm using the BM019, http://www.solutions-cubed.com/bm019/Yes, I do intend to share it soon.
Ah, ha. Works fine using my Windows 10 machine. In fact, it did fail once with the same error but a lot further along in the process. Next try was successful. Mac fails almost immediately.
So for information, I see this issue on a Macbook Pro running Catalina, Version 10.15.4.
Thanks for your help.