3 3
TonyMac32

Lichee Pi zero

Recommended Posts

7 hours ago, sfx2000 said:

 

Nice work - must have been a bit of effort to squeeze a liter of code into 250 ml bucket...

ttyS0 pins on the pi's let me access all the hardware I want with the double din ui, socat serial socket does the job secure as a wired network, accessing hardware wifi would have been the easy way out and bad, imagine someone hacks that and they turn on the nos :angry:

Share this post


Link to post
Share on other sites
11 hours ago, sfx2000 said:

 

Even without a Turbo, a GM LS V8 is an excellent option - one of the better motors GM has done...

350 would like to speak with you :)

Share this post


Link to post
Share on other sites
On 12/16/2018 at 10:52 PM, chwe said:

IMO without interfaces for 11$

is it now $ 11,89.-  free shipping to CH, just like you requested :D  you should have gone lower :P

Share this post


Link to post
Share on other sites
350 would like to speak with you
350 had plenty of problems, it's biggest strength was how cheap it was. The Mopar 318/340/360 was/is a far better engine series.
@Tido@chwe next time say $6. :-P

The thing I see with the V3s is the fact that it appears to be in the same price arena as the H3, and without full vdec/venc/camera support it doesn't have a single benefit over the H3 or a decent micro (esp32, etc)

Sent from my Pixel using Tapatalk

Share this post


Link to post
Share on other sites
7 hours ago, TonyMac32 said:

350 had plenty of problems, it's biggest strength was how cheap it was. The Mopar 318/340/360 was/is a far better engine series.
@Tido@chwe next time say $6. :-P

The thing I see with the V3s is the fact that it appears to be in the same price arena as the H3, and without full vdec/venc/camera support it doesn't have a single benefit over the H3 or a decent micro (esp32, etc)

Sent from my Pixel using Tapatalk
 

 

for a cheap device it has the benefit of lower power and built in ram

Share this post


Link to post
Share on other sites
10 hours ago, TonyMac32 said:

350 had plenty of problems, it's biggest strength was how cheap it was. The Mopar 318/340/360 was/is a far better engine series.

 

Old school SBC's - cheap horsepower - LS, breathes much better, and they're easy to find and build... 

 

Few years back, helped build a hella strong Chrysler RB 440 - over 700 BHP on the dyno on pump gas... modified class dirt track stock car..

Share this post


Link to post
Share on other sites
10 hours ago, TonyMac32 said:

The thing I see with the V3s is the fact that it appears to be in the same price arena as the H3, and without full vdec/venc/camera support it doesn't have a single benefit over the H3 or a decent micro (esp32, etc)

 

I'd agree - but it's hitting a different market than the H/R/A series chips...

 

V3s is not a POP package, so it's not clear if the 64MB is on the die, or just a multi-chip package... what would make it more interesting is more RAM (128MB?) and some flash...

 

Being QFP makes it really interesting for makers, and actually a smart move for Allwinner there.

Share this post


Link to post
Share on other sites
(edited)

Well.. lichee pi zero came in today in a nice container with microusb male to usb female, header pins separate and the lichee pi its self, don't have any idea about pinning a display to this one yet, any displays for this? I don't think this lichee pi is n00b friendly, maybe l337 h@x0r friendly

Edited by chwe
removed mailto link which leads to nowhere

Share this post


Link to post
Share on other sites

Share this post


Link to post
Share on other sites
1 hour ago, ftp-bin2fex said:

Id only get that if it was a 7" or 2.4" < but not for that price.

 

You can try use a used 4.3inch TomTom display for cheap on Ebay

Share this post


Link to post
Share on other sites

Here is the Lichee Pi Zero with 4.3inch 800x480, keyboard and Li-Po battery. (also using a ESP8266 ESP-01 for Serial console over wifi)

 

 

 

tiny-desktop_1.png

Share this post


Link to post
Share on other sites

I also did order a Lichee Pi Zero Dock - because I really liked in the days back to around 2011 the Linksys NSLU2 and the
SnakeOS devices NS-K330 / WLXKJ652

