December 12, 2019, 12:56:14 pm

News:

Have you visited the Allwinner Chipset wiki? - http://linux-sunxi.org/


Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - @lex

1
Cubieboard v2 Hardware (A20 Based) / Re: ts_calibrate
January 18, 2016, 05:43:44 pm
You have not applied the patch with success.
Check if input-raw.c has:
   if ((ioctl(ts->fd, EVIOCGBIT(EV_ABS, sizeof(absbit)), absbit)) < 0 ||
      !(absbit[BIT_WORD(ABS_X)] & BIT_MASK(ABS_X)) ||
      !(absbit[BIT_WORD(ABS_Y)] & BIT_MASK(ABS_Y))) {
      /*fprintf(stderr, "tslib: Selected device is not a touchscreen (must support ABS_X and ABS_Y events)\n");
      return -1;*/
   }

if not, edit the file and comment the lines.
2
Android is the only one capable of rotating the screen (with touch) as far as i know, it does this via Software. If you cannot use Android you can check with some advanced Qt user if the latest version support it. The way video (GPU) is handled/rendered in the ARM world is different from Desktop PC world.
3
Cubieboard v2 Hardware (A20 Based) / Re: Pinout for LCD.
December 03, 2015, 02:37:25 pm
It may help or may sound silly, but i would enable some debugging message in LCD_get_sys_config and make sure your modified script.bin is the one parsed.
4
Try your pin gpio_pin_23 alone and see if it works:

[gpio_para]
gpio_used = 1
gpio_num = 1
gpio_pin_1 = port:PE05<1><default><default><0>

Then again with:
gpio_pin_1 = port:PE05<1><default><default><1>

What kernel are you using?
5
OK!

Here is the update of the progress...
Wires must not be to long for the CSI as you can see it gets noise at high transfer, that is it.

The testing of the pix format is here: https://drive.google.com/open?id=0B7A7OPBC-aN7T0wzdm5yOTM0aDg
6
Thanks premoboss,

Searching arduino forums i realized SDA and SCL need 4.7k-10k pull-up resistors. I did that and did not worked until i found it needs an external clock, the XCLK pin.

The ov7670 module is detected now and i get some activities, but i can see only colored stripes, some times green stripes.

I think the circuitry i made are too long for csi or are unreliable.

For those who would like to wire the OV7670 here it is:
QuotePin <---------> Pin
Camera                  CB1 / CB2
1          +----------  3v3
2         (4.7k)           20 (GND)
3 ------+-----------  6
4 ------+-----------  7
5                            8
6                            9
7                            5
8                            10
9                            18
10                            17
11                            16
12                            15
13                            14
14                            13
15                            12
16                             11


Camera module: ov7670
1 - VCC      2 - GND
3 - SCL      4 - SDA
5 - VSYNC   6 - HREF
7 - PCLK   8 - XCLK
9 - D7      10 - D6
11 - D5      12 - D4
13 - D3      14 - D2
15 - D1      16 - D0

