how to make it run?
#1
I'm honestly confused. please help Sad

I've bought SOEdge to just try what it can do, in my clusterboard but i'm not even able to start it....
here if founds some images and link for a guide how should flash it to the eMMC. However there is no guide for flashing it on clusterboard, and i'm really not sure if i should connect the usb (which one) on the clusterboard with SOEdge inside to my computer or what....
  Reply
#2
I had a similar problem. Same situation, SOEdge module in a clusterboard.

I flashed the factory test build image on the wiki to an eMMC module using the USB-to-eMMC adapter available in the store. What resulted had no partitions and did not boot at all. I was not even able to read the eMMC's contents after flashing. So, I figured the USB-to-eMMC adapter is not the right way to go for this image.

Then I tried the method mentioned in the guide using a Rock64. Good thing I had one of those to try! But, alas, I got the same result. After flashing the image, there was nothing readable or bootable on the eMMC.

Then, I bit the bullet, set up an Ubuntu 16.04 virtual machine (the SDK suggests/requires it), and built an image using the SDK. After a rather long build, I wound up with a set of images that needed to be flashed to the eMMC. I followed the instructions in the SDK and flashed the images using the Rock64 again, and still nothing winds up readable or bootable on the eMMC.

I am clearly doing something wrong. All of my experience with eMMCs on the Pinebook and Rock64 (and many other non-Pine boards) is not helping me here at all. It seems like the flashing process is not doing what it is supposed to.

I am going to order a SOEdge baseboard soon. Maybe I need one of those too, just to get the modules up and running? Any clues would be much appreciated.
  Reply
#3
yeah, some help would be appreciated.

Four months in and still didn't found any "solution" how to boot the SOEdge.
That leads me to two conclusions
1) it's working for everybody else and they are having too much fun with SOEdge, that they don't read it here
2) nobody knows how to make it run and therefore doesn't have the capacity to help us

i wonder what is it....
  Reply
#4
(08-06-2021, 08:18 AM)alembiq Wrote: yeah, some help would be appreciated.

Four months in and still didn't found any "solution" how to boot the SOEdge.
That leads me to two conclusions
1) it's working for everybody else and they are having too much fun with SOEdge, that they don't read it here
2) nobody knows how to make it run and therefore doesn't have the capacity to help us

i wonder what is it....

You also posted about the exploding batteries in the cluserboard, correct? So, does that mean you had just put them in without any operating system installed? I was hoping maybe you had a base image running at least.
  Reply
#5
Did any of you have success yet?
  Reply
#6
(11-02-2021, 09:03 AM)KNERD Wrote: Did any of you have success yet?


Nope, I gave up and sold my Clusterboard + SOPine / SOEdge modules on Ebay.  I am moving off grid, so I needed to downsize power hungry devices.  I am down to three Pine64 boards.  Everything else has been liquidated.


The SOPine modules worked fine.  I could never get SOEdge to boot anything at all.


Good luck to anyone still fighting this fight.
  Reply
#7
(11-02-2021, 06:58 PM)KRT Wrote:
(11-02-2021, 09:03 AM)KNERD Wrote: Did any of you have success yet?


Nope, I gave up and sold my Clusterboard + SOPine / SOEdge modules on Ebay.  I am moving off grid, so I needed to downsize power hungry devices.  I am down to three Pine64 boards.  Everything else has been liquidated.


The SOPine modules worked fine.  I could never get SOEdge to boot anything at all.


Good luck to anyone still fighting this fight.

Even with the SOEdge baseboard, still would not boot? Maybe defective?
  Reply
#8
(11-02-2021, 07:29 PM)KNERD Wrote: Even with the SOEdge baseboard, still would not boot? Maybe defective?

Confirmed.  The baseboard did not help at all. 

The part that I could not figure out at all was the "image" provided on the wiki (as well as the resulting image when I used the SDK to build one from source) was not like any other SBC image that I have ever seen.  I tried various methods of writing them onto SD cards and eMMC modules.  No matter what I tried, the resulting image (now on an SD card or eMMC module) did not have any partitions.  Usually, there is at least something like /dev/mmcblk0p1, and possibly /dev/mmcblk0p2 and /dev/mmcblk0p3 depending on the boot partition scheme.  However, every time I wrote the SOEdge test "image" to a card (yes, even using a USB-A male-to-male cable and a Rock64 like the instructions said to do), all that would ever result was a /dev/mmcblk0, the same thing you would get with an *unformatted* card.  I could never get beyond that point.  No partition meant nothing to mount or inspect.  Nothing would ever boot, no boot messages would pop up.  It was as if I was booting it without a card even installed, or worse.  I never even got any error messages to come across the serial console. 

I might have done something wrong, but I ran out of ideas.  Defective?  Possibly.  Not my call to make though.  I just gave up, ran out of ideas, moved on to something else.  That does not mean it is defective without a doubt, it just means that it was a nut that I was not able to crack.  I would not be surprised if a working image came along in the next few weeks/months, if for no other reason than Murphy's Law to make me look stupid and impatient.

I am just surprised that nobody else has chimed in here except disappointed owners.  Maybe if other devices start to get based on the same SoC, a working image will eventually emerge, or at least a fresh SDK that does not *require* Ubuntu 16.04, for crying out loud.  Confused
  Reply
#9
(11-02-2021, 11:09 PM)KRT Wrote:
(11-02-2021, 07:29 PM)KNERD Wrote: Even with the SOEdge baseboard, still would not boot? Maybe defective?

Confirmed.  The baseboard did not help at all. 

The part that I could not figure out at all was the "image" provided on the wiki (as well as the resulting image when I used the SDK to build one from source) was not like any other SBC image that I have ever seen.  I tried various methods of writing them onto SD cards and eMMC modules.  No matter what I tried, the resulting image (now on an SD card or eMMC module) did not have any partitions.  Usually, there is at least something like /dev/mmcblk0p1, and possibly /dev/mmcblk0p2 and /dev/mmcblk0p3 depending on the boot partition scheme.  However, every time I wrote the SOEdge test "image" to a card (yes, even using a USB-A male-to-male cable and a Rock64 like the instructions said to do), all that would ever result was a /dev/mmcblk0, the same thing you would get with an *unformatted* card.  I could never get beyond that point.  No partition meant nothing to mount or inspect.  Nothing would ever boot, no boot messages would pop up.  It was as if I was booting it without a card even installed, or worse.  I never even got any error messages to come across the serial console. 

I might have done something wrong, but I ran out of ideas.  Defective?  Possibly.  Not my call to make though.  I just gave up, ran out of ideas, moved on to something else.  That does not mean it is defective without a doubt, it just means that it was a nut that I was not able to crack.  I would not be surprised if a working image came along in the next few weeks/months, if for no other reason than Murphy's Law to make me look stupid and impatient.

I am just surprised that nobody else has chimed in here except disappointed owners.  Maybe if other devices start to get based on the same SoC, a working image will eventually emerge, or at least a fresh SDK that does not *require* Ubuntu 16.04, for crying out loud.  Confused

Have you contacted their sales support email to ask them what is going on?
I would expect a better written wiki for something they are selling.

I was looking at buying, but not now with all the complaints, and lack of input from them on what is going on. Even on the monthly posts, they would mentioned very little about the SOC.
  Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)