Kiosk provider seeking an 8051 assembly language developer to patch firmware to: * Add two i2c commands: 1-turn on 2-turn off Notes: 1. Device has pre-existing soft power control. 2. Device has pre-existing operational I2C interface. 3. Current firmware is available only as ROM image. 4. We -possibly- have some C source code for the 8051-based controller, but it is not configured for the product, nor includes past manufacturer provided customizations. It is probably mostly useful as a reference tool. Deliverable Requirements 1. ROM image: a. With new I2C on/off command functionality. b. Upon boot, the device must start in the existing on state. c. All existing functionality must still be operational. d. Provided in the same ROM-able Intel hex format the original firmware image was supplied in. 2. New functionality in deliverable #1 must pass 100 I2C command off/on test cycles. 3. Assembly language listing for deliverable #1, with descriptive comments documenting changes. 4. Deliverables must be provided within 6 business days from when both parties agree to commencement of work. Available Resources We can provide for the duration of the work: * One controller board for development/testing. -and- * One end-product module which uses the controller board. Work Quotation Please e-mail: * Your all-in fixed price for the work. * Relevant qualifications. * The option of partial payment mid-way through project requires two strong references. Otherwise, payment is upon receipt of the required deliverables.
We have no idea what this system is (other than the vague mention of a "kiosk provider") or does.
Maybe it is trivially simple, and can be reverse-engineered from a ROM image alone in a week.
More likely not...
(I prefer to remain an omnibus)
More likely not... May be Tom Cruise(MI:Infinite) or Daniel Craig(James Bond - RE: Reverse Engineering) can do it.
~ LOOP HOLES ~ We dont even know which specific chip has been used? Whether it has on-chip I2C? What code is already written?
We -possibly- have some C source code for the 8051-based controller, but it is not configured for the product, nor includes past manufacturer provided customizations. It is probably mostly useful as a reference tool.
No assurity of existing Code.
Does any body have any idea of who some one is going to generate the assembler code, (or even C for that matter - if you are Einstein, i dont have any problem) from the ROM image in 6 days (forget writing the patch code)?
"We dont even know which specific chip has been used? Whether it has on-chip I2C? What code is already written?"
Neither do we know the size of this "ROM image".
A couple of hundred bytes shouldn't be hard to disassemble (assuming no deliberate obfuscation)...
c. All existing functionality must still be operational. After reading this, i can only hope and have my fingers crossed that code is less than few hundreds of bytes.
I am a bit worried about how will the contractor differentiate between the const strings/arrays from the actual code? (given only the hex)
I'm interested.
How can I PM the guy?
Richard Marshall BEng(Hons)
View all questions in Keil forum