CB2 - CB1pins
1   VCC-5V                   2   PH15 (CSI1-PWR/EINT15)
3   CSI1-IO-2V8                4   PH14 (CSI1-RST#/EINT14)
5   PG0 (CSI1-PCLK/SDC1-CMD)   6   PB18 (TWI1-SCK)
7   PB19 (TWI1-SDA)             8   PG3 (CSI1-VSYNC/SDC1-D1)
9   PG2 (CSI1-HSYNC/SDC1-D0)   10   PG1 (CSI1-MCLK/SDC1-CLK)
11   PG4 (CSI1-D0/SDC1-D2)       12   PG5 (CSI1-D1/SDC1-D3)
13   PG6 (CSI1-D2/UART3-TX)       14   PG7 (CSI1-D3/UART3-RX)
15   PG8 (CSI1-D4/UART3-RTS)       16   PG9 (CSI1-D5/UART3-CTS)
17   PG10 (CSI1-D6/UART4-TX)       18   PG11 (CSI1-D7/UART4-RX)
19   Ground                   20   Ground
7
I can not get further than this.
I cannot detect the camera using i2C at address 0x42, something wrong wiring the pins directly.
SIO_C -> PB18
SIO_O -> PB19 or vice-versa

8
I am stuck on this.

I should mention:
- Wired using 2.8v
- Kernel is 3.4.103 (linux-sunxi)
- followed instructions on http://docs.cubieboard.org/tutorials/expansion_boards_dvk/dvk521/documentations/a10/driver_porting_and_configuration
- Fex according
- Same camera module of DVK521

Dmesg:
Quote[  638.353061] [CSI]Welcome to CSI driver
[  638.354684] [CSI]csi_init
[  638.372778] [CSI]registered sub device,input_num = 0
[  638.377274] axp20_ldo3: Failed to create debugfs directory
[  638.386480] [CSI]V4L2 device registered as video1
[  638.406825] [ccu-err] clk_enable: invalid handle
[  639.389951] HDMI not connected
[  639.392672] Error -5 on register write
[  639.400505] [CSI_ERR]chip found is not an ov7670 chip.
[  639.405521] [CSI_ERR]sensor initial error when csi open!
ubuntu@apps:~$


Should i wire 3.3v to VCC?

Anyone with DVK521 is using this camera module with success?
9
Anyone have this working? Only Cubietech?

I would like to have something like this: http://www.arducam.com/arducam-shiled-rev-c-released/#more-565

Reading OV7670 datasheet i get this VCC:
QuoteVDD-A DC supply voltage - Analog - 2.45 2.75 3.0 V
VDD-C DC supply voltage - Digital Core - 1.62 1.8 1.98 V
VDD-IO DC supply voltage - I/O power - 1.7 - 3.0V V


Seems that VCC is pin 3 (SI1-IO-2V8) on Cubieboard, and Cubietech uses pin 4   PH14 (CSI1-RST#/EINT14) but i don't see fit. And arducam also says it is 4 pins SPI that i suppose would be  PCLK,HREF,SIO_C,SIO_O and XCLK,VSYNC (I2C)?

My understanding is very limited but the arducam modules says it uses SPI and I2C, so where this pin 4 (PH14) would be used for?

Ops! my mistake.
I was looking at the wrong FEX, got the correct fex, it uses PH13 now.
10
Here is the driver for kernel 3.4.108 !
https://drive.google.com/file/d/0B7A7OPBC-aN7WEwtempBU0JmNlU/view?usp=sharing

Decompress it to: /lib/modules/3.4.108/kernel/drivers/media/dvb/dvb-usb/
and load the module, attach the device and check dmesg.

Update:
I think this will work for danand kernel 3.4.108-sun7i+ [ 3.4.108-c ]
https://drive.google.com/file/d/0B7A7OPBC-aN7TUVTVGNPLXlQeVU/view?usp=sharing

Decompress it to: /lib/modules/3.4.108-sun7i+/kernel/drivers/media/dvb/dvb-usb/
and load the module, attach the device and check dmesg.


PS:
If you get errors while loading the module, you may need to run : depmod -a
11
Somehow i got a binary driver for the RTL2832U (2838) and built-in support for several tuners, my primary interest is on R820T for the device i have. This driver loads on kernel 3.4.103 and should work for DVB-T and ISDB-T and could be of interest for someone who could not find or build one.

I am still having problems with dvbv5-scan (version 1.01) and i am investigating.
If you have time and want to check if it works for your device, try it on DVB or ISDB (depends on where you are) and let me know.

The device:

Bus 002 Device 007: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T



Bus 002 Device 007: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0bda Realtek Semiconductor Corp.
  idProduct          0x2838 RTL2838 DVB-T
  bcdDevice            1.00
  iManufacturer           1 Realtek
  iProduct                2 RTL2838UHIDIR
  iSerial                 3 00000001
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           34
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          4 USB2.0-Bulk&Iso
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              5 Bulk-In, Interface
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              5 Bulk-In, Interface
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  bNumConfigurations      2
Device Status:     0x0000
  (Bus Powered)


Here is the kernel log showing it was detected:
[   16.012938] usbcore: registered new interface driver dvb_usb_rtl28xxu
[   17.904270] usbcore: registered new interface driver dvb_usb_rtl2832u
[  196.940438] dvb-usb: found a 'RTL2832U DVB-T USB DEVICE' in warm state.
[  196.948248] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  196.955714] DVB: registering new adapter (RTL2832U DVB-T USB DEVICE)
[  197.930847] DVB: registering adapter 0 frontend 0 (Realtek DVB-T RTL2832)...
[  197.941424] input: IR-receiver inside an USB DVB receiver as /devices/platform/sw-ehci.1/usb2/2-1/2-1.1/input/input6
[  197.947317] dvb-usb: schedule remote query interval to 287 msecs.
[  197.961007] dvb-usb: RTL2832U DVB-T USB DEVICE successfully initialized and connected.

Steps to get it loaded

a) You should load the following modules, manually or editing /etc/modules and adding
dvb-usb-rtl28xxu
dvb-usb-rtl2832u

b) Kernel must be 3.4.103 and dvb-core and dvb-usb must be enabled

c) Your Modules loaded in memory would look like this
Module                  Size  Used by
disp_ump                 861  0
ppdev                   7982  0
lp                      8121  0
parport                34531  2 lp,ppdev
dvb_usb_rtl2832u      395360  0
dvb_usb_rtl28xxu       10637  0
rtl2830                 6751  1 dvb_usb_rtl28xxu
dvb_usb                17560  2 dvb_usb_rtl2832u,dvb_usb_rtl28xxu
dvb_core               92100  1 dvb_usb
rc_core                21139  2 dvb_usb_rtl28xxu,dvb_usb
sunxi_ir                3684  0
leds_sunxi              3721  0
gpio_sunxi              8910  0
sunxi_ts               20294  0
rfcomm                 58145  0
bnep                   14129  2
bluetooth             264397  10 bnep,rfcomm
sunxi_cedar_mod         9962  0
mali_drm                2608  1
drm                   208790  2 mali_drm
mali                  111115  0
ump                    51991  4 mali,disp_ump
lcd                     3778  0


d) Install the dvb-tools

The binary driver is here: https://drive.google.com/file/d/0B7A7OPBC-aN7ZWsycTZzZ0w4Nnc/view?usp=sharing

Download and decompress it to /lib/modules/3.4.103/kernel/drivers/media/dvb/dvb-usb
Boot, attach your device and see if it gets recognized.

I hope this can be useful.
12
Ok, i have had excessive care.Took it for granted, booted, rebooted and it worked as advertised.
Don't forget to use 3.3v and not 5v as input.
13
Thanks Premoboss,

I will try it, but i just wanted to stick on and start using it.
It now looks like frankenstein. :)

If someone uses a Buzzer, please, leave a message.
14
If you think is a bug, please, try to make a patch or hack the relevant code and release it to kernel builders.
What kernel version are you using?

Not many people use LVDS but if the A40 comes true....
15
Beginners / Re: Max possible voltage on input of pins
September 14, 2015, 08:30:58 am
The maximum voltage for input is 3.3v!
I am not a hardware guy, but 5v will damage the pin or the board.
Take a look at this: https://www.sparkfun.com/products/12009
I hope you find a way to keep going with your project.