VoCore: Change to IPX Socket

This is some NG(not good) boards from factory, in fact, they just lose antenna, no other issue, easy to fix.
I upgrade some into IPX socket. Very easy, and looks like wifi signal is better than the blue antenna. Of course the IPX antenna is much bigger :)
PS: I do not know the exactly name of such socket, just watch the picture.

(The PCB board is not washed after the fix)
IMG_0016

Big picture:
IMG_0017

How to make that? Very easy.
The GND connect to the golden pad in the orange rectangle; the feed pad connect to the green point, then it works.
IMG_0018

VoCore: Mass Production 7

Finally, everything is done :)
Docks are ready and will transfer to post office in two days.

I have some experience:
1. I heard many bad stories about the quality of “made in ShenZhen”(or made in China), I am a little “scared” before I do it , very carefully to choose the factory. I asked many friends and search,search,search…(I am a Chinese, but be honest, I do not have much confidence.)
But finally, I find most of the stories are not true.
When I talk with the materials provider, they just give me two lists, one is from original factory(always big factory), one with fake on it(from country side, electrical rubbish etc). To get good one, you have to cost twice or even more. They just tell everything and leave the choice to you.
Of course, I choose the good one. The benefit is obvious, VoCore good rate is over 99.9%, rest 0.1% issue is some antennas lost in SMT…So in another word, the good rate is almost 100%( from test. :) )
The higher the price, the better the quality of the merchandise.

2. Assemble/SMT. There is not much to say, due to 90% work are done by machines, the machines are all from Samsung(their main job is to do work for Samsung Phone/Pad etc), only test part there is a little human work -> put VoCore to the test fixture…They click “Start” on my test application, wait, until the app say “Yes” or “No”.
The factory engineers are very experienced, they help me a lot when I design the test application. I think this is bonus for made in China, most of the production made here, you do not have to cost time and money to design a new test process, but just improve current test process, and get a even better quality.

3. Some suggestions for hardware hobbyists all over the world. If you want to make your production in ShenZhen, better to have a Chinese in your team deal with the factory, some factories have salesman speak English, but engineers do not speak English, if they have problem in the production(this always happen), it will be hard to communicate.
99% of Chinese people are good, if you meet the 1% bad one, you will lose everything. To avoid such problem is easy, just compare, compare, compare…and most important thing, careful if the quote is too low(especially some small factories, their quote is always unbelievable low, 40%~60% as the good quality ones), they use second-hand chip or rubbish chip and you will never know, they can pass your test, even 20% production is NG, they still earn a lot, unless you stay there and monitor them in factory everyday.

Finally, I do not care VoCore is OSHW or not, I do not intent to make it as a “sell” point. I just remember when I was very young, the electrical products are all have schematic in the manual, and my father helped me study the radio…
do not know when that disappeared, just want the happy days back. ^_^

VoCore & Intel Edison & MT7688

Two days busy on the shipping and dealing with factory about the dock assemble test, here are some news:

First News:
Intel Edison comes.

I made a simple compare :)

VoCore Win
Size:
VoCore -> 25.6 x 25.6 x 3.4;
Edison -> 35.5 x 25.0 x 3.9;

Output:
VoCore -> 1.8V 200mA, 3.3V 300mA;
Edison -> 1.8V 100mA, 3.3V 100mA;

Input:
VoCore -> 3.3V ~ 6.0V
Edison -> 3.3V ~ 4.5V

Price:
VoCore -> 20USD
Edison -> 50USD

Edison Win
Edison: x86 x 2, 1GB memory
VoCore: MIPS, 32MB memory

Edison: BlueTooth
VoCore: N/A

Edison: 4GB eMMC
VoCore: 16MB SPI Flash

Fair
Input:
VoCore -> 5V, 200mA
Edison -> 3.3V, 300mA

FCCID:
VoCore -> passed, without shell
Edison -> passed, with shell

I am so happy my VoCore still have some points beat the Intel Edison :D

