There’s not much information about eCos firmware analysis online so we were left blind. This clearly indicates that the load address is incorrect and we need a way to obtain the load address of that firmware. We see that functions are not recognized and the whole segment is left in “unexplored” state. The screenshot below illustrates what happens when you load such a binary in IDA with the right architecture but the wrong load address. ![]() Without knowledge of the load address for that binary, reverse engineering it with any SRE tool will fail given that cross-references cannot be established. ![]() 0 0x0 eCos kernel exception handler, architecture: MIPSEL, exception vector table base address: 0x80000200ġ28 0x80 eCos kernel exception handler, architecture: MIPSEL, exception vector table base address: 0x80000200ĥ475588 0x538D04 Unix path: /home/remus/svn/ivs/IVSPL5-ZyXEL_New/src_0603/build/./build/obj/ecos/ install/include/cyg/libc/stdlib/atox.inlĥ475653 0x538D45 eCos RTOS string reference: "ecos/install/include/cyg/libc/stdlib/atox.inl"ĥ945083 0x5AB6FB eCos RTOS string reference: "ecos_driver_vid_to_if_index !"ĥ949577 0x5AC889 eCos RTOS string reference: "ecos_driver_inject vid=%u, length=%u"Ħ525239 0圆39137 eCos RTOS string reference: "eCos/packages/devs/serial/generic/16x5x/current/src/ser_16x5x.c "
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |