Anyone able to get SOEdge running?
Yes - Then how were you able to?
0%
0
No
100.00%
4
4 vote(s)
* You voted for this item. [Show Results]

Chickens, Eggs, and SOEdge - Part 2
#1
@gamelaster 


Quote:There isn't much information about SOEdge, because developers receiving prototypes only now, and it will take some time, but step by step, the wiki will be filled with information, so also I expect more information published on next community blog. About USB SDK and normal SDK, I tried to compare it without unpacking, there isn't much differences on first sight, need to unpack it and make some bigger comparison. I will write here with results.


And there is still is not much information. The only discussions are about unable to get them functioning, and wiki seems to be poorly written with lots of lacking of needed information to at least get it running.

I was considering ordering a set, but not in the condition it seems to be in now.

@tllim  mentioned about sending a unit to @klaven  but seems nothing from him on anything in his development.


Anyone know what is going on?
  Reply
#2
(11-23-2021, 09:36 AM)KNERD Wrote: @gamelaster 


Quote:There isn't much information about SOEdge, because developers receiving prototypes only now, and it will take some time, but step by step, the wiki will be filled with information, so also I expect more information published on next community blog. About USB SDK and normal SDK, I tried to compare it without unpacking, there isn't much differences on first sight, need to unpack it and make some bigger comparison. I will write here with results.


And there is still is not much information. The only discussions are about unable to get them functioning, and wiki seems to be poorly written with lots of lacking of needed information to at least get it running.

I was considering ordering a set, but not in the condition it seems to be in now.

@tllim  mentioned about sending a unit to @klaven  but seems nothing from him on anything in his development.


Anyone know what is going on?
This isn't hopeful, I was about to purchase one to add to a clusterboard I own.  Maybe I'll hold off.
  Reply
#3
(04-18-2022, 09:07 PM)revoman Wrote:
(11-23-2021, 09:36 AM)KNERD Wrote: @gamelaster 


Quote:There isn't much information about SOEdge, because developers receiving prototypes only now, and it will take some time, but step by step, the wiki will be filled with information, so also I expect more information published on next community blog. About USB SDK and normal SDK, I tried to compare it without unpacking, there isn't much differences on first sight, need to unpack it and make some bigger comparison. I will write here with results.


And there is still is not much information. The only discussions are about unable to get them functioning, and wiki seems to be poorly written with lots of lacking of needed information to at least get it running.

I was considering ordering a set, but not in the condition it seems to be in now.

@tllim  mentioned about sending a unit to @klaven  but seems nothing from him on anything in his development.


Anyone know what is going on?
This isn't hopeful, I was about to purchase one to add to a clusterboard I own.  Maybe I'll hold off.

I managed to chat with the person (gamelaster) doing the software and setup maybe back in February or March. He said he would do a live stream of a complete setup, but would not know when he could do it. I guess I can ask again.
  Reply
#4
@gamelaster

Could we have some guiding how to get shell by UART on SOEdge?
I experiment with that currently, no success. Same issues as for another guys at this forum.
Tried both Factory_Test_Build and BSP_Linux_ver_1.1_Build_from_SDK images from here: https://wiki.pine64.org/wiki/SOEdge

Wrote uncompressed image to SD card using just `dd`, but see nothing in UART and ethernet while booting it.

Rockchip Wiki tells that "The U-boot will make partition when first time boot up": http://rockchip.wikidot.com/linux-develop-guide#toc6
- but I don't see partitions on SD card even after boot.
Another option suggested there and here: https://forum.pine64.org/showthread.php?...#pid100414
is flashing by USB using rkflashloader, but I see only USB host described in SOEdge specs (not USB device or USB OTG). So I'm afraid to damage it or my PC if I connect two USB hosts by USB A <--> USB A cable.

As for UART, I failed to find pinout chart for SOEdge so used this info from Raspberry assuming they are same (SOEdge pins are labeled as "PI-2 GPIO"): https://www.raspberrypi.com/documentatio...pin-header
I have this USB UART adapter: https://pine64.com/product/serial-consol...er-edition
Set yellow jumper on 3.3V and connected to pins # 6,8,10 but still nothing in minicom/screen at my Linux host. Tried to swap TX/RX wires, no result.
Similar issues:
https://forum.pine64.org/showthread.php?...#pid100126
https://forum.pine64.org/showthread.php?tid=2922