(  NAS based on str8132 family of SoC - STAR STR8100 - FA526id(wb) rev 1 (v4l) ) : 
https://web.archive.org/web/20160610082937/https://code.google.com/p/snake-os/

 

Linux WLX652 2.6.16-gazineu #56 Tue Nov 30 04:03:41 BRST 2010 armv4l GNU/Linux

Mem: 9728K used, 20716K free, 0K shrd, 304K buff, 2880K cached
CPU:   0% usr   0% sys   0% nic  99% idle   0% io   0% irq   0% sirq
Load average: 0.00 0.00 0.00 2/32 647

 

Spoiler

Mem: 9776K used, 20668K free, 0K shrd, 304K buff, 2880K cached
CPU:   0% usr   0% sys   0% nic  99% idle   0% io   0% irq   0% sirq
Load average: 0.00 0.00 0.00 3/32 647
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
  647   635 root     R      920   3%   1% top
  634   555 root     S     1876   6%   0% dropbear -p 22
  607   606 root     S N   2760   9%   0% ./transmission-daemon -g /var/transmission/.config/transmission-daemon -
  608   606 root     R N   2760   9%   0% ./transmission-daemon -g /var/transmission/.config/transmission-daemon -
  604     1 root     S N   2760   9%   0% ./transmission-daemon -g /var/transmission/.config/transmission-daemon -
  606   604 root     S N   2760   9%   0% ./transmission-daemon -g /var/transmission/.config/transmission-daemon -
  564     1 root     S     2460   8%   0% smbd -D
  566     1 root     S     2108   7%   0% nmbd -D
  555     1 root     S     1876   6%   0% dropbear -p 22
  551     1 root     S      932   3%   0% /usr/sbin/crond -c /etc/cron.d
    1     0 root     S      928   3%   0% init
  635   634 root     S      928   3%   0% -sh
  543     1 root     S      928   3%   0% init
  567     1 root     S      920   3%   0% httpd -c /etc/httpd.conf -h /usr/share/www -p 80 -r WLX652
  520     1 root     S      916   3%   0% /sbin/klogd
  390     1 root     S      916   3%   0% /sbin/syslogd -S -O /var/messages
  201     5 root     SW<      0   0%   0% [str8100_spi]
  198     1 root     SW       0   0%   0% [mtdblockd]
    4     1 root     SW<      0   0%   0% [khelper]
    2     1 root     SWN      0   0%   0% [ksoftirqd/0]
  240     5 root     SW<      0   0%   0% [usb-storage]
   15     5 root     SW<      0   0%   0% [khubd]
  291     1 root     SW       0   0%   0% [kjournald]
   43     5 root     SW       0   0%   0% [pdflush]
   45     1 root     SW       0   0%   0% [kswapd0]
  181     5 root     SW<      0   0%   0% [cqueue/0]
   46     5 root     SW<      0   0%   0% [aio/0]
  239     5 root     SW<      0   0%   0% [scsi_eh_0]
    3     1 root     SW<      0   0%   0% [events/0]
   44     5 root     SW       0   0%   0% [pdflush]
    5     1 root     SW<      0   0%   0% [kthread]
   12     5 root     SW<      0   0%   0% [kblockd/0]
 



The SnakeOS-devices only got 32Mb of RAM and the Lichee has the double of 64MB RAM ;)
A debian Lenny chroot was available for SnakeOS - using one of the 2 USB-Ports as sda1

Lichee_Pi_Zero_top.jpg

Lichee_Pi_Zero_bottom.jpg

Share this post


Link to post
Share on other sites
On 1/29/2019 at 7:12 PM, markbirss said:

Here the Lichee Pi Zero Dock that I got Ethernet port working that I will use

Yesterday my Lichee Pi Zero Dock did arrive and I wanted to start it today, BUT I dont see real lifesigns after flasing 

