I've been poking around on the i2c applications, seeing if I can use i2cset to interact with the OLED. So far, nothing.
A
Andrew Donnelly
@Andrew Donnelly
1
Reputation
13
Posts
1239
Profile views
0
Followers
0
Following
Best posts made by Andrew Donnelly
-
RE: Oled Screenposted in Omega Talk
Latest posts made by Andrew Donnelly
-
I have an Omega from Kickstarter shipment that does not bootposted in Omega Talk
The instructions here https://wiki.onion.io/Tutorials/Reflash-The-Firmware-With-Ethernet-Expansion do not apply. Why might you ask? I have the testing firmware that was loaded to test the boards.
U-Boot 1.1.4 (Aug 28 2015 - 16:51:26) AP121 (ar9331) U-boot DRAM: 64 MB Top of RAM usable for U-Boot at: 84000000 Reserving 140k for U-Boot at: 83fdc000 Reserving 192k for malloc() at: 83fac000 Reserving 44 Bytes for Board Info at: 83fabfd4 Reserving 36 Bytes for Global Data at: 83fabfb0 Reserving 128k for boot params() at: 83f8bfb0 Stack Pointer at: 83f8bf98 Now running in RAM - U-Boot at: 83fdc000 Flash Manuf Id 0xef, DeviceId0 0x40, DeviceId1 0x18 flash size 16777216, sector count = 256 Flash: 16 MB Using default environment In: serial Out: serial Err: serial Net: ag7240_enet_initialize... No valid address in Flash. Using fixed address No valid address in Flash. Using fixed address : cfg1 0x5 cfg2 0x7114 eth0: 00:03:7f:09:0b:ad eth0 up : cfg1 0xf cfg2 0x7214 eth1: 00:03:7f:09:0b:ad athrs26_reg_init_lan ATHRS26: resetting s26 ATHRS26: s26 reset done eth1 up eth0, eth1 Hit any key to stop autoboot: 0 ar7240> help reset - Perform RESET of the CPU ? - alias for 'help' boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcmd' bootm - boot application image from memory cp - memory copy erase - erase FLASH memory help - print online help md - memory display mm - memory modify (auto-incrementing) mtest - simple RAM test mw - memory write (fill) nm - memory modify (constant address) ping - send ICMP ECHO_REQUEST to network host printenv- print environment variables progmac - Set ethernet MAC addresses run - run commands in an environment variable setenv - set environment variables tftpboot- boot image via network using TFTP protocol version - print monitor version ar7240> printenv bootargs=console=ttyS0,115200 root=31:02 rootfstype=squashfs init=/sbin/init mtdparts=ar7240-nor0:256k(u-boot),64k(u-boot-env),2752k(rootfs),13184k(uImage),64k(NVRAM),64k(ART) bootcmd=bootm 0x9f300000 bootdelay=4 baudrate=115200 ethaddr=0x00:0xaa:0xbb:0xcc:0xdd:0xee ipaddr=192.168.1.2 serverip=192.168.1.10 stdin=serial stdout=serial stderr=serial ethact=eth0 Environment size: 361/65532 bytes ar7240>I need instructions to completely reflash this with the correct U-Boot and firmware. Serial works, if you can give me a TFTPBOOT capable image to load to the device I could boot from memory and flash it that way. Otherwise, it's useless and I'd like to get a replacement.
-
RE: Unable to useposted in Omega Talk
Where are the instructions because I got one just like this with the wrong firmware flashed on it and I've been waiting for said instructions forever. I have an expansion dock and ethernet expansion already.
-
RE: Will not bootposted in Omega Talk
@Boken-Lin Yes, I do, how else would I get the TFTP to work like I did? Wifi doesn't work in the bootloader.
-
RE: Oled Screenposted in Omega Talk
I've been poking around on the i2c applications, seeing if I can use i2cset to interact with the OLED. So far, nothing.
-
RE: Will not bootposted in Omega Talk
@Boken-Lin said:
@Andrew-Donnelly Oh, it seems that you are not using our uboot. 0x20000 only works with our uboot. Not sure which uboot you are using.
I'm using your manufacturing build's U-Boot. Please look at thread https://community.onion.io/topic/56/omega-doesn-t-to-appear-to-be-working and you'll see I have the same U-Boot as the other guy and it was advised to him that he had the manufacturing build of the OS and U-Boot on his device, same as mine. All I'm asking for is instructions to flash the device over from the manufacturing TEST BUILD to the current official build, there must be a way to do it, otherwise how could you have flashed all those devices before shipping them out?
-
RE: Will not bootposted in Omega Talk
@Boken-Lin said:
@Andrew-Donnelly I can confirm that if you have a stable firmware compiled for the Omega, you can just write it at 0x20000. That's what's typically done by the httpd server within uboot anyways.
So the latest build on the repo server, I should be able to copy into memory from tftp, and then write out to 0x20000 and i should be able to get this up and online, correct?
I tried the following: I downloaded the latest build from repo, v0.0.4-b216.bin to my tftp server and renamed to 3700A8C0.img (the IP address hex backwards (little-endian)).
ar7240> setenv ipaddr 192.168.0.55 ar7240> setenv serverip 192.168.0.1 ar7240> ping 192.168.0.1 Using eth0 device host 192.168.0.1 is alive ar7240> tftpboot *** Warning: no boot file name; using '3700A8C0.img' Using eth0 device TFTP from server 192.168.0.1; our IP address is 192.168.0.55 Filename '3700A8C0.img'. Load address: 0x81000000 Loading: * TFTP error: 'File not found' (1) Starting again eth1 link down FAIL *** Warning: no boot file name; using '3700A8C0.img' Using eth0 device TFTP from server 192.168.0.1; our IP address is 192.168.0.55 Filename '3700A8C0.img'. Load address: 0x81000000 Loading: T TFTP error: 'File not found' (1) Starting again eth1 link down FAIL *** Warning: no boot file name; using '3700A8C0.img' Using eth0 device TFTP from server 192.168.0.1; our IP address is 192.168.0.55 Filename '3700A8C0.img'. Load address: 0x81000000 Loading: T #T ######################################################################### # ######################################################################### ########################################################################### ########################################################################## ########################################################################## ########################################################################### ########################################################################## ########################################################################## # ######################################################################### ########################################################################### ########################################################################## ########################################################################## ########################################################################### ########################################################################## ########################################################################## # ######################################################################### ########################################################################### ########################################################################## ########################################################################## ########################################################################### ########################################################################## ########################################################################## # ######################################################################### ########################################################################### ########################################################################## ########################################################################## ########################################################################### ######################################################################## ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ####################################################### done Bytes transferred = 16252928 (f80000 hex) ar7240> md 81000000 81000000: 01000000 4f70656e 57727400 00000000 ....OpenWrt..... 81000010: 00000000 00000000 00000000 72343734 ............r474 81000020: 30300000 00000000 00000000 00000000 00.............. 81000030: 00000000 00000000 00000000 00000000 ................ 81000040: 04700001 00000001 00000000 6c30ff2c .p..........l0., 81000050: cfe8e07f a262e471 ed1a85a0 00000000 .....b.q........ 81000060: 00000000 00000000 00000000 00000000 ................ 81000070: 00000000 80060000 80060000 00f80000 ................ 81000080: 00000200 00116268 00100000 005f602a ......bh....._`* 81000090: 00000000 00000000 00000000 00000000 ................ 810000a0: 00000000 00000000 00000000 00000000 ................ 810000b0: 00000000 00000000 00000000 00000000 ................ 810000c0: 00000000 00000000 00000000 00000000 ................ 810000d0: 00000000 00000000 00000000 00000000 ................ 810000e0: 00000000 00000000 00000000 00000000 ................ 810000f0: 00000000 00000000 00000000 00000000 ................ ar7240> cp 0x81000000 0x20000 0xf80000 ar7240> reset Unknown command 'reset' - try 'help' ar7240> U-Boot 1.1.4 (Aug 28 2015 - 16:51:26) AP121 (ar9331) U-boot DRAM: 64 MB Top of RAM usable for U-Boot at: 84000000 Reserving 140k for U-Boot at: 83fdc000 Reserving 192k for malloc() at: 83fac000 Reserving 44 Bytes for Board Info at: 83fabfd4 Reserving 36 Bytes for Global Data at: 83fabfb0 Reserving 128k for boot params() at: 83f8bfb0 Stack Pointer at: 83f8bf98 Now running in RAM - U-Boot at: 83fdc000 Flash Manuf Id 0xef, DeviceId0 0x40, DeviceId1 0x18 flash size 16777216, sector count = 256 Flash: 16 MB Using default environment In: serial Out: serial Err: serial Net: ag7240_enet_initialize... No valid address in Flash. Using fixed address No valid address in Flash. Using fixed address : cfg1 0x5 cfg2 0x7114 eth0: 00:03:7f:09:0b:ad eth0 up : cfg1 0xf cfg2 0x7214 eth1: 00:03:7f:09:0b:ad athrs26_reg_init_lan ATHRS26: resetting s26 ATHRS26: s26 reset done eth1 up eth0, eth1 Hit any key to stop autoboot: 0 ## Booting image at 9f300000 ... Bad Magic Number -
RE: Will not bootposted in Omega Talk
@Theodore-Borromeo said:
@Andrew-Donnelly what is the format it requires? I'm pretty sure tftpboot can accept a bin, uImage or ELF executable. The biggest issue, I would think, is figuring out the hex offset that said images/binaries would need to be flashed at. . . @Boken-Lin can probably assist in that via contact with the manufacturers or a priori knowledge of the platform's memory layout
I got that far, but when I flashed the U-Boot was still looking in the wrong location and throws bad magic number when I try to boot from that location. I want to quickly confirm with devs if the firmware image that I listed on this post is indeed cleared to be flashed to this hardware, and if so, just start writing it at 20000?
I work on the hardware and OS sides of the equipment, I don't normally do programming other than flashing systems from boot. We use a modified version of U-Boot at work too with some extra tools built in, the httpd server is a great public alternative to what we have baked into ours.
-
RE: Will not bootposted in Omega Talk
@Boken-Lin Not from this format, I'm going to dig into the new firmware file's structure and see if I can't find the updated version of U-Boot and extract it, I figure if I can get that to load over tftpboot, then I could possibly trigger the httpd from that and upgrade.
Update: I tried extracting the U-Boot from the working Omega and tftpbooting that on the bricked one, and no dice, "Bad Magic Number" same as the rest of my attempts.
-
RE: Will not bootposted in Omega Talk
@Theodore-Borromeo There is a tftpboot option, though it requires a different format than the BIN file we're given for firmware updates.
-
RE: Omega doesn't to appear to be workingposted in Omega Talk
@Lazar-Demin I think you misunderstood. I'm not getting httpd in U-Boot, I'm getting httpd in the pre-release firmware that I posted a snapshot of the output of. If you read line by line my 2 console outputs, you'll see which httpd server I'm starting. I'm already booted into the pre-release bench-test linux before I can run it. Please read the output I provide you, again, I work on this kinda stuff for a living, so the output I give you should be useful, make use of it or it's for naught.
@Lazar-Demin said:
@Andrew-Donnelly you're able to get httpd running with the Ethernet Expansion?
Download the latest firmware from: http://repo.onion.io/omega/images/omega-v0.0.3-b213.bin
Use that to reflash your Omega.I will say this, that filename is super helpful, since now I think I can tftpboot off that and manually push the firmware by invoking an upgrade from the console! And U-Boot refuses to directly load that firmware update file, dang.
I have a question, can I use dd to flash this .bin file to the "DOA" Omega? I mean I can get into the pre-release environment, I can get on the network without issue, heck, it looks like there's enough facilities here to pull the image across the network to load it, so what say you and your team? /dev/mtd2 ?
Well I've been playing around and trying to get this thing flashed. I'm still able to get into U-Boot so provided a bootable tftpboot image can be made available, I can quickly write up instructions on how to recover the device from scratch if needed.