You can get some serial console functionality via Ethernet using a netconsole.
CLUNC is a netconsole which is adapted for use on LaCie NAS products.
You can get it here.
You don't even need to open your EDmini v2 to use CLUNC
.</EDIT>
The EDmini v2 uses J2 for JTAG and serial console.
LaCie have thoughtfully pre-equipped J2 on my board with header pins
I believe that the Ethernet Big Disk uses the same board (but with the second set of SATA connectors equipped).
The J2 pinout is:
1 VCC (+5V)
2 GND
3 JTAG TMS : input to board
4 JTAG TCK : input to board
5 JTAG TDO : output from board
6 JTAG TDI : input to board
7 Serial RxD : input to board
8 Serial TxD : output from board
Pin 1 is furthest from the power connector.
UPDATE: kosmaty has kindly indicated pins 1 and 8 here: http://img524.imageshack.us/my.php?image=800pxlacieebdboardcompogk5.jpg
Note that:
I believe this information to be correct but please do not blame me if you blow up your board
In particular I guessed the JTAG from the connections to the xc9536 but I have not yet tested it
EDIT: Albert Aribaud (aaribaud) has told me that this JTAG chain seems to only include the Xilinx
So it would seem that the FLASH cannot be reprogrammed via these JTAG connections
EDIT 15/12/2010: Concerning JTAG FLASH access, Albert has subsequently told me via the lacie-nas mailing list:
aaribaud wrote:You must use the connector J11 I think -- that's the only other 8x1 connector on the board. Pinout is:
pin 1: 3.3V
pin 2: Gnd
pin 3: TMS
pin 4: CLK
pin 5: TDO
pin 6: TDI
pin 7: SRST
pin 8: RESET
To make things clear: J2 has the console and the Xilinx JTAG, and J11 has the Marvell SoC JTAG.
I have not investigated the J2 Xilinx JTAG, and know of no way to access the Flash through it.
I have investigated the J11 SoC JTAG, and while it does not provide direct access to the Flash, it provides access to the SoC debug port, which allows accessing the Flash using OpenOCD in two ways:
1. Direct OpenOCD reads and writes to the Flash address area (caveat: right after reset, the Flash CS settings put it at 0xF8000000, not at 0xFFF80000. You must read or reprogram the BOOT CS registers if you want to be sure where the Flash is located). You can even program the flash that way, following the write sequences in the Macronix datasheet, but it takes ages.
2. Indirect flash programming: build a RAM-based U-boot for edminiv2 (for RAM-based, you need to skip critical inits, by #define'ing CONFIG_SKIP_LOWLEVEL_INIT in include/configs/edminiv2.h) and use OpenOCD to load and execute U-Boot. From U-boot prompt, you will be able to read and reprogram the Flash at will.
Serial I/O is at 3.3V logic levels and not RS232C levels.
I am not certain that the inputs are 5V tolerant.
(I suspect that they should be as otherwise it would be stupid to put 5V on pin 1 of the connector.)
My usage of TxD and RxD is that the edmini sends on TxD and receives on RxD but this may not be standard as I have not taken into account DCE/DTE
For the serial console I used a modified DKU-5 mobile phone USB cable which works perfectly (115200, 8, N, 1 with XON/XOFF if you like but you must disable the hardware handshake (RTS/CTS IIRC or maybe DSR/DTR)).
LaCie have also thoughtfully put the security lock hole in exactly the right position to bring out the cable
EDIT: Albert Aribaud has told me that opening minicom freezes his PC when using a DKU-5 and 2.6.24.4 and 2.6.25.1 Linux kernels.
I have read a discussion about the Prolific PL2303 USB to serial chip used in the DKU-5 cables not being USB compliant.
Maybe they have removed some workaround for the quirks of the Prolific chip from the kernel.
So it looks like a combination of the Prolific chip and recent kernels should be avoided.
See Albert's website: http://tweaky.aribaud.net for details on this and other interesting articles on the EDmini V2.
EDIT 15/12/2010: The Prolific chip works for me with Ubuntu 10.10 which uses a 2.6.35 kernel IIRC.
I used a three wire connection (GND, TxD and RxD) for my DKU-5.
Here is the pinout of the Nokia connector:-
http://pinouts.ru/CellularPhones-Nokia/ ... nout.shtml
I cut off the connector at the Nokia side leaving just enough wire to determine with a ohmmeter which colours were connected to which pins.
The colours seem to vary but you may have the same colours as me if you have this model:-
http://eshop.no-ip.biz/eshop/#DATA_CABLE
(He sells on eBay too which is in fact where I bought mine.)
Taken from my (unreliable) notes the surprising colours on my cable were:-
- Yellow: GND to J2 pin 2
Blue: TxD (output from the cable) to RxD J2 pin 7
Green: RxD (input to the cable) to TxD J2 pin 8
However for me it is inconceivable to connect red to GND
So I think I just taped back the red wire.
However PLEASE check your colours.
Don't connect the EDmini at first; it is better to blow up a $4 cable than your EDmini
You should be able to identify GND with an ohmmeter to GND on the USB side.
Then with the cable connected to the USB of your PC:-
When it is static TxD (the output from the cable) will be at about +3.2 V with respect to GND.
Then with minicom (Linux) or HyperTerminal (Windows):-
You can check RxD by connecting it back to TxD on the cable and testing whether the characters you type are echoed.
When you are sure that you have GND, TxD and RxD right you can then try them out on the EDmini.
Enjoy
Other notes:
I should be interested in hearing from anybody hacking this board or the Ethernet Big Disk or the 2Big Network.
I bought mine with a dead disk and I should be interested if someone could give me a backup of the system partitions.
EDIT: I have them now thanks to aaribaud.
I have managed to install and boot the software for another NAS with fairly similar hardware (Maxtor Shared Storage II).
Serial access to uBoot is required to boot it and some functions do not work because the hardware has minor differences.
The kernel for the LaCie 2Big Network seems to support the EDmini v2 as well.
Some other Feroceon boards are supported as standard in the 2.6.25 kernels.
Is anybody working on adding EDmini v2 support to the latest kernels?
EDIT: I am now
- I have created a machine type and I have posted information in another topic:-http://forums.nas-central.org/viewtopic ... &t=76#p351
Cheers,
Chris
...
