Posts Tagged yoggie
While trying to solve some booting problems, here are ideas for SOHO projects:
- Use the two Ethernet NICs as bridge and run Wireshark on them for the passing traffic. Save the capture data on an SD card.
- Use a Tor client and a minimal desktop environment (browser, what else?). Save the work files on SD card.
- Make that damn SD card slot work 🙂
I ordered this adapter from DIY-Beamer. It should help me connect to the SOHO 20-pin consle port. Also hoping that Yoggie publishes the pinout as they promised.
The problem with SD card on Yoggie SOHO seems to be fixed already in a newer kernel.
[PATCH] pxamci: fix byte aligned DMA transfers
> The pxa27x DMA controller defaults to 64-bit alignment. This caused > the SCR reads to fail (and, depending on card type, error out) when > card->raw_scr was not aligned on a 8-byte boundary. aww crap, now that was the problem! I already suspected something as such (possible alignment issue), even dug down to closer inspection of raw_scr address, however didn't actually manage to find it at that time (I was more inching towards timing or transfer length issues). Thanks a _lot_, that fixed phone boot for me on my affected SD card! Andreas Mohr
I managed to open the enclosure – it’s not too difficult, and it looks undamaged, so I could glue it together again if needed.
Inside there’s basically one interface which is suspected to have UART pins, and probably JTAG pins as well. Yoggie representative on their forum promised to publish the details soon.
The socket is marked as J8, and it’s a 1cm wide, 20-way flat flex cable fixation. It looks like the cable from Farnell.com with the product number AXO-00008 should fit it. Now I need to figure out how to access to the pins of that cable, as it should look rather miniature.
After installing and uninstalling the Yoggie siftware, the network drivers are already on my Vista. Now I’m trying to get closer to the SOHO Open firewall. When connected with USB, it also responds to SSH at firstname.lastname@example.org, with the same password “yoggie”.
I managed to remove the front cover (the one with blue LEDs), and the PCB is visible inside. To the moment I haven’t managed to take the PCB out. I’m really curious if I can get to the console UART.
In /lib/modules, one can find the MMC drivers, so there is a chance to get the SD card slot working.
In /etc/modules, there are actually two lines for uncommenting to enable the SD card:
# MMC support -- comment out the next two lines to enable CF #mmc_block #pxamci
After uncommenting the above and running /etc/init.d/rc.modules, the following messages were added to dmesg:
yoggie_mci_setpower: on yoggie_mci_setpower: on mmcblk0: mmc0:b368 SD 1981440KiB mmcblk0:<3>mmcblk0: error 2 transferring data end_request: I/O error, dev mmcblk0, sector 0 Buffer I/O error on device mmcblk0, logical block 0 mmcblk0: error 1 sending read/write command end_request: I/O error, dev mmcblk0, sector 0 Buffer I/O error on device mmcblk0, logical block 0 unable to read partition table
It has seen the size of my SD card (YUPPIE!!), but somehow failed to read the data. Not enough power? let’s try the power supply which I wasn’t bored to used till now.
Rebooting with the external power supply…. and now my PC cannot acquire a DHCP address from Yoggie!
Removed the SD card, and now it’s reachable again…
Inserted the SD card, and dmesg shows the same I/O errors. This SD card is easily and reliably readable from other devices, so I consider that the kernel support for SD cards in the current SOHO firewall is broken.
The original dmesg follows:
Installed the default Yoggie software and plugged in he Pico stick. It took it about a minute to boot before Windows detected a new device. The driver installation went quite smoothly.
After that, the Yoggie tray icon was failing on my Vista. Also the network usage was blocked when I unplugged the Yoggie stick. I uninstalled the Yoggie software, but the network interface drivers remained on the system, so SSH connection into the Yoggie box continued to work.
The Yoggie software has created a new interface on my PC with the address 172.16.0.200/16. Guys, you took the whole RFC1918 172.16.* range just for a single point to point link – what a shame. Now I can’t use it inside any corporate LAN which uses these addresses.
OK, now to the interesting part. The device accepts SSH connections on email@example.com, password is “yoggie”. Inside you see a typical Busybox environment.
Ordered the two open source products from Yoggie, as described at LinuxDevices.com, and now they’ve arrived. Silly me, after too short reading I thought that the Pico modell has one Ethernet and one USB device port, but it actually has only USB device port.
Pity there’s no access to the console UART (probably there is, but I haven’t tried to open the enclosures 🙂 ).
The SOHO open firewall has got an undocumented SD slot! wow! (no idea yet if it’s functional though)
- 3G 2600hz adm5120 Allwinner A10 arm armadeus autoconf automake big-endian contracting debian docsis dvop.net e-reader emulators erlang freescale freeswitch freeswitch GUI friendlyelec gerty git gizmoforyou gnu autoconf gnu automake GSM hosting i.MX27 iNum iot ipsec ipv6 kamailio kazoo linux lte mips monitoring mooxu network automation networking network management network monitoring oAuth openwrt oyo packaging parallels plesk patch pbx pcengines perl routing sbc scaleway sensors server management sip Skype software design software development T2 testing tips tumblr ubuntu UMTS usb virtualization vmware voip voyage linux wifi xlab1 yoggie