1. RAJASHAKER GOUD RANGA
Citizenship : Indian ▪ Date of birth : 03 Mar 1986
Contact
Tel : +60 10 392 2432
e-mail ID :
rajashakergoudranga@gmail.com
Objectives
To obtain a challenging and responsible position of Firmware Engineer that facilitates learning and
Provides strong communicational, organizational, analytical and technical skills to design & develop
firmware for the next generation technology. I feel that my educational qualification as well as the
previous work experience will definitely help me to serve better for the organization.
Education
2005 to 2009 Bachelor in ELECTRONICS&COMMUNICATION ENGINEERING with an
aggregate of 71.80%
UNIVERSITY :Jawaharlal Nehru Technological University, Hyderabad, AP
COLLEGE : Vathsalya Institute of Science and Technology, Bhongir. Affiliated to
J.N.T.U.,Hyderabad
2003 to 2005 Intermediate with an aggregate of 92.3%
INSTITUTION : Board of Intermediate Education, Andhra Pradesh
COLLEGE : Narayana Junior college, Hyderabad, AP.
1992 to 2003 SSC with an aggregate of 73%
INSTITUTION : Board of secondary Education, Andhra Pradesh
SCHOOL : Bhoopathy High School, Hyderabad, AP.
Professional Experience
Currently Employed with : US Technology Resources (M) Sdn Bhd.
Employed since : 7th
August 2013 to till date
Current designation : Embed Software Lead
Previous Experience details :
Employed with : American megatrends India Pvt Ltd.
Employed since : 12th
July 2010 to 23rd
June 2013
Designation : System Software Engineer
Brief Role : Feature Implementation, Coding, Porting and Bug fixing.

2. Detail note on work experience:
6 years of experience in working with different platform BIOS baytrail, braswell, Broxton, cherry trail, Piketon,
Sandybridge, etc., Currently working on FSP and coreboot for these platform. Also expertise in BIOS Porting, Bug
Fixing and Validation. Worked in APTIO V, INTEL EDKII Projects.

3. Project Experience
COREBOOT & FSP customization (IoTG Group):
Client: Intel, Malaysia Role: Porting, Bug fixing, Implementation and Unit testing.
Environment : EDKII Duration: April 2015 to till date
The activity includes comparing the schematics, identifying the platform changes, customizing Coreboot to
Bayley bay and cherry trail platform board and support UEFI and legacy boot. Also, integrate the legacy and UEFI
payloads and debug and resolve the issues during OS boot.
Roles & Responsibilities:
The project is in development phase, currently working on Bayley Bay and Cherry hill Platforms and worked
on below customer requirements.
a) Thermal zone implementation for customized hardware, where no platform sensors present
and to utilize CPU DTS, use internal PUNIT interrupts.
b) Implement EFI DXE driver for thermal trip and throttling under EFI payload.
c) Resolved the show stopper issue that the customer unable to install WIN7 on top of
COREBOOT+FSP + SEABIOS combination due to not detecting USB keyboard and mouse.
d) Resolved the show stopper issue that Linux unable use HSUART and I2C devices when LPSS
devices are configured in ACPI mode.
e) Integrate network stack in UEFI payload to support PXE boot.
f) Configure turbo boost feature enabled
g) Implement ACPI tables for LPSS devices
h) Integrate latest FSP to the customer core boot
i) Calculate the boot time using the timestamps and display in log
j) Customize the corboot and payload in order to display most minimized boot time.
k) Debug and resolve the issues related to FSP, ACPI resources and interrupts.
Intelligent Systems Group (ISG):
Client: Intel, Malaysia Role: Porting, Bug fixing, Implementation and Unit testing.
Environment : AptioV Duration: August 2013 to March 2015
The activity includes comparing the schematics, identifying the platform changes, customizing BIOS to Bayley bay
and BakeSport CRB board. Added support to booting SD, legacy usb boot to OS. Added support to 64 bit legacy
usb and sd card booting. Provided OS Selection CMOS setup option to customize the setup options for
appropriate OS selected in Setup.
Roles & Responsibilities:
The project is in development phase, currently working on Bayley Bay FAB-3 and BakerSport FAB- B boards.
a) Involved in requirement gathering and Analysis
b) Involved in preparation of Design Documents
c) Code Review and performance tuningBug fixing of modules and modularization
d) Involved in coding and unit testing
e) Provided support of Legacy usb, legacy sdcard booting for baytrail platform (Baley
bay and bakersport boards.)
f) Involved in check in changes (clear case), Build and release of the BIOS images.

