Welcome, Guest |
You have to register before you can post on our site.
|
Online Users |
There are currently 92 online users. » 1 Member(s) | 91 Guest(s) PhillipWob
|
Latest Threads |
Top-notch Сasual Dating -...
Forum: General
Last Post: jadenmikey
04-20-2024, 11:03 AM
» Replies: 0
» Views: 123
|
unpredictable dating
Forum: General
Last Post: JessicaWes
02-26-2024, 04:42 PM
» Replies: 2
» Views: 38,180
|
singular dating
Forum: General
Last Post: JessicaWes
02-26-2024, 11:40 AM
» Replies: 1
» Views: 35,648
|
Normall Lift Table manufa...
Forum: Newbie and Startup
Last Post: TERenlTet
12-10-2023, 07:13 PM
» Replies: 1
» Views: 2,612
|
Снять шлюху Владивосток д...
Forum: General
Last Post: MariaEl
07-01-2022, 12:42 AM
» Replies: 2
» Views: 38,754
|
I want to meet serious ma...
Forum: General
Last Post: MariaEl
06-29-2022, 09:48 PM
» Replies: 1
» Views: 39,695
|
WhiteFanposts Fanshots Se...
Forum: General Discussion on Lindenis V5
Last Post: MariaEl
06-29-2022, 09:40 PM
» Replies: 2
» Views: 6,014
|
Rectangular Dining Room T...
Forum: Newbie and Startup
Last Post: MariaEl
06-29-2022, 07:06 AM
» Replies: 1
» Views: 3,969
|
NEW 2020! IMPORTANT! - W...
Forum: General
Last Post: MariaEl
06-26-2022, 06:30 AM
» Replies: 5
» Views: 76,554
|
Hampton Bay Ceiling Fans ...
Forum: General Discussion on Lindenis V5
Last Post: MariaEl
06-26-2022, 05:57 AM
» Replies: 2
» Views: 5,685
|
|
|
How to properly set up ov2718 camera module? |
Posted by: DWD - 10-22-2019, 07:08 AM - Forum: General Discussion on Lindenis V5
- Replies (14)
|
|
Hey everyone!
I tested Lindenis with imx317 module and it works good, but we're currently trying to make it work with "ov2718" and it doesn't work.
I compiled ov2718_mipi.c driver, it correctly loads into kernel and even able to read/write to camera's i2c address but when I run 'ldcam -c -d 0 -o out' it freezes with the following dmesg errors:
Code: [ 114.995285] [ov2718_mipi]PWR_ON!
[ 115.079343] [ov2718_mipi]sensor_detect read value is 0x27
[ 115.086025] [ov2718_mipi]sensor_detect read value is 0x70
[ 115.101275] [VIN_ERR]buffer count is invalid, set to 3
[ 115.120535] [ov2718_mipi]sensor_s_stream on = 1, 1920*1080 3008
[ 116.178767] [ov2718_mipi]s_fmt set width = 1920, height = 1080
[ 116.279632] [VIN_ERR]isp0 frame error
[ 118.140426] [ov2718_mipi]sensor_s_stream on = 0, 1920*1080 3008
[ 118.147839] [ov2718_mipi]PWR_OFF!
Here's the [sensor0] section from sys_config.fex file that I corrected to suit my camera:
Code: [vind0/sensor0]
sensor0_used = 1
sensor0_mname = "ov2718_mipi"
sensor0_twi_cci_spi = 0
sensor0_twi_cci_id = 2
sensor0_twi_addr = 0x6c
sensor0_mclk_id = 2
sensor0_pos = "front"
sensor0_isp_used = 1
sensor0_fmt = 1
sensor0_vflip = 0
sensor0_hflip = 0
sensor0_iovdd = "iovdd-csi"
sensor0_iovdd_vol = 1800000
sensor0_avdd = ""
sensor0_avdd_vol = 1800000
sensor0_dvdd = "dvdd-csi-1"
sensor0_dvdd_vol = 1200000
sensor0_power_en =
sensor0_reset = port:PI3<1><0><1><0>
sensor0_pwdn = port:PI10<1><0><1><0>
sensor0_sm_hs = port:PI5<1><0><1><0>
sensor0_sm_vs = port:PI6<1><0><1><0>
Can someone help me with getting this camera to work?
According to Allwinner V5 manual it is supported.
|
|
|
How to build Lindenis sdk with buildroot? |
Posted by: Vikey - 10-06-2019, 08:52 AM - Forum: General Discussion on Lindenis V5
- Replies (1)
|
|
I ried to build sdk with choosing builadroot as OS,but I get a fail of not finding buildroot.config.
So does Lindenis sdk support buildroot yet?
$ source build/envsetup.sh
All available platforms:
0. eagle(Allwinner-V5,sun8iw12p1,arm)
1. petrel(Allwinner-H3,sun8iw7p1,arm)
2. cuckoo(Allwinner-V3,sun8iw8p1,arm)
Choice: 0
All available OS:
0. buildroot
1. debian
Choice: 0
0. allwinner-dvb
1. lindeni-v5
Choice: 1
|
|
|
build image using lindenis SDK (2 part) |
Posted by: ssdmt - 09-04-2019, 10:47 AM - Forum: General Discussion on Lindenis V5
- Replies (2)
|
|
Hi all.
i build the image form lindeni sdk.
finally i got the next log:
....
[ 2.685552] [mnt] /dev/root, nrt=ext3
[ 2.694400] EXT4-fs (mmcblk0p1): couldn't mount as ext3 due to feature incompatibilities
[ 2.703723] [mnt] /dev/root, nrt=ext4
[ 2.708611] EXT4-fs (mmcblk0p1): INFO: recovery required on readonly filesystem
[ 2.716978] EXT4-fs (mmcblk0p1): write access will be enabled during recovery
[ 2.782652] EXT4-fs (mmcblk0p1): recovery complete
[ 2.790008] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
[ 2.799085] VFS: Mounted root (ext4 filesystem) readonly on device 179:1.
[ 2.808300] Freeing unused kernel memory: 1024K (c0b00000 - c0c00000)
[ 3.041116] systemd[1]: System time before build time, advancing clock.
[ 3.058721] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #162555: comm systemd: checksum invalid
[ 3.071136] random: systemd: uninitialized urandom read (16 bytes read, 6 bits of entropy available)
[ 3.084447] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[ 3.104974] systemd[1]: Detected architecture arm.
...
Welcome to [1mDebian GNU/Linux 9 (stretch)[0m!
[ 3.126912] systemd[1]: Set hostname to <linbian>.
[ 3.141933] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #162555: comm systemd: checksum invalid
[ 3.156004] systemd[1]: Failed to open generator directory /usr/local/lib/systemd/system-generators: Bad message
[ 3.168755] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #162555: comm systemd: checksum invalid
[ 3.180923] systemd[962]: Failed to open directory /usr/local/lib/systemd/system-generators: Bad message
[ 3.192250] systemd[1]: system-generators failed with error code 1.
[ 3.199545] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #162555: comm systemd: checksum invalid
[ 3.211988] random: systemd: uninitialized urandom read (16 bytes read, 7 bits of entropy available)
[ 3.222356] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #162555: comm systemd: checksum invalid
[ 3.234228] systemd[1]: Failed to open directory /usr/local/lib/systemd/system, ignoring: Bad message
[ 3.246073] random: systemd: uninitialized urandom read (16 bytes read, 7 bits of entropy available)
[ 3.256307] [DISP] disp_device_attached_and_enable,line:190:
[ 3.262440] attached ok, mgr0<-->device0, type=4, mode=10
[ 3.266547] random: systemd: uninitialized urandom read (16 bytes read, 7 bits of entropy available)
[ 3.266874] random: systemd: uninitialized urandom read (16 bytes read, 7 bits of entropy available)
[ 3.267475] random: systemd: uninitialized urandom read (16 bytes read, 7 bits of entropy available)
[ 3.273867] random: systemd: uninitialized urandom read (16 bytes read, 7 bits of entropy available)
[ 3.278225] random: systemd: uninitialized urandom read (16 bytes read, 7 bits of entropy available)
[ 3.281254] random: systemd: uninitialized urandom read (16 bytes read, 7 bits of entropy available)
[ 3.284093] random: systemd: uninitialized urandom read (16 bytes read, 7 bits of entropy available)
[ 3.315901] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd: checksum invalid
[ 3.324954] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd: checksum invalid
[ 3.388523] systemd[1]: Reached target Swap.
[OK] Reached target Swap.
[ 3.406748] systemd[1]: Listening on udev Kernel Socket.
[OK] Listening on udev Kernel Socket.
[ 3.436774] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[OK] Started Dispatch Password Requests to Console Directory Watch.
...
...
Starting Login Service...
[ 31.279695] EXT4-fs error: 152 callbacks suppressed
[ 31.288259] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd-journal: checksum invalid
Starting System Logging Service...
[ 31.304481] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd-journal: checksum invalid
[ 31.318935] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #161533: comm (rsyslogd): checksum invalid
[ 31.331131] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #162555: comm systemd-logind: checksum invalid
[ 31.343894] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd-journal: checksum invalid
[ 31.358549] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd-journal: checksum invalid
Starting RealtimeKit Scheduling Policy Service...
[ 31.374227] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd-journal: checksum invalid
[ 31.406261] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd: checksum invalid
[ 31.418264] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd-journal: checksum invalid
[ 31.430769] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd: checksum invalid
[OK] Started Daily apt download activities.
[OK] Started Daily apt upgrade and clean activities.
[OK] Reached target Timers.
[OK] Started Regular background program processing daemon.
Starting Save/Restore Sound Card State...
[FAILED] Failed to start System Logging Service.
See 'systemctl status rsyslog.service' for details.
[OK] Started Save/Restore Sound Card State.
[OK] Started Raise network interfaces.
...
...
[ 56.371189] EXT4-fs error: 82 callbacks suppressed
[ 56.376816] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd-journal: checksum invalid
[FAILED] Failed to start Login Service.
[ 56.395154] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd-journal: checksum invalid
See 'systemctl status systemd-logind.service' for details.
[ 56.409634] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd-journal: checksum invalid
[ 56.424318] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd-journal: checksum invalid
[ 56.438492] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd-journal: checksum invalid
[ 56.452219] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd-journal: checksum invalid
[ 56.465820] EXT4-fs error (device mmcblk0p1): ext4_iget:4267: inode #131904: comm systemd-journal: checksum invalid
...
THEN! i flash lindenis image, and everything was fine!!
then i flased my image again, and EXT4-fs error appeared again!
can someone help me?
|
|
|
Questions about boot modes on Lindenis V5 |
Posted by: DWD - 08-28-2019, 12:53 PM - Forum: General Discussion on Lindenis V5
- Replies (3)
|
|
Hello,
I currently have two Lindenis V5 boards and I want to understand the boot process a little bit more.
From Allwinner documentation, I understand that there’s so called FEL pin which either boots motherboard normally (depending on BOOTSEL flags) or enters UPGRADE mode (USB or UART).
So can you please help me with the following questions:
- Where this FEL pin is located? I can’t find it in schematics.
- How to enter UART upgrade process instead of USB? I want to try it out.
|
|
|
|