Code Monkey home page Code Monkey logo

lamobo-d1's Introduction

Lamobo-D1 Development Environment

The Latest Build

Build Status Download

Firmware Build Steps

  1. Tested OS

    • Ubuntu 12.04.3 32Bit
    • Ubuntu 12.04.3 64Bit
  2. Clone

    cd ~
    git clone https://github.com/Lamobo/Lamobo-D1.git
    
  3. Build

    ~/Lamobo-D1/build/build.sh
    
  4. Check

    cd ~/Lamobo-D1/output
    ls -l D1_Basic*.zip
    ls -l D1_Extra*.zip
    
  5. Clean

    ~/Lamobo-D1/build/build.sh clean
    

Firmware Flash Steps

  1. Tested OS

    • Windows 7 Professional 32Bit
    • Windows 7 Professional 64Bit
  2. Prepare

    1. [PC] Connect D1 flashing port to PC via USB cable
    2. [PC] Extract D1_Basic*.zip (firmware and burntool)
  3. Flash

    1. [PC] Start "Burn Tool" application by double-click "BurnTool.exe"
    2. [D1] Power on D1 (press and hold "function" key before power on)
    3. [PC] Hold "Boot/WPS" key and wait until "Burn Tool" displays "Ready"
    4. [PC] Start flashing by click "Start" in "Burn Tool"
    5. [PC] [Optional] Extract D1_Extra*.zip (extra programs) to the TFCard
  4. Complete

    1. [D1] Unplug power cable
    2. [D1] Plug power cable to power on
    3. [D1] Now D1 started with the new firmware

lamobo-d1's People

Contributors

lamobo avatar steka avatar zonesan avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

lamobo-d1's Issues

Cannot connect to my ap

I link to 192.168.0.1 and wanna set the wireless to my ap

But I set the password and click save button. It doesn't connected to my AP.

Is the webpage wrong?

AK ISP Tool

My device is connected to WiFi network, I can ping the device as well see the streams. But while running ISP Tool, I keep on getting "Not search any server!" when I search for device.

Please help.

URL for streaming from Anyka IP Camera

Hello!:

I got broken my NVR but the cameras still working and want to use motioneye OS to use them mean while I got a new NVR, but cannot find the URL needed to connect via RTSP, RTMP, MJPEG or JPEG, any guidance is very wellcomed Thanks

3G/ 4G modem connect

I want the modem to work on BPI-D1. I connected to BPI various modems (huawei e1550, ZTE823d - usb ethernet), installing the necessary modules. All modems were correctly defined, but they did not exchange data with BPI. Does anyone have any ideas or examples?

default with RTC driver and hwclock...;

i have post an issue on http://www.bananapi.com/bbs/Show.aspx?tid=909&page=2
hwclock return bad date, confusing day and seconde.
I am testing with release tohax@bdf9584 , the same problem exist.
the rtc device is DS1337S in schematic bananapi-D1

datasheet of DS1337S https://datasheets.maximintegrated.com/en/ds/DS1337-DS1337C.pdf
with tool i2c-test i can read rtc device

[root@Lamobo-D1 ~]$ /mnt/local/bin/i2c-test r 0x68 0 0x6
Open i2c device successfully !
Set slave addr to 0x68!
Read 0x0039 from 0x68[0x00]            <-- seconde in rtc device [00-59]
Read 0x0046 from 0x68[0x01]            <-- minute   in rtc device [00-59]
Read 0x0001 from 0x68[0x02]            <-- hour       in rtc device [00-23 or 00-11]
Read 0x0004 from 0x68[0x03]            <-- day       in rtc device [1-7]
Read 0x0011 from 0x68[0x04]            <-- date       in rtc device [1-31]
Read 0x0001 from 0x68[0x05]            <-- mounth  in rtc device [1-12]
Read 0x0000 from 0x68[0x06]            <-- year       in rtc device [00-99]

[root@Lamobo-D1 ~]$ /mnt/local/bin/i2c-test r 0x68 0 0x6; date -u; hwclock
Open i2c device successfully !
Set slave addr to 0x68!
Read 0x0005 from 0x68[0x00]
Read 0x0021 from 0x68[0x01]
Read 0x0002 from 0x68[0x02]
Read 0x0004 from 0x68[0x03]
Read 0x0011 from 0x68[0x04]
Read 0x0001 from 0x68[0x05]
Read 0x0000 from 0x68[0x06]
Fri Jan 13 01:21:10 CST 2017          **<-- GMT system date**
Sat Jan  5 02:21:05 2002  0.000000 seconds   **<-- hwclock**

decoding rtc registers say : [04]=Fri [01]=Jan [11]=13 [00]=2000 [02][21][05]=02:21:05
content register was set by ntpd -q -p pool.ntp.org (error on year ...?),

But when read register with hwclock more errors ( seem read register 00 as day and register 01 as month and register 02 as year ......)

