@Pavel-Metrokhin какая-то странная ситуация, вы открещиваетесь от дальнейшей поддержки девелоперской платы, выпущенной вашей компанией как раз для разработки в случае, если дефолтное состояние было нарушено (в моем случае - стер загрузчик, причем стер средствами нативного кода, зашитым при покупке самой платы), при этом проблема не возникла из неоткуда, а наблюдалась с самого начала получения мной платы (наша ранняя беседа в хелпдеске) - и, с учетом, частоты вашей поддержки я искал пути решения проблемы, которая не позволяла мне пользоваться полноценно покупкой. Ваш бутлоадер мне помог стартовать плату, но bootcmd по умолчанию настроен на tftp инициализацию, при покупке не было указано, что для работы платы требуется ваш док, я использую свои макеты, не вижу смысла покупать новую плату из-за того, что ваша компания не дает компетентной поддержки
Best posts made by Ilya Mordasov
Latest posts made by Ilya Mordasov
RE: Copy firmware from usb
RE: Copy firmware from usb
@cas Sure I read this docs and didn't have troubles with it, but now, when I choose option 2 (Flash firmware from USB storage) I stuck with TIMEOUT issue
*ERROR: CTL:TIMEOUT X BBB_reset usb_control_msg: request: 0xFF, requesttype: 0x21 value 0x0 index 0x0 length 0x0 ERROR: CTL:TIMEOUT X
I found out that usb works fine if I reset USB bus, so that I enter in command line mode and execute the commands I wrote above.
If I put my firmware to the address 0x80000000, that I have LZMA error (I guess it's okay, because it seems to me uboot is there), so now I put omega2.bin to 0x80800000, and it's started booting, but returned me to the first screen (forgot to log it), of course, after rebooting my RAM is free, so how can I transfer omega2.bin to local storage to boot from firmware?
Here is my log file after bootm 0x80800000
Copy firmware from usb
I can't install firmware from usb storage, always stuck. I entered in boot's console mode and executed this commands:
fathead usb 0:1 0x80000000 omega2.bin // this copy my omega2 file into RAM starting with 0x80000000
after this my omega is rebooting and I see the welcome screen again.
upd: according to log file
FAT: 7078054 Bytes read Omega2 # bootm 0x80000000 ##Booting image at 80000000 ... Image Name: MIPS LEDE Linux-4.4.46 Image Type: MIPS Linux Kernel Image (lzma compressed) Data Size: 1311622 Bytes = 1.3 MB Load Address: 80000000 Entry Point: 80000000 Verifying Checksum ... OK Uncompressing Kernel Image ... LZMA ERROR 1 - must RESET board to recover
how can I transfer omega2.bin file from usb to local storage of omega to boot from this one? I'm not able to use ethernet
Omega2 can't recognise the SPI flash
Hi, I previously accidentally erased my flash with uboot, and don't have backups. So I decided to compile from this repo https://github.com/OnionIoT/omega2-bootloader new boot loader. Everything is ok, and I got uboot.bin
After that I upload this uboot.bin to my SPI flash (it's a SOIC8 W25Q128FV) via flashrom, but flashrom couldn't upload it successfully because the firmware size didn't match flash's size, so I truncated this file to get expected size and tried again. Flashrom flashed the uboot.bin file and verified it without errors. Next, I soldered it back to omega2 (I remembered where was the key) and now my console shows only this
I checked the soldered pins, everything is ok, maybe I missed something?
And one more question: I found my old logs, there was W25Q128BV recognised chip instead of W25Q128FV (this is marked on the chip)
Or may someone upload the backup of boot loader for omega2 (not plus)
RE: Flash boot loader via flashrom, image doesn't match the flash chip's size
@Douglas-Kryder for what? Pine is just simple dev board, ok, raspberry shows the same error, should I go to raspberry forum? I use flashrom, pine64 is connected by spi, and is used for communication only
upd: I resized uboot.bin up to required size and flashed it without errors, tomorrow I will solder it back to omega2 and test it
Flash boot loader via flashrom, image doesn't match the flash chip's size
I'm trying to flash compiled from here https://github.com/OnionIoT/omega2-bootloader the new bootloader via flashrom.
Flashrom recognised my spi flash
root@pine64:~# sudo flashrom -p linux_spi:dev=/dev/spidev0.0 flashrom v0.9.9-rc1-r1942 on Linux 3.10.105-0-pine64-longsleep (aarch64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Winbond flash chip "W25Q128.V" (16384 kB, SPI) on linux_spi. No operations were specified.
But when I try to upload uboot.bin I get an error:
root@pine64:~# flashrom -w /home/ubuntu/uboot.bin -p linux_spi:dev=/dev/spidev0.0 flashrom v0.9.9-rc1-r1942 on Linux 3.10.105-0-pine64-longsleep (aarch64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Winbond flash chip "W25Q128.V" (16384 kB, SPI) on linux_spi. Error: Image size (173544 B) doesn't match the flash chip's size (16777216 B)!
How to resolve it?
RE: How to flash uboot after full erasing?
Yes, I already read this one, but it’s not my case. I erased everything: bootloader, kernel, firmware. Seems, my omega is empty.
Theoretically, i could flash uboot via some JTAG, but I have to resolder spi flash to do that. Moreover, guess it’s a BGA chip and I’m not familiar with soldering bga.
What I have now is the connection between my laptop and this board over serial (which even shows nothing). My question is the way to reflash uboot over serial with clear Flash memory
How to flash uboot after full erasing?
I accidentally erased everything on my omega2 via console
is there way to flash boot loader again, cause after that I got brick, even led doesn't blink. I only see that something like CP2102 (my serial on omega) connected to my laptop.
RE: What is the stable firmware version for omega2?
Thanks for your reply. I thought the same that 0.1.10 is more stable that previous, looked at changelog. But at first, I stucked in issue when I have to set internet connection via browser. Not always I see my ssid in the available networks list and usually type it manually. Even after that when I’m pressing configure it can freeze in this half-state. I’d prefer to set it using wifisetup over ssh or console.
Also I tried to use lede repos instead of onion’s, but with it I got error relocating errors for wget and missed libencrypt.so
Traceroute shows that I have access to the internet.
But to be honest, I use my own extension board, but I’m not sure this is the reason. If I had the problem with it my o2 wouldn’t work. And o2 gets 3.3v of power and enough current
Yep, I created ticket on onion’s helpdesk and sent them logs.