Images seem to have custom format by Rockchip, can be unpacked by rkflashtool:
https://github.com/linux-rockchip/rkflashtool.git
https://github.com/ayufan-rock64/rkflashtool.git

There are UART-related parameters in "second" file inside boot.img (inside embedded-update.img, inside update-soedge-factory-test-2021-03-23.img)
and I see /etc/init.d/S50sshd inside rootfs.img - but still not sure if UART console and sshd are really activated at boot.

Any comments will be greatly appreciated!
  Reply
#5
(08-30-2022, 12:49 PM)qux Wrote: @gamelaster

Could we have some guiding how to get shell by UART on SOEdge?
I experiment with that currently, no success. Same issues as for another guys at this forum.
Tried both Factory_Test_Build and BSP_Linux_ver_1.1_Build_from_SDK images from here: https://wiki.pine64.org/wiki/SOEdge

Wrote uncompressed image to SD card using just `dd`, but see nothing in UART and ethernet while booting it.

Rockchip Wiki tells that "The U-boot will make partition when first time boot up": http://rockchip.wikidot.com/linux-develop-guide#toc6
- but I don't see partitions on SD card even after boot.
Another option suggested there and here: https://forum.pine64.org/showthread.php?...#pid100414
is flashing by USB using rkflashloader, but I see only USB host described in SOEdge specs (not USB device or USB OTG). So I'm afraid to damage it or my PC if I connect two USB hosts by USB A <--> USB A cable.

As for UART, I failed to find pinout chart for SOEdge so used this info from Raspberry assuming they are same (SOEdge pins are labeled as "PI-2 GPIO"): https://www.raspberrypi.com/documentatio...pin-header
I have this USB UART adapter: https://pine64.com/product/serial-consol...er-edition
Set yellow jumper on 3.3V and connected to pins # 6,8,10 but still nothing in minicom/screen at my Linux host. Tried to swap TX/RX wires, no result.
Similar issues:
https://forum.pine64.org/showthread.php?...#pid100126
https://forum.pine64.org/showthread.php?tid=2922

Images seem to have custom format by Rockchip, can be unpacked by rkflashtool:
https://github.com/linux-rockchip/rkflashtool.git
https://github.com/ayufan-rock64/rkflashtool.git

There are UART-related parameters in "second" file inside boot.img (inside embedded-update.img, inside update-soedge-factory-test-2021-03-23.img)
and I see /etc/init.d/S50sshd inside rootfs.img - but still not sure if UART console and sshd are really activated at boot.

Any comments will be greatly appreciated!

I had a short chat with him just now. He says some recent work has been done on the SOEdge with newest SDK ," with numerous fixes and new stuff!"

He pointed to this link to use for SOEdge

https://wiki.pine64.org/wiki/SOEdge#Linu..._ver_1.1.7

He also mentioned hopefully will be able to get a Debian image going as it will be easier than BSD.

That's all I could get out of him for now.



Let us know if you tried that already.



Also, you may want to try using Etcher to make the image instead of DD
  Reply
#6
(08-30-2022, 01:58 PM)KNERD Wrote: He pointed to this link to use for SOEdge

https://wiki.pine64.org/wiki/SOEdge#Linu..._ver_1.1.7

He also mentioned hopefully will be able to get a Debian image going as it will be easier than BSD.

That's all I could get out of him for now.

Let us know if you tried that already.

This link points to SDK source code, as far as I see. I did not build images by myself - assumed that prebuilt images have better chances to boot successfully.
There are only two of them at that SOEdge page, I tried both with same result:
http://files.pine64.org/os/SOEdge/stock/...1.1.img.gz
http://files.pine64.org/os/SOEdge/gamiee...-23.img.gz

Should they work at all? If they are bootable, how to get into the device after boot? UART, SSH, Telnet, Web, anything?

(08-30-2022, 01:58 PM)KNERD Wrote: Also, you may want to try using Etcher to make the image instead of DD

Thanks, I'll try it. The "Factory Test Build" image clearly references `dd`
  Reply
#7
It seems the Pine A64 and baseboard share some similarities. You may want to look here

https://wiki.pine64.org/wiki/PINE_A64-LT...ifications
.

Also there is a guide in the forum on connecting to the Pine A64 via serial
  Reply
#8
(08-30-2022, 02:37 PM)qux Wrote:
(08-30-2022, 01:58 PM)KNERD Wrote: He pointed to this link to use for SOEdge

https://wiki.pine64.org/wiki/SOEdge#Linu..._ver_1.1.7