Second News:
MT7688 is coming, I heard some rumours, the final chip has two versions, one with 8MB memory(not enough :( ), one without memory, speed is same as MT7620, 580MHz, but power consume is 0.6watt(is this greater than AR9331’s 0.5watt?)

VoCore: Mass Production 6

I am crazy…
The factory just made a new big mistake(or accident), they deleted all the test log, just for a stupid reason, those test logs took too much disk space…and they ‘think’ the productions had done the test, that should be useless. Simply ignore my notify, ye, I notified them to keep the log at least three times, in face or phone call. T-T Now they are trying to recover the deleted data…
I planed to use that log to trace the production quality…If user gets the VoCore but has problem, at least I have some data to trace.
They agree if the log can not back, they will test again, but I can not wait. Just hope the log be recovered.

VoCore: Two UARTs

Enable two UARTs for VoCore, one UART lite, one UART full.
Just need to change DTS a little:(new dts)

/dts-v1/;

/include/ "rt5350.dtsi"

/ {
	compatible = "VoCore", "ralink,rt5350-soc";
	model = "VoCore";

	palmbus@10000000 {
		gpio1: gpio@660 {
			status = "okay";
		};

		i2c@900 {
			status = "okay";
		};

		spi@b00 {
			status = "okay";

			m25p80@0 {
				#address-cells = <1>;
				#size-cells = <1>;
				compatible = "w25q128";
				reg = <0>;
				linux,modalias = "m25p80", "w25q128";
				spi-max-frequency = <10000000>;

				partition@0 {
					label = "uboot";
					reg = <0x0 0x30000>;
					read-only;
				};

				partition@30000 {
					label = "uboot-env";
					reg = <0x30000 0x10000>;
					read-only;
				};

				factory: partition@40000 {
					label = "factory";
					reg = <0x40000 0x10000>;
					read-only;
				};

				partition@50000 {
					label = "firmware";
					reg = <0x50000 0xfb0000>;
				};
			};
			
			mmc-slot@1 {
				compatible = "mmc-spi-slot";
				reg = <1>;
				voltage-range = <3300 3300>;
				spi-max-frequency = <10000000>;
				broken-cd;
			};
		};
	
		uart@500 {	
			status = "okay";
		};
	};

	pinctrl {
		state_default: pinctrl0 {
			gpio {
				ralink,group = "jtag", "led";
				ralink,function = "gpio";
			};
		};
	};

	ethernet@10100000 {
		mtd-mac-address = <&factory 0x4>;
	};

	esw@10110000 {
		ralink,portmap = <0x17>;
	};

	wmac@10180000 {
		ralink,mtd-eeprom = <&factory 0>;
	};

	ehci@101c0000 {
		status = "okay";
	};

	ohci@101c1000 {
		status = "okay";
	};

	gpio-export {
		compatible = "gpio-export";
		#size-cells = <0>;

		gpio0 {
			gpio-export,name = "gpio0";
			gpio-export,direction_may_change = <1>;
			gpios = <&gpio0 0 0>;
		};

		/* JTAG */
		gpio17 {
			/* JTAG_TDO */
			gpio-export,name = "gpio17";
			gpio-export,direction_may_change = <1>;
			gpios = <&gpio0 17 0>;
		};
		gpio18 {
			/* JTAG_TDI */
			gpio-export,name = "gpio18";
			gpio-export,direction_may_change = <1>;
			gpios = <&gpio0 18 0>;
		};
		gpio19 {
			/* JTAG_TMS */
			gpio-export,name = "gpio19";
			gpio-export,direction_may_change = <1>;
			gpios = <&gpio0 19 0>;
		};
		gpio20 {
			/* JTAG_TCLK */
			gpio-export,name = "gpio20";
			gpio-export,direction_may_change = <1>;
			gpios = <&gpio0 20 0>;
		};
		gpio21 {
			/* JTAG_TRST_N */
			gpio-export,name = "gpio21";
			gpio-export,direction_may_change = <1>;
			gpios = <&gpio0 21 0>;
		};

		/* ETH LEDs */
		gpio22 {
			/* ETH0_LED */
			gpio-export,name = "gpio22";
			gpio-export,direction_may_change = <1>;
			gpios = <&gpio1 0 0>;
		};
		gpio23 {
			/* ETH1_LED */
			gpio-export,name = "gpio23";
			gpio-export,direction_may_change = <1>;
			gpios = <&gpio1 1 0>;
		};
		gpio24 {
			/* ETH2_LED */
			gpio-export,name = "gpio24";
			gpio-export,direction_may_change = <1>;
			gpios = <&gpio1 2 0>;
		};
		gpio25 {
			/* ETH3_LED */
			gpio-export,name = "gpio25";
			gpio-export,direction_may_change = <1>;
			gpios = <&gpio1 3 0>;
		};
		gpio26 {
			/* ETH4_LED */
			gpio-export,name = "gpio26";
			gpio-export,direction_may_change = <1>;
			gpios = <&gpio1 4 0>;
		};
	};

	gpio-leds {
		compatible = "gpio-leds";
		status {
			/* UARTF_RXD */
			label = "vocore:green:status";
			gpios = <&gpio0 10 0>;
		};
		eth {
			/* UARTF_DTR_N */
			label = "vocore:orange:eth";
			gpios = <&gpio0 11 0>;
		};
	};
};

First, enable uart@500

uart@500 {	
	status = "okay";
};

Then, remove uartf from ralink,group:gpio.

	pinctrl {
		state_default: pinctrl0 {
			gpio {
				ralink,group = "jtag", "led"; -> remove "uartf"
				ralink,function = "gpio";
			};
		};
	};

Finally, delete the code that export uartf as gpio:
in gpio-export section, remove gpio7, gpio8, gpio9, gpio10, gpio11, gpio12, gpio13, gpio14. If we keep them will get some error in log, but no effect to system boot.
PS: find a possible bug here, gpio10 and gpio11 are missed :)

Now good news is the two UARTs work same time, bad news is we lose eight gpio. ;)
Hope one day a hero will make a new rt5350-uart driver, so that allows ralink-function=”uartf,gpio”, then we can save 4 gpios. It is a good chance to practise Linux driver code. :D

New Site VoCore.io

The new site has opened recently :)
I try to make the site as simple as possible, hope you like it.
Special thanks to Kovács Kornél, a great work.
Some parts are still under construction, if you have good idea, please mail to vonger@live.com.
Especially the wiki part :D

view