4. Text Setup Environment (TSE):
Client: AMI USA Role: Porting, Bug fixing, Implementation and Unit testing.
Environment : EDKII Duration: July 2010 to June 2013
The Text Setup Environment (TSE) is the AMI firmware user interface designed to work in conjunction with Aptio.
TSE is a drop-in eModule for Aptio and is UEFI compatible. Being modular, specific features can be enabled or
disabled during build time.TSE is installed during the DXE dispatch phase and requests notification of the console
devices in order to manage them as soon as they are available. During the initialization phase, TSE publishes a
protocol that has to be used by BDS to invoke TSE. TSE gets control from BDS after EFI drivers have been started
but before starting the boot timeout. This allows user input and handing off control of the system to the booting
device. TSE is a substitute for the second half of the BDS phase.
TSE does 3 functionalities they are Boot Manager, Post Manager and displaying the setup.
Post Manager: Is responsible for initializing the setup and displaying logos and copyright messages during
initialization of the firmware.
Setup: Provides the user Interface for getting the user input and changing the boot order etc. The setup can be
configurable with the user’s style.
Driver health protocol support:
Provided support for checking driver health in setup. If any boot device failed to boot then TSE will check
whether any driver need repair if so then TSE will do necessary operations to rescue the driver using driver
health protocol.
Also, TSE will displays the health status of the drivers in the separate page if any drivers supports driver health.
User can do appropriate action like repair from this page.
Since the card which publish driver health are not available here in India so, wrote sample driver which does the
Operations required like GetHealthStatus, Repair and DrvHealth.
Boot Manager: Is a component in firmware that determines which drivers and applications should be explicitly
loaded and when.
TSE is made up of a series of drivers, applications and images, which can be customized to an OEM’s look and
feel, or can use AMI’s default interface.
Windows8MetroStyle:
Client: AMI USA Role: Porting, Bug fixing, Implementation and Unit testing.
Environment : EDKII Duration: July 2012 to June 2013
The Windows8MetroStyle (Metro) is the AMI firmware user interface designed to work in conjunction with
Aptio. The Setup Environment in the firmware consist of the following functionality blocks.
POST & Boot Manager
UEFI Setup Engine
Text Setup Browser
Graphical Setup Browser
OEM/Board Customization module
UI based Setup page customization
Should be easy configurable and customizable for firmware space.
Technical Skills
Proficient or familiar with a vast array of programming languages, concepts and technologies, including
Architecture : X86 – IA32
Components: PCI, ISA, SPI, AHCI, USB, Option ROM, Flash, ACPI.
Languages : Assembly (ASM), C.
Technology : UEFI
Product : AptioV, EDKII and Veb.
Tools : ITP,SoftSdv,Simics,AFU,MM tool
OS : Windows, Linux(Yocto)
Quality : Compliant to ISO standard quality documentation process.
Achievements
 Submitted technical paper on converting modules from EDK to EDKII, which is presented in
AMI India annual meeting held at Asiana hotel.
 Participated in National level technical paper presentation on GPS which is held at Bhojreddy
College HYD during graduation.
Personal Details
First Name : Rajashaker Goud
Last Name : Ranga
Age : 29
Gender : Male
Marital Status: Unmarried
Address for Communication: #1B-12B-2, Elite heights, Bayan lepas, Pulau Pinang, PIN 11900.

5. Client: AMI India Role: Porting, Bug fixing, Implementation and Unit testing.
Environment : EDKII Duration: July 2010 to June 2013
 Wrote sample driver to check for driver health.
 Wrote sample driver to publish pages. Mostly Aptio4 compiler won’t support much of the opcodes so we
will develop drivers for opcode support in Aptio5 and load those driver in Aptio4 and check it out.
 Developed drivers to generate variables like Driver#### for driver order support.
 Wrote sample driver to check for driver health.
 Wrote sample driver to publish pages. Mostly Aptio4 compiler won’t support much of the opcodes so we
will develop drivers for opcode support in Aptio5 and load those driver in Aptio4 and check it out.
Declaration
I hereby declare that the above stated information is true and correct to the best of my
Knowledge.

6. Client: AMI India Role: Porting, Bug fixing, Implementation and Unit testing.
Environment : EDKII Duration: July 2010 to June 2013
 Wrote sample driver to check for driver health.
 Wrote sample driver to publish pages. Mostly Aptio4 compiler won’t support much of the opcodes so we
will develop drivers for opcode support in Aptio5 and load those driver in Aptio4 and check it out.
 Developed drivers to generate variables like Driver#### for driver order support.
 Wrote sample driver to check for driver health.
 Wrote sample driver to publish pages. Mostly Aptio4 compiler won’t support much of the opcodes so we
will develop drivers for opcode support in Aptio5 and load those driver in Aptio4 and check it out.
Declaration
I hereby declare that the above stated information is true and correct to the best of my
Knowledge.