the mindb-image ( https://licheepizero.us/downloads/mindb_dd.tar.gz ) via win32diskimager or dd to the microsd-card.

 

No blinking LED on the maiboard or on the ethernetport.

 

The only little lifesigns are a warm cpu and on Windows and Linux I do get a CDC-Device shown.
For Windows I didnt go/find a (universal) Win10-driver and in Linux I couldnt find a way to apply a IP to the CDC-Ethernet-device


[ 2144.150943] cdc_ether 5-1:1.0 usb0: unregister 'cdc_ether' usb-1c1d000.usb-1, CDC Ethernet Device
[ 2161.978424] usb 5-1: new high-speed USB device number 3 using ehci-platform
[ 2162.139648] usb 5-1: New USB device found, idVendor=0525, idProduct=a4aa, bcdDevice= 4.10
[ 2162.139666] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2162.139676] usb 5-1: Product: CDC Composite Gadget
[ 2162.139686] usb 5-1: Manufacturer: Linux 4.10.2-licheepi-zero+ with musb-hdrc
[ 2162.152561] cdc_ether 5-1:1.0 usb0: register 'cdc_ether' at usb-1c1d000.usb-1, CDC Ethernet Device, ae:cc:7a:1a:24:ac
[ 2162.165007] cdc_acm 5-1:1.2: ttyACM0: USB ACM device


 

@markbirss how did you get the ethernet port working? Do you have a special image? I yes - could you share it

or tell me a place on the net for a better forum like https://bbs.sipeed.com/c/lichee-pi-zero

 

LicheePi_CDC_Win.jpg

LicheePi_Dock.jpg

Share this post


Link to post
Share on other sites

@guidol sure

 

the led on the dock board will come on when using the dock dtb file (change it from the zero to the dock file)

i had to compile another kernel 4.13 and replace the sdcard kernel with the new vmlinuz/initrd and kernel modules and add ifconfig ethx up

 

Remember that the Ethernet leds dont light up !!! but the Ethernet still works

 

Here are another Chinese forum and the notes

 

Quote

 

Quote

1. sudo apt-get install gcc-arm-linux-gnueabihf

2. Download and compile Uboot

git clone https://github.com/Lichee-Pi/u-boot.git -b v3s-spi-experimental 
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- LicheePi_Zero_800x480LCD_defconfig 
make ARCH=arm menuconfig 
mime make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4

3. Download and compile Kernel

git clone https://github.com/Lichee-Pi/linux.git -b zero-4.13.y 
cd linux 
make ARCH=arm licheepi_zero_defconfig 
make ARCH=arm menuconfig #add bluethooth, etc. 
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j16 
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j16 INSTALL_MOD_PATH=out modules 
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j16 INSTALL_MOD_PATH=out modules_install

 

Share this post


Link to post
Share on other sites
23 minutes ago, markbirss said:

@guidol sure

 

the led on the dock board will come on when using the dock dtb file (change it from the zero to the dock file)

i had to compile another kernel 4.13 and replace the sdcard kernel with the new vmlinuz/initrd and kernel modules and add ifconfig ethx up

Thanks for the information. I want to use him (if possible) headless.

So is there another defconfig file for the dock/ethernet version?

 

Which Linux did use use to compile - some build-system (like the armbian one) do need Ubuntu 18.04 64Bit

 

So I did try with usb0/cdc a litle bit and got
 

LicheePi CDC Ethenet IP:
ip link set usb0 up
ip addr add 192.168.6.120/24 dev usb0

root@npi-neo2-24(192.168.6.24):~# ping 192.168.6.120
PING 192.168.6.120 (192.168.6.120) 56(84) bytes of data.
64 bytes from 192.168.6.120: icmp_seq=1 ttl=64 time=0.150 ms

root@npi-neo2-24(192.168.6.24):~# ssh -l root 192.168.6.120
root@192.168.6.120's password:

but neither toortoor nor licheepi does work as root-password for the mindb (minimal debian) image :(
[EDIT] that is only the local IP on the side of my Neo2 at USB-CDC :(
because I did edit the /etc/shadow of the partition sdb2 from the card and after the login Iam back on my Neo2 as IP120

or is the the password of the /etc/shadow also coded to which IP I could login?

(if this is the login from the mindb-image - but I think yes because of the dmesg-message

[    2.637857] usb 5-1: Manufacturer: Linux 4.10.2-licheepi-zero+ with musb-hdrc
)

Share this post


Link to post
Share on other sites
23 minutes ago, markbirss said:

@guidol sure

 

the led on the dock board will come on when using the dock dtb file (change it from the zero to the dock file)

i had to compile another kernel 4.13 and replace the sdcard kernel with the new vmlinuz/initrd and kernel modules and add ifconfig ethx up

Thanks for the information. I want to use him (if possible) headless.

So is there another defconfig file for the dock/ethernet version?

 

Which Linux did use use to compile - some build-system (like the armbian one) do need Ubuntu 18.04 64Bit

 

So I did try with usb0/cdc a litle bit and got
 

LicheePi CDC Ethenet IP:
ip link set usb0 up
ip addr add 192.168.6.120/24 dev usb0

root@npi-neo2-24(192.168.6.24):~# ping 192.168.6.120
PING 192.168.6.120 (192.168.6.120) 56(84) bytes of data.
64 bytes from 192.168.6.120: icmp_seq=1 ttl=64 time=0.150 ms

root@npi-neo2-24(192.168.6.24):~# ssh -l root 192.168.6.120
root@192.168.6.120's password:

but neither toortoor nor licheepi does work as root-password for the mindb (minimal debian) image :(
[EDIT] that is only the local IP on the side of my Neo2 at USB-CDC :(
because I did edit the /etc/shadow of the partition sdb2 from the card and after the login Iam back on my Neo2 as IP120

or is the the password of the /etc/shadow also coded to which IP I could login?

(if this is the login from the mindb-image - but I think yes because of the dmesg-message

[    2.637857] usb 5-1: Manufacturer: Linux 4.10.2-licheepi-zero+ with musb-hdrc
)

Share this post


Link to post
Share on other sites
(edited)
On 4/27/2019 at 11:30 AM, markbirss said:

@guidol sure

the led on the dock board will come on when using the dock dtb file (change it from the zero to the dock file)

i had to compile another kernel 4.13 and replace the sdcard kernel with the new vmlinuz/initrd and kernel modules and add ifconfig ethx up

Hmmm - litte more progress....

 

I did found the boot.scr and the sun8i-v3s-licheepi-zero-dock.dtb for activating the LED

 

u-boot compile didnt worked because of

Spoiler

root@licheebuild:/home/guido/v3s# make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- LicheePi_Zero_800x480LCD_defconfig
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/zconf.lex.c
  SHIPPED scripts/kconfig/zconf.hash.c
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/conf
#
# configuration written to .config
#
root@licheebuild:/home/guido/v3s# make ARCH=arm menuconfig
  HOSTCC  scripts/kconfig/mconf.o
  HOSTCC  scripts/kconfig/lxdialog/checklist.o
  HOSTCC  scripts/kconfig/lxdialog/util.o
  HOSTCC  scripts/kconfig/lxdialog/inputbox.o
  HOSTCC  scripts/kconfig/lxdialog/textbox.o
  HOSTCC  scripts/kconfig/lxdialog/yesno.o
  HOSTCC  scripts/kconfig/lxdialog/menubox.o
  HOSTLD  scripts/kconfig/mconf
scripts/kconfig/mconf  Kconfig


*** End of the configuration.
*** Execute 'make' to start the build or try 'make help'.

root@licheebuild:/home/guido/v3s# mime make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4

Der Befehl 'mime' wurde nicht gefunden, meinten Sie:

  Befehl 'meme' aus dem Snap meme (1.0)
  Befehl 'mame' aus dem Snap mame (mame0208)
  Befehl 'hime' aus dem deb hime
  Befehl 'time' aus dem deb time
  Befehl 'mmime' aus dem deb mblaze
  Befehl 'mame' aus dem deb mame

Informationen zu neuen Versionen sind mit 'snap info <snapname>' zu finden.

root@licheebuild:/home/guido/v3s# make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4
scripts/kconfig/conf  --silentoldconfig Kconfig
  CHK     include/config.h
  UPD     include/config.h
  CFG     u-boot.cfg
  GEN     include/autoconf.mk.dep
  CFG     spl/u-boot.cfg
  GEN     include/autoconf.mk
  GEN     spl/include/autoconf.mk
  CHK     include/config/uboot.release
  CHK     include/generated/timestamp_autogenerated.h
./scripts/dtc-version.sh: Zeile 17: dtc: Befehl nicht gefunden
  UPD     include/generated/timestamp_autogenerated.h
./scripts/dtc-version.sh: Zeile 18: dtc: Befehl nicht gefunden
*** Your dtc is too old, please upgrade to dtc 1.4 or newer
Makefile:1359: recipe for target 'checkdtc' failed
make: *** [checkdtc] Error 1
make: *** Auf noch nicht beendete Prozesse wird gewartet …
  UPD     include/config/uboot.release
root@licheebuild:/home/guido/v3s#
 

 

compile of Kernel (new zImage?) did work. replaces only the zImage....are they all in there (VMLinux/Initrd and modules)?
Maybe I miss some step for the kernel in 

make ARCH=arm menuconfig #add bluethooth, etc. ?

 

Got a ifconfig eth0 up in

/etc/rc.local but no ethernet DHCP is coming up :(

 

The cdc-device isnt also there anymore while connected to USB:

[17600.443734] usb 5-1: USB disconnect, device number 16
[17651.140334] usb 5-1: new high-speed USB device number 17 using ehci-platform
[17651.488322] usb 5-1: device descriptor read/64, error -71
[17651.944349] usb 5-1: device descriptor read/64, error -71
[17652.392347] usb 5-1: new high-speed USB device number 18 using ehci-platform
[17652.740661] usb 5-1: device descriptor read/64, error -71
[17653.196443] usb 5-1: device descriptor read/64, error -71
[17653.304488] usb usb5-port1: attempt power cycle
[17653.956440] usb 5-1: new high-speed USB device number 19 using ehci-platform
[17654.304444] usb 5-1: device descriptor read/64, error -71
[17654.764455] usb 5-1: device descriptor read/64, error -71
[17655.208560] usb 5-1: new high-speed USB device number 20 using ehci-platform
[17655.556501] usb 5-1: device descriptor read/64, error -71
[17656.016510] usb 5-1: device descriptor read/64, error -71
[17656.124641] usb usb5-port1: unable to enumerate USB device
[17656.516569] usb 8-1: new full-speed USB device number 6 using ohci-platform
[17656.708535] usb 8-1: device descriptor read/64, error -62
[17657.008574] usb 8-1: device descriptor read/64, error -62
[17657.308651] usb 8-1: new full-speed USB device number 7 using ohci-platform
[17657.500582] usb 8-1: device descriptor read/64, error -62
[17657.800584] usb 8-1: device descriptor read/64, error -62
[17657.908689] usb usb8-port1: attempt power cycle
[17658.412591] usb 8-1: new full-speed USB device number 8 using ohci-platform
[17658.828604] usb 8-1: device not accepting address 8, error -62
[17659.016610] usb 8-1: new full-speed USB device number 9 using ohci-platform
[17659.432632] usb 8-1: device not accepting address 9, error -62
[17659.432709] usb usb8-port1: unable to enumerate USB device

 

Edited by Tido
added code box

Share this post


Link to post
Share on other sites

Hey Guys,

 

I spent time over the past two days updating https://licheepizero.us and if you visit the site and use the navigation at the top right I have added some simple how-tos for certain things as well as have included better links to the resources you need.  This includes the dock.dtb file your looking for, if you look through the wifi setup page, I believe it is linked at the bottom: https://licheepizero.us/setup-wifi-for-licheepi-zero

 

As some of the Chinese resources have been slowly going down, I am trying to replicate the how-tos into English and add pages so that they will not be lost.

 

If you guys come up with anything that would be good to keep on there that I am missing, please PM me here or send me info using the Feedback form on the page.

 

Also if you get stuck on something, I will try to keep checking back here and offer suggestions as I can.

 

@guidol if you get stuck and your familiar with IRC you can come on Freenode irc network and join #H3Droid and I will be happy to try and help you some with getting things working, as I know just how frustrating the thing can be.

 

Have a great weekend!

 

Cheers!

Share this post


Link to post
Share on other sites
14 minutes ago, TheLinuxBug said:

I spent time over the past two days updating https://licheepizero.us and if you visit the site and use the navigation at the top right I have added some simple how-tos for certain things as well as have included better links to the resources you need.  This includes the dock.dtb file your looking for, if you look through the wifi setup page, I believe it is linked at the bottom: https://licheepizero.us/setup-wifi-for-licheepi-zero

 

If you guys come up with anything that would be good to keep on there that I am missing, please PM me here or send me info using the Feedback form on the page.

 

Also if you get stuck on something, I will try to keep checking back here and offer suggestions as I can.

Have a great weekend!

 

Many thnaks for your information and maintaining the webpage - it seems the only stop for english speaking people which want to use the LicheePi.

I only searched for the doch dtb, because I did think about my "LicheePi Zero Dock" Board for using the Ethernetport.

But now it seems that this dock dtb is more for enableing WiFi on the older borad-version without all these connectors :(

 

Maybe you could give me a hint for an image that is useable with ethernet or you can find a info, which would also be finde on your page for other/newer users.

 

IRC isnt directly in my mind :) Thats over 25 years ago for me when I did try to use IRC - like the old BBS-Chats.

 

Share this post


Link to post
Share on other sites
6 minutes ago, markbirss said:

@guidol also do a /sbin/dhclient eth0

you can use the existing u-boot if you dont need a new one

@markbirss

there was an DHCP eth0 entry in /etc/network/interfaces - which I now reconfigured as static IP,

but the eth0 port wouldnt talk to me :(

Share this post


Link to post
Share on other sites

@guidol You will need to use Google translate but the document you want for ethernet is: https://www.kancloud.cn/lichee/lpi0/327886

 

It may take compiling your own kernel with the driver built in.  To be honest I think I got around this at the time I was testing by using an image produced by Zeepan for my use with Cameras which I believe had ethernet already enabled.  

 

Don't quote me as saying this should work, but you could test this image: https://licheepizero.us/lpi_zero_cam.zip You should be able to unzip and then DD that to an SDcard and boot it.  It should provide, I believe, ethernet, VGA and camera interfaces already in the kernel if I recall correctly. (I have a VGA adapter board and a few other items I still need to add to the site for reference when I have time).

 

P.S. If you don't have an irc client installed but wish to join the irc room briefly there are now web based clients you can use, you can follow this link: https://h3droid.com/chat-with-us to and it will tell you what to do.

 

Maybe this will help you?

 

Cheers!

Share this post


Link to post
Share on other sites
29 minutes ago, TheLinuxBug said:

@guidol You will need to use Google translate but the document you want for ethernet is: https://www.kancloud.cn/lichee/lpi0/327886

 

Don't quote me as saying this should work, but you could test this image:

https://licheepizero.us/lpi_zero_cam.zip

You should be able to DD that to an SDcard and boot it.  Maybe this will help you?

With some old instructions (see above in this trhread) I had some problems compiling u-boot. Maybe in some days (when I got time again) I could try the instructions-page you listed. 

 

The lpi_zero_cam.zip give me some problems :(

First I do get verify-errors after write with win32diskimager v1.00 - with 6 differnt microSD-cards :(

I also did try to dd it directly (dd if=./lpi_zero_cam.dd of=/dev/sdb) but neither a win32diskimager nor

a dd flash does seem to boot (no messages on the linux usb-port where connected nor a DHCP-Request)

 

It looks like I have to solder the U1 serial port these days (like RX & TX and the Ground from the 5V/3.3V) for getting some more informations what the LPi is doing....

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
3 3