• Content Count

  • Joined

  • Last visited

About PaddleStroke

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Bananapi boards are using AP6212 wifi+bt module. Maybe it's easier to use this module as it seem it already works on armbian. In your experience, is this module working correctly? Thanks!
  2. hey guys, Using legacy kernel I have trouble having dual output on LCD and HDMI. I tried to have a cloned dual output (same framebuffer for both) : [disp_init] disp_init_enable = 1 disp_mode = 4 screen0_output_type = 1 screen0_output_mode = 6 screen1_output_type = 3 screen1_output_mode = 4 fb0_width = 0 fb0_height = 0 fb0_framebuffer_num = 2 fb0_format = 10 fb0_pixel_sequence = 0 fb0_scaler_mode_enable = 0 fb1_width = 1024 fb1_height = 600 fb1_framebuffer_num = 2 fb1_format = 10 fb1_pixel_sequence = 0 fb1_scaler_mode_enable = 0 ... Also tried with 2 framebuffers : [disp_init] disp_init_enable = 1 disp_mode = 2 screen0_output_type = 1 screen0_output_mode = 6 screen1_output_type = 3 screen1_output_mode = 4 fb0_width = 0 fb0_height = 0 fb0_framebuffer_num = 2 fb0_format = 10 fb0_pixel_sequence = 0 fb0_scaler_mode_enable = 0 fb1_width = 0 fb1_height = 0 fb1_framebuffer_num = 2 fb1_format = 10 fb1_pixel_sequence = 0 fb1_scaler_mode_enable = 0 ... On both case when booting the signal is first on HDMI until kernel starts. Then the signal goes to LCD and HDMI turns off. Any hint? Full fex below :
  3. Hey guys, What is in your opinion the best solution to add WIFI/BT capability to a A20 board? Currently I tried to add ESP8266 connected with SDIO. (without much success so far). Then in order to add BT too I am thinking about ESP32 (with ESP-WROOM-32 module). Do you know if there are references of using this ESP32 solution to provide wifi and bt to a allwinner board/armbian ? Also this module have a lot of different interfaces available, which should be prefered? Or alternatively, do you know other armbian supported solution for wifi/bt? Best would be a solution that does not use USB ports as I need them. Thanks!
  4. Hey guys, Using a A20 board with AXP209, using mainline, I am trying to add a battery indicator as an overlay on video signal so that user can see remaining battery %. Something similar to smartphone battery indicator. Any idea how to do this? This shows how to get battery % but how to add an overlay? This sounds like something that probably have already been done. Do you know any existing reference ?
  5. Hi Tido, Thanks for your feedback. Finally the FJ035CI54-R40 could work on legacy. Without even timing values. So it seems timing values are not critical to get picture... The error was probably somewhere else, I still need to do some test to find out more precisely. Here's the fex that works with legacy and FJ035CI54-R40 for reference.
  6. Hey guys, Some questions about LCD interfacing. I have a A20 board and 2 LCD, one 640*480 3.5" (FJ035CI54-R40), one 320*240 3.5" (LQ035NC111, same as bananapi LCD). Both LCD have the same pinout, formfactor and ribbon so should be hardware compatible. 1 - LQ035NC111 I could get the LQ035NC111 to work on legacy kernel with the following script.fex (for reference) But can't get it to work with mainline. With mainline I get a white rectangle flashing on the left side of the screen. Interestingly I can reproduce the exact same bug with legacy by changing all the pin configurations from : lcdd0 = port:PD00<2><0><3><default> lcdd1... to lcdd0 = port:PD00<2><0><default><default> lcdd1... Looking at fex guide I see that the third parameter is "<drive capability> defines the output drive in mA, values are 0-3 corresponding to 10mA, 20mA, 30mA and 40mA." As the visual issue is exactly the same on mainline I guess the problem must come from this but I can't figure out how to change this drive capability in mainline. Any guess? 2 - FJ035CI54-R40 So for this LCD I can't get over a black screen (Backlight is working). The tricky part is that the datasheet (enclosed) is not clear for me. Also supplier gave me additional data which seem different than datasheet. #define HT 680 //Horizontal total period = (HT + 1) pixels #define HPS 2 //Horizontal Sync Pulse Start Position = (HPS + 1) pixels #define LPS 20 //Horizontal Display Period Start Position = LPS pixels #define HPW 20 //Horizontal Sync Pulse Width = (HPW + 1) pixels #define VT 550 //Vertical Total = (VT + 1) lines #define VPS 2 //Vertical Sync Pulse Start Position = VPS lines #define FPS 6 //Vertical Display Period Start Position = FPS lines #define VPW 12 //Vertical Sync Pulse Width = (VPW + 1) lines #define HSPW 2 #define HBPD 20 #define HFPD 20 #define VSPW 2 #define VBPD 6 #define VFPD 12 //DCLK=20MHZ On page 6 of datasheet the timing data looks different, but it may just be a misunderstanding from me. For instance datasheet say PCLK = 63.61MHz, but the file above say DCLK = 20MHZ (even if commented out). Do you know what is the difference between PCLK and DLCK? (The inconsistancy between LCD datasheets parameter names and symbols is killing me.) Also the datasheet say "The RGB only support the DE mode: HSYNC,VSYNC,DCLK and DE pin ." It seems from fex guide that mode can be set by "lcd_if" value. However there is no DE mode. Only : So I am unsure what to select. I can't find much documentation about those modes on internet. Also I can't understand what is this and how it should be set : "lcd_io_cfg0 = 268435456" I made several attemps with either datasheet or above code timing values but without luck so far. Only a black screen. Anyone has some experience with LCD interfacing on armbian could help me writing this fex? It would really really really be appreciated. Above is my last attempt of fex : FJ035CI54-R40.pdf
  7. Hi there, I am trying to download the lime2 legacy image : But the link is dead (error 404). Any chance to get this back up? Or can I use another legacy image and just change the script.bin or is there other things to modify? Thanks Edit : I just found the image on olimex website :
  8. Thanks for feedback! In chinese, do you mean that those commands are hardware coded in the allwinner chip? It's not something that is coded in armbian? I can handle chinese documentation if you have any. Or if you confirm allwinner could help I'll ask them, but I am not sure what to ask them right now as I thought it was a armbian feature.
  9. Thanks for feedback, anyway I found a way to hardware rotate LCD now. It was just for curiosity. What about the dispdbg commands? Do you know where I can find documentation about that? Or the source code of these commands? Any idea how to disable disp1 and enable disp0 ? I think perhaps it's not working because the switch command only changes the screen_output_type and mode but is not actually enabling/disabling screen0/screen1 I tried to enable both disp in my script.bin with : [disp_init] disp_init_enable = 1 disp_mode = 2 # dual head screen0_output_type = 0 # 0 should be NONE screen0_output_mode = 5 screen1_output_type = 2 screen1_output_mode = 14 But then I have not any signal on either screen. Maybe disp_mode= 4 (clone(screen0, screen1, fb0) (2 screens, one standard framebuffer) ) would work? Also I am not sure how to enable HDMI after disable TV (as I don't have screen anymore...). So I tried to make a bash file but not sure the syntax is correct. Can you tell me if something is wrong in the syntax? #!/bin/bash cd /sys/kernel/debug/dispdbg/ echo "switch" > command echo "disp1" > name echo "0 14" > param echo "1" > start sleep 2 cd /sys/kernel/debug/dispdbg/ echo "switch" > command echo "disp0" > name echo "4 5" > param echo "1" > start
  10. on another topic, I found this about LCD rotation : Can someone explain me what it means "supply" a kernel parameter and how to do it? Also I tried to echo on a booted device. sudo su cd /sys/class/graphics/fbcon echo "2" > rotate But nothing happenned, no error message. I am missing something? I am not sure to understand differences between sunxi-linux and armbian and how they interact...
  11. Ok after few tests : Currently my script.bin is as follow : [disp_init] disp_mode = 1 #(tv mode) screen0_output_type = 3 screen0_output_mode = 5 screen1_output_type = 2 screen1_output_mode = 14 hdmi_used = 0 tv_used = 1 Using "disp" --> does not work Using "disp1" --> works echo "switch" > command echo "disp1" > name echo "0" > param echo "1" > start --> turn off my TV signal. However enabling HDMI instead does not work. I tried : echo "switch" > command echo "disp1" > name echo "4 5" > param echo "1" > start and with "3 5" both don't work. It just turns OFF the TV signal but HDMI is not turning ON. I guess it's because HDMI should be set on disp0 and not disp1? Is there any documentation about this dispdbg commands? Can't find any on google. Then as I have no longer video signal I don't know how to know what happens afterwards and have to reboot the unit.
  12. Thanks!! It's indeed working with devmem2. There should have been something wrong in my mmap before. When I run devmem2 the value change when HDMI is connected or not. No HDMI : 266f0 0000 0000 0000 0010 0110 0110 1111 0000 HDMI : a66F0 0000 0000 0000 1010 0110 0110 1111 0000 The method you gave here, is working for legacy 3.4.113 correct? So I should do : Switch from TV (TNSC) to HDMI sudo su cd /sys/kernel/debug/dispdbg/ echo "switch" > command echo "disp" > name echo "4 5" > param echo "1" > start Why is it "4 5" ? Is it not as follow : "screen0_output_type screen0_output_mode" In script.bin HDMI output type is "3", "4" being VGA. (source here) Switch from HDMI to TV (TNSC) sudo su cd /sys/kernel/debug/dispdbg/ echo "switch" > command echo "disp" > name echo "2 14" > param echo "1" > start Or should I first disable the previous video output with : sudo su cd /sys/kernel/debug/dispdbg/ echo "switch" > command echo "disp" > name echo "0" > param echo "1" > start Or should I used disp0 and disp1 as you suggest? Then it would be as follow : Switch from TV (TNSC) to HDMI sudo su cd /sys/kernel/debug/dispdbg/ echo "switch" > command echo "disp1" > name echo "0 14" > param echo "1" > start echo "switch" > command echo "disp0" > name echo "4 5" > param echo "1" > start Switch from HDMI to TV (TNSC) sudo su cd /sys/kernel/debug/dispdbg/ echo "switch" > command echo "disp0" > name echo "0 5" > param echo "1" > start echo "switch" > command echo "disp1" > name echo "2 14" > param echo "1" > start PS : for those that might be interested, here is how to install devmem2 If you have internet access just do the following : wget gcc ./devmem2.c sudo mv ./a.out /usr/local/bin/devmem2 Then to run devmem2 to read a value type : sudo devmem2 0x01EF0038 You can replace 0x01EF0038 by the address you want to read.
  13. Found the problem. It was a hardware issue on SD card detect line. A resistor that should not have been there... The units are booting correctly.
  14. Hey guys! So the boards are working relatively correctly now. I just have a boot problem that is happening sometimes. On about 1 boot every 3 or 4 times the unit will not boot. It's random so I am not sure what can be the reason. When the unit can't boot it says (see enclosed pictures too) : Then it seems to try to boot on USB then on PHY (which don't work as nothing is setup) Any idea why this could be happening and why it would be happening only sometimes? The boot config that I use is "orangepi_pc_plus_defconfig" could it be something in there that can be the problem? I can't understand much from this file, is there some explanations of that script content somewhere? Do you think it could be a trace impedance problem with the SD card reader?
  15. I think the guy made the mapping specific to opi PC, and so he left lot of GPIO not mapped. I had trouble with this so in the end I corrected the mapping by adding all the GPIO in the map file. However it is not mapped with connector module. So you should use the GPIO name (port.c) to call it "PA01" ... Find enclosed my pyH3 folder, see specifically the mapping.h file. Again I filled the connectors randomly (as it's different between each SbC I don't think it should be used anyway) so use port. pyH3-0.2.12.rar