-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BRAND DIGOO, Model DG-MYQ #7
Comments
thx, will give this a try! |
I renamed start.sh via FTP and after reboot the DG-MYQ seems to be bricked. Anbody solved this issue? |
Hi, |
Hi,
Here is how I did this.
I did the soldering as soon I got the camera. I have the same FTDI. I did
not connected the power to the serial.
I went over the serial connection, then I ran in ti your git, and I found
out that the telnet is available.
Then I cut them
[image: image.png]
I did everything over the telnet then.
You cannot upload over the serial.
You can try different methods though.
Do you get the shell over the serial or not?
If yes, just vi there and edit and save the file you deleted.
or you can share the rootfs onto a NFS I can give you more details,
then change the files onto your shared drive on PC.
If you dont get the shell do you get the u-boot prompt ?
at u-boot you can try if you have the ums
connect the USB as well to your PC
connect the serial
over serial at u-boot prompt you can try
try:
uboot> mmc rescan
mmc list
# see your mmc
then try
connect the USB as well to your PC
connect the serial
over serial at u-boot prompt you can try
ums mmc MMC_BLOCK_#
This if the ums is there should mount a drive onto your computer which is
the emmc from the camera,
If you need the missing file I can sent them to you.
…On Sun, Feb 16, 2020 at 6:56 AM TungstenE2 ***@***.***> wrote:
do you also power on USB in order to get VCC?
I have USB FTDI Adapter for flashing ESP. Should this work? How to adress
cam using telnet in this way? I have done image of the camera using dd. Can
I flash the image back to the camera using the serial connection? Can you
guide me? Thx!
[image: 15818539870380]
<https://user-images.githubusercontent.com/39955685/74604133-5d247c00-50bb-11ea-8a10-b62dc2e8938a.jpg>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7?email_source=notifications&email_token=AB5PRAJQQTJVFOZNEU2IJLTRDESWFA5CNFSM4G4WL65KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL4EYQA#issuecomment-586697792>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB5PRAKOCVJ5GSQADMD2IZ3RDESWFANCNFSM4G4WL65A>
.
|
Ohh you-re on windows.
You don't telnet
You use putty for serial communication, Connect over UART
https://store.chipkin.com/articles/using-putty-for-serial-com-connections-hyperterminal-replacement/
The speed I don't remember you can try 9600 38400 115200, try all speed
from Upper 115200 to lower
9600, until you see the shell.
Then try to mount the nfs like in the
section *get file system* @ https://github.com/comarius/digoo-DG-MIQ-720p
I dont know how to do that on windows but you can find it out there.
https://www.poftut.com/how-to-mount-nfs-share-in-linux-and-windows/
Let em know if you have any progress.
…On Sun, Feb 16, 2020 at 11:38 AM TungstenE2 ***@***.***> wrote:
Thx, the FTDI adapter shows up in Windows on USB serial port COM3.
How do I telnet to this COM3 using eg MobaXterm ? Tried like in Screenshot
below.
Did you set the FTDI adapter to 5v or 3.5V?
[image: grafik]
<https://user-images.githubusercontent.com/39955685/74608617-09c62400-50e3-11ea-800f-036c4135d750.png>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7?email_source=notifications&email_token=AB5PRAM2766F5C7JNR2XOADRDFTXXA5CNFSM4G4WL65KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL4LYVQ#issuecomment-586726486>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB5PRAI6UPPDRCEEW3OM6ZLRDFTXXANCNFSM4G4WL65A>
.
|
I have not seen your screen shot.
THat's promising. Try different speeds for UART starting at 115200, then go
lower until you see the right characters.
9600, 14,400, 19,200, 38,400, 57,600, and 115,200
…On Sun, Feb 16, 2020 at 11:45 AM TungstenE2 ***@***.***> wrote:
ok, I get something like this
[image: grafik]
<https://user-images.githubusercontent.com/39955685/74608752-231ba000-50e4-11ea-94c6-c9bddac21d4e.png>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7?email_source=notifications&email_token=AB5PRAPYIOS3OUWKZKJFDO3RDFUTLA5CNFSM4G4WL65KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL4L6XA#issuecomment-586727260>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB5PRAOZCQKGQB5P3GCRNT3RDFUTLANCNFSM4G4WL65A>
.
|
digooo home folder
…On Sun, Feb 16, 2020 at 11:48 AM Co M ***@***.***> wrote:
I have not seen your screen shot.
THat's promising. Try different speeds for UART starting at 115200, then
go lower until you see the right characters.
9600, 14,400, 19,200, 38,400, 57,600, and 115,200
On Sun, Feb 16, 2020 at 11:45 AM TungstenE2 ***@***.***>
wrote:
> ok, I get something like this
> [image: grafik]
> <https://user-images.githubusercontent.com/39955685/74608752-231ba000-50e4-11ea-94c6-c9bddac21d4e.png>
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#7?email_source=notifications&email_token=AB5PRAPYIOS3OUWKZKJFDO3RDFUTLA5CNFSM4G4WL65KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL4L6XA#issuecomment-586727260>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AB5PRAOZCQKGQB5P3GCRNT3RDFUTLANCNFSM4G4WL65A>
> .
>
|
To be honest I give up. The pads are very small for my soldering and I tried serveral times to connect. Also my SD card slot is broken. So I declare this a brick. Not worth spending more time ob this cam. Thx for your help. |
I you find these appropriate, you can add them to the readme.
The serial (I have no picture) pins are by the side of the micros SD card. The pins are Rx Gnd Tx, and they are 3 little soldering pads with holes.
Telnet was enabled by default.
First: vi /home/wps_supplicant.conf
home folder is permanent and can be changed.
vi /home/wpa_supplicant.conf
Second: configure camera with the mobile app.
Disable the cloud access: commenting all as shown
./cloud.ini & ./cloud_oversea.ini
In config.cfg screw up the ID's
Save.
Edit start.sh, Look for: <<<<
If you did not run p2pcam you can configure your wifi form shell
The camera wont access the cloud anymore.
The text was updated successfully, but these errors were encountered: