/dev/sda is the flash drive
/dev/mem is the sdram

fdisk /dev/sda
p

will give you a clue about the flash drive's arrangement

and

gdb -k -wcore kernel.debug /dev/mem

should give the sdram stack details. You can always dump these to a
file using dd or > expression. I asked about Python because if you
find workarounds to extract addresses of these blocks, you can easily
wrap all of them with Python.

2012/1/30  <jana1972@centrum.cz>:
>
>> 2- Go through the /proc (do cat on probable options)
> Which options should I do cat on?
>
>> 3- By flash you mean the drive that the OS is installed on ?
> Yes
>
>>Can you
>> do a "ls -a /dev" and provide the output ?
> Here it is
> root@me:~# ls -a /dev
> . =A0 =A0 =A0 =A0 =A0 =A0 =A0 sda1 =A0 =A0 =A0 =A0 =A0 =A0tty49 =A0 =A0 =
=A0 =A0 =A0 ttyS36
> .. =A0 =A0 =A0 =A0 =A0 =A0 =A0sg0 =A0 =A0 =A0 =A0 =A0 =A0 tty5 =A0 =A0 =
=A0 =A0 =A0 =A0ttyS37
> .udev =A0 =A0 =A0 =A0 =A0 shm =A0 =A0 =A0 =A0 =A0 =A0 tty50 =A0 =A0 =A0 =
=A0 =A0 ttyS38
> XOR =A0 =A0 =A0 =A0 =A0 =A0 snd =A0 =A0 =A0 =A0 =A0 =A0 tty51 =A0 =A0 =A0=
 =A0 =A0 ttyS39
> audio =A0 =A0 =A0 =A0 =A0 tpm0 =A0 =A0 =A0 =A0 =A0 =A0tty52 =A0 =A0 =A0 =
=A0 =A0 ttyS4
> block =A0 =A0 =A0 =A0 =A0 tty =A0 =A0 =A0 =A0 =A0 =A0 tty53 =A0 =A0 =A0 =
=A0 =A0 ttyS40
> bus =A0 =A0 =A0 =A0 =A0 =A0 tty0 =A0 =A0 =A0 =A0 =A0 =A0tty54 =A0 =A0 =A0=
 =A0 =A0 ttyS41
> char =A0 =A0 =A0 =A0 =A0 =A0tty1 =A0 =A0 =A0 =A0 =A0 =A0tty55 =A0 =A0 =A0=
 =A0 =A0 ttyS42
> console =A0 =A0 =A0 =A0 tty10 =A0 =A0 =A0 =A0 =A0 tty56 =A0 =A0 =A0 =A0 =
=A0 ttyS43
> dbox =A0 =A0 =A0 =A0 =A0 =A0tty11 =A0 =A0 =A0 =A0 =A0 tty57 =A0 =A0 =A0 =
=A0 =A0 ttyS44
> disk =A0 =A0 =A0 =A0 =A0 =A0tty12 =A0 =A0 =A0 =A0 =A0 tty58 =A0 =A0 =A0 =
=A0 =A0 ttyS45
> dsp =A0 =A0 =A0 =A0 =A0 =A0 tty13 =A0 =A0 =A0 =A0 =A0 tty59 =A0 =A0 =A0 =
=A0 =A0 ttyS46
> dvb =A0 =A0 =A0 =A0 =A0 =A0 tty14 =A0 =A0 =A0 =A0 =A0 tty6 =A0 =A0 =A0 =
=A0 =A0 =A0ttyS47
> fb =A0 =A0 =A0 =A0 =A0 =A0 =A0tty15 =A0 =A0 =A0 =A0 =A0 tty60 =A0 =A0 =A0=
 =A0 =A0 ttyS48
> fb0 =A0 =A0 =A0 =A0 =A0 =A0 tty16 =A0 =A0 =A0 =A0 =A0 tty61 =A0 =A0 =A0 =
=A0 =A0 ttyS49
> full =A0 =A0 =A0 =A0 =A0 =A0tty17 =A0 =A0 =A0 =A0 =A0 tty62 =A0 =A0 =A0 =
=A0 =A0 ttyS5
> fuse =A0 =A0 =A0 =A0 =A0 =A0tty18 =A0 =A0 =A0 =A0 =A0 tty63 =A0 =A0 =A0 =
=A0 =A0 ttyS50
> i2c =A0 =A0 =A0 =A0 =A0 =A0 tty19 =A0 =A0 =A0 =A0 =A0 tty7 =A0 =A0 =A0 =
=A0 =A0 =A0ttyS51
> i2c-0 =A0 =A0 =A0 =A0 =A0 tty2 =A0 =A0 =A0 =A0 =A0 =A0tty8 =A0 =A0 =A0 =
=A0 =A0 =A0ttyS52
> i2c-1 =A0 =A0 =A0 =A0 =A0 tty20 =A0 =A0 =A0 =A0 =A0 tty9 =A0 =A0 =A0 =A0 =
=A0 =A0ttyS53
> i2c-2 =A0 =A0 =A0 =A0 =A0 tty21 =A0 =A0 =A0 =A0 =A0 ttyS0 =A0 =A0 =A0 =A0=
 =A0 ttyS54
> i2c-3 =A0 =A0 =A0 =A0 =A0 tty22 =A0 =A0 =A0 =A0 =A0 ttyS1 =A0 =A0 =A0 =A0=
 =A0 ttyS55
> i2c-4 =A0 =A0 =A0 =A0 =A0 tty23 =A0 =A0 =A0 =A0 =A0 ttyS10 =A0 =A0 =A0 =
=A0 =A0ttyS56
> initctl =A0 =A0 =A0 =A0 tty24 =A0 =A0 =A0 =A0 =A0 ttyS11 =A0 =A0 =A0 =A0 =
=A0ttyS57
> input =A0 =A0 =A0 =A0 =A0 tty25 =A0 =A0 =A0 =A0 =A0 ttyS12 =A0 =A0 =A0 =
=A0 =A0ttyS58
> kmem =A0 =A0 =A0 =A0 =A0 =A0tty26 =A0 =A0 =A0 =A0 =A0 ttyS13 =A0 =A0 =A0 =
=A0 =A0ttyS59
> kmsg =A0 =A0 =A0 =A0 =A0 =A0tty27 =A0 =A0 =A0 =A0 =A0 ttyS14 =A0 =A0 =A0 =
=A0 =A0ttyS6
> log =A0 =A0 =A0 =A0 =A0 =A0 tty28 =A0 =A0 =A0 =A0 =A0 ttyS15 =A0 =A0 =A0 =
=A0 =A0ttyS60
> mem =A0 =A0 =A0 =A0 =A0 =A0 tty29 =A0 =A0 =A0 =A0 =A0 ttyS16 =A0 =A0 =A0 =
=A0 =A0ttyS61
> misc =A0 =A0 =A0 =A0 =A0 =A0tty3 =A0 =A0 =A0 =A0 =A0 =A0ttyS17 =A0 =A0 =
=A0 =A0 =A0ttyS62
> mixer =A0 =A0 =A0 =A0 =A0 tty30 =A0 =A0 =A0 =A0 =A0 ttyS18 =A0 =A0 =A0 =
=A0 =A0ttyS63
> mtd0 =A0 =A0 =A0 =A0 =A0 =A0tty31 =A0 =A0 =A0 =A0 =A0 ttyS19 =A0 =A0 =A0 =
=A0 =A0ttyS7
> mtd0ro =A0 =A0 =A0 =A0 =A0tty32 =A0 =A0 =A0 =A0 =A0 ttyS2 =A0 =A0 =A0 =A0=
 =A0 ttyS8
> mtd1 =A0 =A0 =A0 =A0 =A0 =A0tty33 =A0 =A0 =A0 =A0 =A0 ttyS20 =A0 =A0 =A0 =
=A0 =A0ttyS9
> mtd1ro =A0 =A0 =A0 =A0 =A0tty34 =A0 =A0 =A0 =A0 =A0 ttyS21 =A0 =A0 =A0 =
=A0 =A0urandom
> mtd2 =A0 =A0 =A0 =A0 =A0 =A0tty35 =A0 =A0 =A0 =A0 =A0 ttyS22 =A0 =A0 =A0 =
=A0 =A0usbdev1.1_ep00
> mtd2ro =A0 =A0 =A0 =A0 =A0tty36 =A0 =A0 =A0 =A0 =A0 ttyS23 =A0 =A0 =A0 =
=A0 =A0usbdev1.1_ep81
> mtd3 =A0 =A0 =A0 =A0 =A0 =A0tty37 =A0 =A0 =A0 =A0 =A0 ttyS24 =A0 =A0 =A0 =
=A0 =A0usbdev2.1_ep00
> mtd3ro =A0 =A0 =A0 =A0 =A0tty38 =A0 =A0 =A0 =A0 =A0 ttyS25 =A0 =A0 =A0 =
=A0 =A0usbdev2.1_ep81
> mtdblock0 =A0 =A0 =A0 tty39 =A0 =A0 =A0 =A0 =A0 ttyS26 =A0 =A0 =A0 =A0 =
=A0usbdev3.1_ep00
> mtdblock1 =A0 =A0 =A0 tty4 =A0 =A0 =A0 =A0 =A0 =A0ttyS27 =A0 =A0 =A0 =A0 =
=A0usbdev3.1_ep81
> mtdblock2 =A0 =A0 =A0 tty40 =A0 =A0 =A0 =A0 =A0 ttyS28 =A0 =A0 =A0 =A0 =
=A0vc
> mtdblock3 =A0 =A0 =A0 tty41 =A0 =A0 =A0 =A0 =A0 ttyS29 =A0 =A0 =A0 =A0 =
=A0vcs
> null =A0 =A0 =A0 =A0 =A0 =A0tty42 =A0 =A0 =A0 =A0 =A0 ttyS3 =A0 =A0 =A0 =
=A0 =A0 vcs1
> port =A0 =A0 =A0 =A0 =A0 =A0tty43 =A0 =A0 =A0 =A0 =A0 ttyS30 =A0 =A0 =A0 =
=A0 =A0vcsa
> ptmx =A0 =A0 =A0 =A0 =A0 =A0tty44 =A0 =A0 =A0 =A0 =A0 ttyS31 =A0 =A0 =A0 =
=A0 =A0vcsa1
> pts =A0 =A0 =A0 =A0 =A0 =A0 tty45 =A0 =A0 =A0 =A0 =A0 ttyS32 =A0 =A0 =A0 =
=A0 =A0zero
> random =A0 =A0 =A0 =A0 =A0tty46 =A0 =A0 =A0 =A0 =A0 ttyS33
> sci0 =A0 =A0 =A0 =A0 =A0 =A0tty47 =A0 =A0 =A0 =A0 =A0 ttyS34
> sda =A0 =A0 =A0 =A0 =A0 =A0 tty48 =A0 =A0 =A0 =A0 =A0 ttyS35
>
>
>
> Yes, I can run Python.Will it help?
> Thanks
>
>>
>> If we were talking about a regular x86 that this was a piece of cake
>> but in this case because the instruction set is limited, everyday
>> workarounds will not work. Can you run Python on the box?
>>
>> 2012/1/30 =A0<jana1972@centrum.cz>:
>> > Hi,
>> > yes, I have root access on the box
>> > It is Debian like =A0system but a little restricted because it is an e=
mbeded Debian
>> >
>> >
>> >
>> >> You got root on the box ? What is the exact OS ?
>> >>
>> >> 2012/1/30 =A0<jana1972@centrum.cz>:
>> >> >> Can you boot the device, access the console ?
>> >> > Yes, I can boot it up.I can connect to it via telnet.
>> >> > And I can access to the console and use =A0Linux commands.
>> >> > Do you have any idea how to find out memory ranges?
>> >> > Thanks
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >> Can you boot the device, access the console ?
>> >> >>
>> >> >> On Mon, Jan 30, 2012 at 7:25 PM, =A0<jana1972@centrum.cz> wrote:
>> >> >> > I have a Linux embeded =A0device that consists
>> >> >> > CPU, BIOS,FLASH and SDRAM.
>> >> >> >
>> >> >> > Is there any way how to find out which memory range is assigned =
to BIOS and which
>> >> >> > addresses are assigned to flash and which SDRAM?
>> >> >> > Thanks
>> >> >> >
>> >> >> > --
>> >> >> > http://www.piclist.com PIC/SX FAQ & list archive
>> >> >> > View/change your membership options at
>> >> >> > http://mailman.mit.edu/mailman/listinfo/piclist
>> >> >>
>> >> >> --
>> >> >> http://www.piclist.com PIC/SX FAQ & list archive
>> >> >> View/change your membership options at
>> >> >> http://mailman.mit.edu/mailman/listinfo/piclist
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > http://www.piclist.com PIC/SX FAQ & list archive
>> >> > View/change your membership options at
>> >> > http://mailman.mit.edu/mailman/listinfo/piclist
>> >>
>> >> --
>> >> http://www.piclist.com PIC/SX FAQ & list archive
>> >> View/change your membership options at
>> >> http://mailman.mit.edu/mailman/listinfo/piclist
>> >
>> >
>> >
>> > --
>> > http://www.piclist.com PIC/SX FAQ & list archive
>> > View/change your membership options at
>> > http://mailman.mit.edu/mailman/listinfo/piclist
>>
>> --
>> http://www.piclist.com PIC/SX FAQ & list archive
>> View/change your membership options at
>> http://mailman.mit.edu/mailman/listinfo/piclist
>
>
>
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.