Omega2+ not starting up
No, not the flash, the DDR2 RAM, or more likely the connections between that and the SoC. It's crashing at the point where it tries to move itself from Flash to RAM - that's what the "relocate_code Pointer" is about. And it's happening after quite obviously not finding the populated DDR2 size.
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.
@Chris-Stratton I don't quite know why you had been voted down, because you are correct: 1) The U-boot loader resides on the SPI-flash, and the Omega2 wouldn't even be able to get that far, if the flash was broken or soldered poorly. 2) The fact that U-boot only reports 64kB RAM instead of 64MB quite clearly spells out exactly what the problem is: the SoC has 64kB built-in instruction-cache SRAM, but it clearly cannot initialize the external DDR2 RAM.
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. Please Onion, a month has passed and I've had no advice from you or the community how I get my device running (I don't have solder reflow capabilities, besides it will invalidate any warranty with you). There's at least 3 of us now that have the same problem @Johan-Charpentier @Wai-Weng-Kong . Help please...
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.
@DrWheetos and all others with the same issue:
I'm sorry that your ticket was closed with no real resolution! Our support hasn't been all that great lately and we definitely want to improve on that end, so we've made some staffing and procedure changes on the support side.
If you have this issue, please create (or reopen) a ticket on the helpdesk and we will try to sort it out!
@Lazar-Demin Thanks Lazar. I can see that one of your hardware designers is working on my ticket now.
I'm going through the same as you. Banner only over the serial, month old ticket that got closed, zero comforting comments, now assigned to a designer (I'm not convinced). Let us know if you have any progress!
(Fortunately I ordered 2 and the other works fine)
@Hummed Another week on and still no update on my ticket. And to rub it in I get an email broadcasted from Onion today to say creating a ticket is the best way to resolve an issue. Maybe it's because of the Chinese new year celebrations. Still it's encouraging that I'm not the only one with this issue.
In the meantime, I'm having great fun with Particle Photons that just work.
I have also encountered the same problem.
Is not this an initial malfunction?
Onion should do a technical investigation, but I do not have to wait for the result.
Please exchange immediately.
(My ticket number is 5296.)
Someone had an update on this issue (Ticket or something) ?
Got a nice update on ticket, my unit will be replaced.
For thoses who still wait a reply, don't worry they will answer it.
No update on my ticket as yet. It has been closed again with no indication of what course of action I should take. I've been waiting almost 3 months now. I'll re-open the ticket and ask for a resolution.
At last, a result. Onion will be sending a replacement in the next shipping batch. Better late than never.
@Lazar-Demin OK, so it's been almost 2 months now and despite my ticket being closed 3 times saying it's been resolved, and a promise of a replacement Omega 2+ which would be delivered within 2 weeks from 14th March, it hasn't happened. So I've raised a new ticket (#8161) because I can't re-open the old one. To say the least, I'm very disappointed to have paid for this last year and I'm still waiting nearly 6 months later. Not an easy introduction to Kickstarter for me!
@Johan-Charpentier Did you get a replacement?
Just for the record, I've received my Omega 2+ and it's working fine. With the help of the community, I've got the LEDE cross compiler working in a hyper-v machine and a hello world C program running on the Omega. Nice! Now to start something a bit more adventurous. :smile:
@DrWheetos I have this problem also.
So the outcome is the hardware fault correct? And anybody who encounters this problem should get a replacement?
I just got a new 2+ and same relocate error. Has this been solved? Is there a fix? WTF? this is a year later, you would think they test these things before shipping. I also got a onion 2 at the same time. It was tested because the pins were bent from de-insertion. The pins were straight on the 2+. Not saying they didn't, but sure looks like its not tested. I Always order at least 2 of everything when I'm developing. Can't say how much time it has saved me but its huge.