RE: how to keep some basic relocation information in executable binary
"Peiyu Li" <[email protected]>
| Newsgroups | gmane.linux.ports.arm.general |
|---|---|
| Message-ID | <ED2979D1CA1B3E4BB166ED99900885223662E4@SJOAMSEXB01.AMERICAS.ROOT.PRI> |
Hi Jamie, I just have a look at bFLT format, it is what I want: relocatable and simple. Many thanks! I will try it later soon. Peiyu -----Original Message----- From: Jamie Lokier [mailto:[email protected]] Sent: Friday, October 09, 2009 7:51 PM To: Peiyu Li Cc: [email protected] Subject: Re: how to keep some basic relocation information in executable binary Peiyu Li wrote: > I am trying to find a way to build out one ARM-instruction binary that > can run at any address in the bare metal environment. You might have luck looking at the uClinux bFLT ("flat") format. To make a bFLT file, the tools first produce an ELF executable with relocations, and then convert the executable to bFLT format. bFLT is the same as what you get with objcopy to binary format, with compact relocations stuck on the end. You can either make a normal bFLT which has relocations throughout the text and data areas, or a bFLT-XIP which concentrates them in the GOT and can be run from ROM as well as anywhere in RAM. If you don't want to use the bFLT format, you could still look at how the tools produce the ELF executable with relocations and then convert it. -- Jamie To report this email as spam click https://www.mailcontrol.com/sr/wQw0zmjPoHdJTZGyOCrrhg== b6JUKVCjGaM0hoQFif+O!D6Uz4murBbVL0sWPB8dn7asg== . Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom