-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x96max+ a100 支持写入emmc使用 #779
Comments
amlogic-s9xxx-armbian/build-armbian/armbian-files/common-files/etc/model_database.conf Line 118 in 259107e
百兆应该是选517吧,你先在USB里修改下/boot/uEnv.txt里的dtb名称为meson-sm1-x96-air.dtb,然后重启,确认选择正确的话再写入emmc,选择517 |
按照上述操作,修改了 uEnv.txt,启动进入 TF 卡上的 armbian 并运行 armbian-install,选择 517 后写入 emmc 后重启,屏幕和之前变砖不同,虽然还是全黑,但 led 屏幕的背光是亮的,即不能显示任何信息。也不能正常启动 emmc 上的 armbian |
安装时用:armbian-install -m yes |
你之前用的哪个dtb |
我记不清之前用的哪个 dtb 了,那几个 dtb 我都试过了,还是一样 |
你先改下uEnv.txt里的dtb为meson-sm1-sei610.dtb,改完重启,如果可以正常从tf卡启动,网络也没问题再写入emmc 在5.15内核里,u-boot如果不需要也可以启动,就可以不添加 |
5.15 内核里,用 meson-sm1-sei610.dtb 可以正常从 emmc 启动进入系统,无线网络没问题。我不太需要用到有线,就没试 |
你就改这个dtb测试,写入emmc时选0手动输入。测试没问题的话添加一条配置信息,以后就选ID。 |
内存少了就复制u-boot重启 u-boot-x96maxplus.bin 复制为 u-boot.emmc |
我在另外一个帖子里看到了,a100盒子用 meson-sm1-sei610.dtb 有线、无线、蓝牙都可以使用 |
盒子已经没了,我一直用主板。照片稍后整理发出 我是用 u盘 启动,进入 u盘 自己的 armbian 之后,把 mmcblk2p1 mount 到一个目录下,进行的 copy 操作,没有重新运行 armbian-install 命令 |
u盘是u-boot.ext |
|
还是之前说的那个问题,emmc 不能启动 armbian。把 u-boot.emmc 删除后,能进入 armbian,但内存只识别出 1G |
SlimBox 固件下载地址 |
在usb里把u-boot-x96maxplus.bin 复制为 u-boot.ext可以启动?这时内存是正常的吧。 |
你是复制的还是改名的?只能复制不能改名,不要把u-boot-x96maxplus.bin整没了,不然写入emmc时缺少文件无法复制。 |
这个帖子里使用5.10内核。这个肯定需要u-boot才能启动,他存储32G不知道他使用的是emmc还是tf卡。 按理说tf能用的u-boot,在emmc里也没问题,你这是第一个反应只能usb使用的现象。 |
你会救砖的话,可以试试在 刚才给你添加的 写入时还是使用命令: USB使用u-boot.ext能使用的原因之一,是因为USB里的固件里添加MAINLINE_UBOOT |
这样就可以了! |
添加MAINLINE_UBOOT可以了? |
是的,你更新一下 /etc/model_database.conf 吧 |
I have already done those steps. But when I do And if I do |
which kernel are you using |
I have tried 5.15/5.10/5.4 |
please send pictures of your board |
export to dtb |
try #788 |
This is the dtb that I have extracted from my box |
The dtb you provided in the first post cannot be decompiled. The file is damaged. used |
I have used this way to extract the dtb Should I try the method you have just provided? |
yes |
try to open the error file The dtb you provided in the first post cannot be decompiled. The file is damaged. if you can export the DTS |
Hello @D-Sta install select the 523 and after feedback |
Hi @tv4you2016 |
@tv4you2016 I have tried to boot from the this image, but with no success. But this image seems different that those build for s905x3. This image has only 1 partition called |
@D-Sta https://github.com/ophub/amlogic-s9xxx-armbian/actions |
OK, thanks. Waiting for the build to complete. |
describe the procedures you performed |
With the exact same setup and method, but only using
|
put the dtb in the folder?? |
@D-Sta follow the following steps:
|
I can say that this works, because I did it in the box of @luucasmooreira #784 |
Yes it works. Congratulations to @tv4you2016 |
@D-Sta build completed follow the following steps: install select the 523 and after feedback |
Thanks @tv4you2016! I used the previous build, but used the DTB you have provided
and update the /etc/model_database.conf and after installing the system to the emmc, everything is working fine, WIFI + 4GB RAM + Ethernet. But can you please provide some information about the solution? How is the new meson-sm1-x96-max-plus-q1.dtb different from the old one (which did not boot at all). Regards |
Device Information | 设备信息
Armbian Version | 系统版本
Describe the bug | 问题描述
用2022年6月份的版本,具体记不清了,也是jammy,内核5.15把,已经刷机成功,并正常写入 emmc ,也是一直能够正常运行
最近想折腾一下桌面环境,自己装老是有各种报错,非常苦恼。看了现在最新的版本,有 armbian-software 命令,可以比较方便地一键安装桌面环境,故想要重新刷机。
把现在最新的 release 正常刷进 TF 卡,通过 TF 卡启动,然后运行 armbian-install 来写入 emmc 后,再断电,拔 TF 卡,插电,一直黑屏,估计是变砖了。
用线刷刷入 sbx_x96max_plus_a100_atv_15_4_1.img,回到 SlimBox,再捅菊花,通过 usb读卡器加载 TF 卡,启动进入 armbian,再次运行 armbian-install 写入 emmc,变砖情况依旧。
变砖是连开机的 logo 都看不到,之前开机是有一个 x96max+ 的动画的,我是不是把某些更底层的启动代码给洗掉了?
The text was updated successfully, but these errors were encountered: