The LEDs on the expansion board and on the Omega2+ don't light up at all when power is applied.

I can see the Omega2+ write this out to the serial console using Putty on my host PC (115200 8N1):

Board: Onion Omega2 APSoC DRAM: 64 kB
relocate_code Pointer at: 7ff70000

This photo shows the Omega2+ is connected via COM5 because it's connected via a powered USB hub. It connects via COM3 when connected directly to the host PC.

Linux does not start up and the AP is not visible using a WiFi analyzer.

I've tried with different USB leads connected direct to the host PC and via a powered USB hub (which incidentally powers a Particle Photon, Olimex JTAG programmer and Logic Analyzer just fine), but I always get the same result.

The Omega2+ is plugged into the expansion board correctly as shown below.

I've checked the 5V and 3.3V power lines on the header socket with a digital meter and they are present. The RF screen on the Omega2+ does get warm but I would expect that.

Can someone tell me why it's not booting up?

Edited 24/12/2016 - added a couple of more photos to show the both rows of pins inserted into the headers and one of underneath the Omega2+ to show that no pins have folded inside underneath the board.

Please check out the link on the top (guidelines), if you do all the points there you probably got defective hardware ...

I'll try some other USB cables today and see if that makes any difference.

Further update:

• I've tried today with all the USB A to micro USB cables I have (about 7 of them) and I get the same result with each. At least the Omega2+ is getting power and I'm seeing output on the console so that proves it's powering up and it can talk to my host PC.
• I know that sometimes a device may not power up properly if it can't get enough current from its power supply so I tried powering the expansion board from a 5V 2A wall plug supply. The LEDs still don't light up so I'm assuming it's still not completing its bootup process.
• I haven't tried powering the expansion board via its USB A socket yet because I don't have a suitable USB A to A cable to hand. But I haven't seen anything in the Getting Started guide to say this would be an alternative way to power the Omega2+ anyway.

Thanks for the advice so far. Really looking forward to playing with this due to its tiny size.

Wondering if this is on the board as 2x64MB chips and one of them isn't responding.

No. It says 64KB, not 64MB.

I'm pleased someone else has the same problem as me, in that it's not an isolated problem, but I'm sorry you're in the same boat as me . I hope this spurs Onion to suggest what to do even if it's a return.

Nothing! My device won't boot....

Board: Onion Omega2 APSoC DRAM: 64 kb

relocate_code Pointer at: 7ff70000

Get out the hot air gun...and a SPI Flash writer.

It likely just has the wrong Das uBoot installed.
As in the bootloader code for a device with 64M RAM.
A small but important difference

Or maybe just send it back?

Shouldn't it say "relocate_code Pointer at: 87f60000" ?
Mine does

Of course it could be the RAM chip ... but you would need some hot air to fix that problem as well.

I stated on my support ticket that it could be the wrong firmware but haven't had any response from Onion about the issue at all.

Note that my board says:
Board: Onion Omega2 APSoC DRAM: 64 kB
but yours says:
Board: Onion Omega2 APSoC DRAM: 128 MB

Yours is reporting the correct amount of DRAM but I've got as much as a 1980's 8-bit CPU .

Board: Onion Omega2 APSoC DRAM: 128 MB

relocate_code Pointer at: 87f60000

Here all the boot sequence :

   ____       _             ____ 
 / __ \___  (_)__  ___    / __ \__ _  ___ ___ ____ _ 
/ /_/ / _ \/ / _ \/ _ \  / /_/ /  ' \/ -_) _ `/ _ `/ 
\____/_//_/_/\___/_//_/  \____/_/_/_/\__/\_, /\_,_/ 
W H A T  W I L L  Y O U  I N V E N T ? /___/" 

Board: Onion Omega2 APSoC DRAM:  64 kB 
relocate_code Pointer at: 7ff70000 

And then... nothing

If the flash were completely bad, you wouldn't see the initial banner, or really any sign of life at all, except (with a scope) ongoing traffic on the SPI lines as it tries and repeatedly fails to find some code to boot.

All this is to say: if U-boot reports only kilobytes of RAM available, not megabytes, the DDR2 RAM is bad or not soldered down properly. You could possibly reflow it, but it's a BGA-package and those are not easy to solder down even with proper tools. The other, recommended, option is to request a replacement from Onion.

I'm the OP and have followed the RMA procedure to the letter but have had no response from Onion other than to close my support ticket saying it will be resolved by the community. I got the ticket reopened on 28th Dec and it's still open with no response so far.

That's quite terrible, to be honest. Pinging @administrators might help, but they should have fixed this from the get-go and not just closed the ticket.

...had no response from Onion other than to close my support ticket saying it will be resolved by the community...

The best statement since long from onion ... kkk

It is really strange ... ppl who already have hardware from onion and know a bit how to deal with, are still waiting to get the new hardware ... And then they write the community should solve it ... what a strange Idea!!

@administrators, please let us have one FAQ with actual information!! Best made on Github.

If you have this issue, please create (or reopen) a ticket on the helpdesk and we will try to sort it out!

(Fortunately I ordered 2 and the other works fine)

In the meantime, I'm having great fun with Particle Photons that just work.