[root@Lamobo-D1 ~]$ /mnt/local/bin/i2c-test r 0x68 0 0x6; date -u ; hwclock
Open i2c device successfully !
Set slave addr to 0x68!
Read 0x0005 from 0x68[0x00]
Read 0x0043 from 0x68[0x01]
Read 0x0002 from 0x68[0x02]
Read 0x0004 from 0x68[0x03]
Read 0x0011 from 0x68[0x04]
Read 0x0001 from 0x68[0x05]
Read 0x0000 from 0x68[0x06]
Fri Jan 13 01:43:09 UTC 2017
Tue Mar  5 02:43:05 2002  0.000000 seconds
[root@Lamobo-D1 ~]$ /mnt/local/bin/i2c-test r 0x68 0 0x6; date -u ; hwclock
Open i2c device successfully !
Set slave addr to 0x68!
Read 0x0006 from 0x68[0x00]
Read 0x0043 from 0x68[0x01]
Read 0x0002 from 0x68[0x02]
Read 0x0004 from 0x68[0x03]
Read 0x0011 from 0x68[0x04]
Read 0x0001 from 0x68[0x05]
Read 0x0000 from 0x68[0x06]
Fri Jan 13 01:43:11 UTC 2017
Wed Mar  6 02:43:06 2002  0.000000 seconds
[root@Lamobo-D1 ~]$ /mnt/local/bin/i2c-test r 0x68 0 0x6; date -u ; hwclock
Open i2c device successfully !
Set slave addr to 0x68!
Read 0x0007 from 0x68[0x00]
Read 0x0043 from 0x68[0x01]
Read 0x0002 from 0x68[0x02]
Read 0x0004 from 0x68[0x03]
Read 0x0011 from 0x68[0x04]
Read 0x0001 from 0x68[0x05]
Read 0x0000 from 0x68[0x06]
Fri Jan 13 01:43:12 UTC 2017
Thu Mar  7 02:43:07 2002  0.000000 seconds
[root@Lamobo-D1 ~]$ /mnt/local/bin/i2c-test r 0x68 0 0x6; date -u ; hwclock
Open i2c device successfully !
Set slave addr to 0x68!
Read 0x0031 from 0x68[0x00]
Read 0x0043 from 0x68[0x01]
Read 0x0002 from 0x68[0x02]
Read 0x0004 from 0x68[0x03]
Read 0x0011 from 0x68[0x04]
Read 0x0001 from 0x68[0x05]
Read 0x0000 from 0x68[0x06]
Fri Jan 13 01:43:35 UTC 2017
Sun Mar 31 02:43:31 2002  0.000000 seconds
[root@Lamobo-D1 ~]$ /mnt/local/bin/i2c-test r 0x68 0 0x6; date -u ; hwclock
Open i2c device successfully !/mnt/local/bin/i2c-test r 0x68 0 0x6
Set slave addr to 0x68!
Read 0x0038 from 0x68[0x00]
Read 0x0043 from 0x68[0x01]
Read 0x0002 from 0x68[0x02]
Read 0x0004 from 0x68[0x03]
Read 0x0011 from 0x68[0x04]
Read 0x0001 from 0x68[0x05]
Read 0x0000 from 0x68[0x06]
Fri Jan 13 01:43:43 UTC 2017
hwclock: RTC_RD_TIME: Invalid argument <-- **not exist March 38 !!!!!!!!**

Can you help me ?

VFS: Cannot open root device

There is something wrong in the current kernel.

VFS: Cannot open root device "mtdblock1" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
1f00 16384 mtdblock0 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

At the moment i cant figured out where the problem is. I tried mtdblock0 too but it does not work.
Which drivers are needed? Or can you provide an older version?

Not Connecting to WiFi

I am using the Banana Pi D1 with the official Banana Pi WiFi Module. I am able to boot the device and connect to it when it is broadcasting as an AP.

From the wireless table I found my wifi network at saved my password. The instructions say that once this is saved to press the function key and it will switch to slave mode and the LED will blink. It does blink but only for a second and then goes back to solid and does nothing.

I've been told you have to edit /etc/jffs2/camera.ini, the [wireless] block. I have not been able to connect over serial but either way the fact it isn't working from the control panel seems like an issue. Any advice? I am using the latest 2.0 image.

http://bananapi.com/index.php/forum/general-discussion-for-bpi-d1/564-connect-to-wifi

stuck at massboot

how do i boot from SD Card? when i try to use burn tool it gets stuck at decompressing done, booting kernel

anyka default username/password

what is the default username/password for the system?
tried:

  • admin/admin
  • admin/password
  • Researcher/

Able to connect to telnet
Ask login/password
I can't find login/password

SDIO use

Hello,

On gpio pins there is alternate option for SPI. I would like to use SDIO for connecting a wifi chip, how can I do it?

rtl8152

Somebody manage to connect usb to lan adpater to bpi-d1?

更改工作模式

摄像头现在连接电源后就开始录制,怎样修改使录制可控,或者说哪部分源码与这个功能相关

Qemu emulation

has anyone tried to run the kernel with qemu ? i tried to emulate it with Qemu but no luck.

Video quality issue in firmware ver 3.0

In firmware ver 3.0, there are some noticeable color variations every few frames, not in a consistent periods.
That issue is not noticeable in firmware ver 2.0.

I tried (with no luck):

  1. streaming mode vs. recorded video file - the same.
  2. .avi and mp4 file types.
  3. ipcamera application vs. record_video sample.
  4. switching the board, switching camera sensor.
  5. pre-build and self-build firmware.

Bug in record_video sample

There is a bug in src/samples/record_video/main.c.

Line 215 (time_flag = 1;) needs to be inside the if branch above, eg:

if (ts > 1000)
{
    printf("get ts is %ld\n",ts);
    camera_usebufok();

    gettimeofday(&tv, NULL);
    t0 = tv.tv_sec*1000 + tv.tv_usec/1000;
    times = t0 + ext_gSettings->enc_time*1000;
    time_flag = 1;

    continue;
}

Without this, it never gets past the initial stage of discarding frames until ts>1000, and the output file remains empty.

Windows 10

Both tools (Anyka IP Camera.exe and ISPControl.exe) do not run on Windows 10. Can you please rebuild them or open up the source code. Thanks!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.