Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - tolson

Pages: [1] 2 3 ... 59
1
Videos/Guides/Tutorials / Re: RFduino Cheat Card
« on: January 17, 2018, 09:04:42 AM »
Change RFDuino to RFduino.

The FACTORY pin is SWD for those that want to do JTAG.

Would be nice to reduce file size down from 800kB+.

Otherwise, purty.

2
Production Application Guidance / Re: ICSP programming
« on: December 20, 2017, 07:04:52 AM »
You don't really need a reset button. Just a capacitor between the DTR line and the RESET line is needed. Look at the schematic for the RFduino USB shield.

3
Production Application Guidance / Re: ICSP programming
« on: December 19, 2017, 03:49:30 PM »
Let me put this another way:  Does SparkFun just buy your chips and solder them onto their Simblee BLE Breakout board?  This is SKU WRL-13632 https://www.sparkfun.com/products/13632

If that is true then I'm with you 99%.  Just give the board serial I/O and burn the code in from the Arduino IDE.

So one more question:  What does all this ancillary circuitry do in the above SF board?  Taking signals from the serial DTR pin?  Thanks

Yes, the Simblee SOC is bought from RFdigital and mounted on the sparkfun board. Sparkfun has really good documentation on how things work.

The schematic you show is a manual reset button in conjunction with the DTR through a capacitor. The DTR line is used to by the Arduino IDE to reset the Simblee/RFduino to tell the bootloader to go into programming mode or run mode.

4
Production Application Guidance / Re: ICSP programming
« on: December 19, 2017, 03:46:20 PM »
I am not an employee of RFdigital. Just a community user who happens to be a moderator.

The bootloader firmware is programmed into the nRF51822 read protected flash by RFdigital. They keep secret the actual  bootloading code and exactly where that loads into the nRF51822. So if you blow away their bootloader using JTAG/SWD to install your own ARM code or MBED, or Nordic libraries you won't be able to reload RFdigitals bootloader as they don' make that binary/hex available. I guess they figure if they made that available then everyone would install that on their hardware too and perhaps not buy their SOCs. That is why I say if you decide to go with installing MBED or Nordic firmware via JTAG you will loose all Arduino IDE, and SimbleeForMobile, for example, features.

The advantage of still using the Simblee SOC or the RFduino Module in your designs, if you go with custom low level programming,  is that it is the best packaging of the nRF51822 and assorted bits and pieces.. like the crystals and antenna. If I was running the company I would be selling boocoo of the chips and not care what people put on it. The money is in the condensed complete system on chips. And make the firmware open source so the community can fix and improves things mucho faster. And make the chips so cheap no one would want to waste their time designing in the nRF and support components on their own.



5
Production Application Guidance / Re: ICSP programming
« on: December 19, 2017, 11:55:54 AM »
And if you blow away the RFduino/Simblee firmware you are basically on your own. Might as well be programming with Nordics API or MBED at that point. Good luck and have fun!


6
Production Application Guidance / Re: ICSP programming
« on: December 19, 2017, 05:43:37 AM »
The USB programmer is just a USB to serial converter. It does not have a bootloader. The bootloader is built into the RFduino module. Have you found the documentation at RFduino.com? The JTAG SWD is only used if you want to blow away the RFduino/Arduino builtin bootloader and program at the lowest level.. which would be ARM Cortex M0.

7
Production Application Guidance / Re: ICSP programming
« on: December 18, 2017, 08:46:58 PM »
How did you prototype the board without knowing the answer?
There is no AVR ICSP.
Uses RS232 TTL RFduino programming using Arduino IDE.
Otherwise low level is programmed using JTAG SWD pins. Check the documentation for nRF51822.

8
Hopefully somebody from the RF Digital team will respond with an explanation of what is going on,

9
Simblee For Mobile / Re: App crashing
« on: December 08, 2017, 12:43:31 PM »
onDisconnect is useful to set or reset a flag that indicates if you are connected to a phone or not.
For example if there is no phone connected you don't want to be trying to send something to it.

10
Support / Re: Simblee for Mobile as USB keyboard
« on: December 06, 2017, 01:44:26 PM »
RFduino can not do SFM. Did you mean use a Simblee?

11
ONE mistake.

void SimbleeBLE_onReceive(byte *data, int len)

should be...

void SimbleeBLE_onReceive(char *data, int len)

12
Support / Re: Porting RFduino to Simblee
« on: November 03, 2017, 11:58:11 AM »
Yes, you can port RFduino sketches to Simblee. You do, of course, have to change the references to RFduino API to Simblee API, but everything you can do in RFduino you can do in Simblee. The reverse is not the case if you use advanced Simblee features.

I have some notes here...
https://thomasolson.com/PROJECTS/BLE/Simblee/

13
Support / Re: GZZL + BLE
« on: November 02, 2017, 03:57:21 PM »
There is an example under RFduinoGZLL with BLE. But the trick they are using is turning off BLE while you do GZLL and visa-versa. But, I think the problem arises that the phone looses the BLE connection when you turn off BLE on the RFduino.

Same trick to do it with Simblee. However...
What I want to do is connect to Simblee with Simblee for Mobile as the bridge to then communicate with my RFduino GZLL units using GZLL. There is no support to do this that I have been able to figure out. I want to take advantage of SFM and not have to write a dedicated APP(s). RFdigital suggested using SimbleeCOM, but of course, that doesn't work with RFduinos and the whole point is to get to use Simblee For Mobile with RFduino's even if via a bridge/gateway.






14
Support / Re: Changing Default UART Pins while uploading the sketch
« on: November 01, 2017, 10:45:16 AM »
The bootloader is hardcoded to GPIO 0 and 1. As is the firmware inside the RFduino/Simblee.

Simblee RXD (INPUT) is on GPIO 0 connects to the UART TXD.
Simblee TXD (OUTPUT) is on GPIO 1 connects to the UART RXD.
You can only change the serial port for your application during runtime.
It will always default back to 0,1 on reset.

15
Support / Re: Wake not working
« on: October 26, 2017, 09:02:25 AM »
How will that be different from systemOFF. You had said you have no noise when using that.

Pages: [1] 2 3 ... 59
anything