I am trying to set up my piko blx fc and the Betaflight set up page says no dataflash chip found. What does this mean? Is this what is preventing the receiver to not be recognized?

Are you flashing the board? Plug it in having bootloader pins shorted. That can be only my case, but I had to use zadig to switch USB drivers to winUSB.
Check this video out:



If you have to try zadig, read this: https://prestongarrison.com/flashing-cc3...aceflight/ just ignore all raceflight/revo stuff. you use it the same way.

And what does the receiver has to do with it?

The board is already flashed and all Betaflight parameters have been set up now that the board is all soldered with all components. In Betaflight the page called receiver does not show any movement from the tx sticks or switches. What does "no datachip found"?  Betaflight shows that it is flashed and all set up, just no radio receiver showing.

Sorry, it says "no dataflash chip found"

Can you show a screen shot of the betaflight tab where this message is shown (or describe exactly the place in betaflight the message shows)?

Also, what receiver have you attached and how (ppm sbus spektrum, etc)? Is the receiver successfully bound to the transmitter? We need a bit more information to help you.

            Frysky x4r bound, green LED, s bus set up on Betaflight and wired correctly 

I really appreciate help. I did set up my first piko board with no problem.

Did you short ppm or sbus pads on fc?

It means that the FC doesn't have any flash memory for storing blackbox logs. It is nothing wrong as there are several FCs that doesn't have it

(04-Feb-2017, 07:31 AM)KonradS Wrote: Did you short ppm or sbus pads on fc?

CaCondor, thanks for posting the extra information.

From the photo, it looks like the proper pads are bridged for sbus.

Just checked mine, I've got the same dataflash message, but that just means there's no blackbox memory available on board (and there is not) so that's no problem.

Only thing I can think of is that maybe a stray blob of solder somewhere (bridge).  [I'm assuming that you are performing the same sequence in testing the receiver that you did with your other piko.]

EDIT: I don't know if it's the same for your Rx (I use spektrum), but I always make sure my Tx is turned on before supplying power to the board when testing in the receiver tab.

Ready Made RC is graciously sending another board. I have been doing a lot of on line research about problems with the Piko Blx board and found many who have bought one have had problems with them. That's not to say they are a bad product, but the quality control is. As mentioned, my first one had the bad 5v regulator, which is a common problem with some of the first batches. They say, "third time's the charm" so maybe there's hope. If not, it might be "3 strikes, you're out" : )

Yes, I did solder over the s bus pads.

CaCondor,
please as a sanity check validate (while waiting for new board),
in config UART 3 is set to Serial RX, and in the later part you have set the sbus/ibus (whatever protocol you use)

also look into this pdf that might come in handy
http://furiousfpv.com/dev/Piko%20BLX%20FC%20Manual.pdf

Ready Made rc sent another Piko board. 

I hooked it up to Betaflight and saw that it is preflashed with 3.0.1

I proceeded to set up the board parameters.  The board does not reconnect after cli commands although it tries. You must choose another comm port from the one that is default to connect.

It doesn't seem normal for the board to disconnect after parameters are saved. Sometimes it does stay connected. Yes, my USB cord is a good one and tested.

THE PLAN

I will start by soldering sbus pads together and then add the power wires followed by the receiver. I will add the rest of the hardware when and if I see the receiver and my Taranis talking.

  Do you think it's normal for the board to disconnect after saves?  I haven't had Naze or other fc boards do this.

Wish me Luck.

My RE1 typically disconnects on save, but always reconnects with no problem, so I don't fret about it. F3 never disconnected in Cleanflight so maybe it's just a Betaflight function.

(11-Feb-2017, 01:12 AM)CaCondor Wrote: Do you think it's normal for the board to disconnect after saves?  I haven't had Naze or other fc boards do this.

It's normal to me, with many different boards. Yes sometimes they do reconnect after CLI, but most of the times i have to either re-start the configurator (in that case usually the board ID number keeps increasing each time i try to connect), and sometimes i have to physically unplug and reconnect the board too.

Thanks, glad to know I am not loosing my mind.