Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Jack_Simth]

Hello all,

When I found out that D-Link posts most of their firmware source as part of GPL compliance (Bravo!!!), I started thinking about various projects I could do with that - systemically scan a room when it detects noise, build composite snapshots of a larger room, send a self-recovering rtmps video stream to a target internet address, and many other possibilities. 

Anyway: I seem to be able to compile it... but in order to do some of these things, I need to have a better idea of what resources it has in terms of RAM, CPU, existing commands, available flash memory for additional software components, et cetera.  Does anyone have data on those things, ideas of how I could get them, or experience with modifying the firmware?

Thanks.

[FurryNutz]

Might check OpenWRT or DD-WRT or WikiDevi to see if they have specs listed for this model camera.

[Jack_Simth]

Thank you.

Sadly, I'm having difficulties locating that model on the referenced sites.  Oh well; that just means I'll need to do it the hard way... maybe modify the firmware to have it send me the data on boot up (which... basically means assuming a few things will exist - curl and/or mail... and using those assumptions to make firmware to send the results of things like 'ls -lR /', 'cat /proc/cpuinfo', 'cat /proc/meminfo' and similar to myself in various ways). 

[FurryNutz]

Might check with D-Link to see if they have any GPL code, if they do then you could compile your own FW.

[Jack_Simth]

Might check with D-Link to see if they have any GPL code, if they do then you could compile your own FW.

I don't need to ask them.  I already found it.  The firmware for the DCS-5030L is posted right along with the rest for public download, requiring no login, just an access agreement that mostly boils down to "we don't support any of the stuff you find here, and you could break our hardware pretty hard doing this sort of thing yourself, so don't blame us if you break it" with some additional notes about them including a few closed binaries in the mix, as well as some standard disclaimers that go with any software that includes mixes licenses.  I can dig out what I need myself when I have the time, I was just hoping someone had already done the work and was willing to share. No big deal if the shortcut doesn't exist.

[FurryNutz]

Let us know if you get it going.