Posts made by N Willems

Thanks for your assistance, great support!

@Boken-Lin We made it!

@Boken-Lin , I tried, but I can only get to step 4, no httpd.
However, I configured my laptop's networkinterface, and I can ping just fine over the ethernet. And I see a tftpboot command. If I'm not mistaken I only need the correct arguments for it.

Here the output:
(sorry I don't know how to make a codeblock, <pre><code> does not seem to work)

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>** httpd
Unknown command 'httpd' - try 'help'

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>** ping 192.168.1.10
dup 1 speed 100
Using eth0 device
host 192.168.1.10 is alive

**ar7240>** tftpboot
*** Warning: no boot file name; using '0201A8C0.img'
Using eth0 device
TFTP from server 192.168.1.10; our IP address is 192.168.1.2
Filename '0201A8C0.img'.
Load address: 0x81000000
Loading: T T ^C
Abort

**ar7240>** ?
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

@Boken-Lin
I received the ethernet expansion and matching dock today

@Boken-Lin Thanks man!

@Boken-Lin Any news on this? Haven't heard from you guys since my confirmation.

@Boken-Lin
No worries, I assume you guys are under a lot of pressure at the moment, so I very much appreciate all your efforts. Accidents happen.

I can confirm my address has not changed.
Please note I only have the mini dock, and I'm not sure Ethernet dock will fit.

Hi,

My Onion Omega seems to have no wifi.
When connected, there is no blinking LED , and no Omega-XXX network appears.
If it is really dark, I can see the LED glowing very very faintly.

I can see the Omega boots to a login prompt when I connect a USB cable.
When I login as root however, there is only eth0, eth1 and lo.
The suggested command to set up wifi is not available.
Running rc file for the wireless network results in a syntax error.
Running the AP setup scripts results in a reboot.
If I load the modules from the rc file by hand, a wifi0 interface appears, but
iwconfig says 'no wireless extensions' for all interfaces.

Do you have any hints? To me this looks like a wrong firmware, like https://community.onion.io/topic/63/password

Or could the mini-dock be at fault?
The switch of the mini dock snapped at first use, but I managed to switch it with a needle, and as stated above, the Omega does boot all the way to the login prompt.
Can I maybe connect another powersource directly to the Omega? I have a breadboard with 3.3V and 5V power options, I just don't know which pins to use.

I have the same issue and I'm currently making a new topic for it (Lazar asked me to do this after I first posted to the ticketing system).

A friend and I managed to hack into the omega by interupting the boot sequence an replacing init with sh. Then we were able to see the crypted password, wich in turn googled to the string '5up'. This seems to be the OpenWRT standard root password.

So try to log in with: root & 5up