He also mentioned hopefully will be able to get a Debian image going as it will be easier than BSD.

That's all I could get out of him for now.

Let us know if you tried that already.

This link points to SDK source code, as far as I see. I did not build images by myself - assumed that prebuilt images have better chances to boot successfully.
There are only two of them at that SOEdge page, I tried both with same result:
http://files.pine64.org/os/SOEdge/stock/...1.1.img.gz
http://files.pine64.org/os/SOEdge/gamiee...-23.img.gz

Should they work at all? If they are bootable, how to get into the device after boot? UART, SSH, Telnet, Web, anything?

(08-30-2022, 01:58 PM)KNERD Wrote: Also, you may want to try using Etcher to make the image instead of DD

Thanks, I'll try it. The "Factory Test Build" image clearly references `dd`

@qux Did you gave any luck?

Someone sent me this link on a sort of a guide they wrote up , and their experience working with it.

https://jsanchez.dev/#/projects/soedge
  Reply
#9
(10-07-2022, 07:09 AM)KNERD Wrote: @qux Did you gave any luck?

Someone sent me this link on a sort of a guide they wrote up , and their experience working with it.

https://jsanchez.dev/#/projects/soedge

In short, I have no success with booting anything on soedge for now.

My current understanding is following:

1) Images you referenced are bootable but they can't be written on sd card by dd as listed there. Some rockchip software and (maybe) USB connection are required.

2) For a successful case we shall see something in UART at least. Maybe something at ethernet interface as well.
Now we have correct UART pinout listed at soedge wiki page and it corresponds to what you pointed at (pins 6,8,10 at PI-5 bus, speed=1500000).

3) I found and tried following rockchip tools:

a) rkflashtool from https://github.com/linux-rockchip/rkflashtool.git or https://github.com/ayufan-rock64/rkflashtool.git

It can write flash, but I don't see commands related to flashing entire image for a first sight.

b) upgrade_tool from https://github.com/rockchip-linux/rkbin.git

It reports successful update for soedge connected by USB OTG. However OTG is not declared officially, so connect it at your own risk - it might damage soedge or your PC or both, I don't know.
Success is reported only when SD card is inserted - but nothing is really written there after "successful" update.
Internal flash is too small for the referenced images (128 MB vs 400-500 MB).
So it does not put anything in UART of course, something is definitely wrong.

Thank you for the link! I need to spend more time with it. Currently not getting why its author declares that emmc image did not boot but immediately after this  soedge appeared alive in UART somehow.
  Reply
#10
@KNERD
Thank you again - I got it alive! Something seems misaligned in the image so it can't find Linux kernel, but I can proceed.

Used `rkbin/tools/upgrade_tool uf update-soedge-factory-test-2021-03-23.img` with board's USB connected to my Linux PC by USB 3.0 A <--> USB 3.0 A cable.

EMMC was connected to SOEdge and uSD card was not inserted.

After that got following 9 partitions on EMMC.

jsanchez has 6/7 but it is more or less ok taking into account I used different flashing method.


    # parted /dev/sdb unit MB print
    Model: Generic STORAGE DEVICE (scsi)
    Disk /dev/sdb: 7818MB
    Sector size (logical/physical): 512B/512B
    Partition Table: gpt
    Disk Flags:

    Number  Start  End    Size    File system  Name      Flags
    1      8.39MB  12.6MB  4.19MB              uboot
    2      12.6MB  16.8MB  4.19MB              trust
    3      16.8MB  21.0MB  4.19MB              misc
    4      21.0MB  54.5MB  33.6MB              boot
    5      54.5MB  88.1MB  33.6MB              recovery
    6      88.1MB  122MB   33.6MB              backup
    7      122MB   189MB   67.1MB  ext2        oem
    8      189MB   1262MB  1074MB  ext4        rootfs
    9      1262MB  7818MB  6556MB  ext2        userdata


Attached Files
.log   uart_initial_boot.log (Size: 5.31 KB / Downloads: 134)
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  New to the ecosystem - Bought the SOEDGE MrAnthony 11 10,189 02-04-2022, 03:12 PM
Last Post: KNERD
  console on SOEDGE Model A Baseboard bertiewooster 4 4,943 10-01-2021, 11:58 PM
Last Post: bertiewooster
  Chickens, Eggs, and SOEdge lewellyn 11 16,270 11-21-2020, 08:13 PM
Last Post: tllim

Forum Jump:


Users browsing this thread: 1 Guest(s)