How can I find .bin file in VidualDSP++ ?
I built .ldr file, but I need .bin
The file is not an Intel Hex-32 file, so that output format from our elfloader would not match the content of this existing file either. I do feel that the help I can offer is now extremely limited. It appears that the expected file format for the programming tool you use does not directly match the format produced by our elfloader.
The content of your attachment is definitely a binary format of some sort, but it simply doesn't match what our tools produce. Again, I would recommend your next step is to consult with the Flash Center documentation/support team to determine exactly what format is expected, then work from there on converting our output to the expected format.
What do you need a .bin file for? You can select the LDR format to be binary in either the loader page GUI (click the binary radio box instead of the defaulted hex box) or by using the -f binary command line switch. If that is not what you are after, you can also dump memory from the IDDE to a text file in binary format.
I use Flash Center to program the RAM, it seems this programmer only works with .bin files. I need .bin file to program my external RAM (This external RAM is connected to my Blackfin BF527).
The "bin" simply tells us the extension that Flash Center expects of the files - what actual format must the data take? The Elfloader utility - which generates the Loader Files from a DXE - can produce "Binary", "Intel Hex-32", "ASCII", "Include", "Motorola-S1/2/3" format files - all with the *.ldr extension.
Though the extension is the same for each of these file types, the content is very different due to the differences in formatting. If your chosen utility is expecting a Binary stream, as the *.bin extension would suggest, simply choose the "Binary" format for elfloader (either through the project options or, as Joe says above, the "-f" switch), then rename the resulting *.ldr file to *.bin.
Without knowing that actual formatting expectations/requirements of the Flash Center utility, we may not be able to offer much further advice. I should say that that output file formats are documented in the Loader and Utilities manual, and they are ultimately pretty straight forward formatting - it would be relatively simple to create a simple conversion utility to parse our LDR files into whatever formatting the selected programming utility expects.
I know there is a *.bin file as a sample program and I programmed my Blackfin with that.
This programmer, is used to program a serial flash RAM (Atmel AT45DB161D) and the flash programs the Blackfin.
Can you share this example Bin file? I can take a look at its contents, and determine which of our file formats [most closely] matches the expected format.
You can attach files to your reply on the EngineerZone by clicking the 'Use advanced editor' option in the top-right of the reply window.
I can not attach the file, it is a secret IP code; but I attached the first few line.
I hope you can figure out from it.
While the contents of that file are binary, they unfortunately do not match our Binary format. You will need to reference the documentation for this Flash Center application (and/or contact their support channels) to get details of the expected format.
You can then cross-reference that with the format of our boot streams (e.g. for the BF52x see the documentation at "ADSP-BF52x Blackfin® Processor Hardware Reference > 17 System Reset and Booting > Basic Booting Process > Block Headers").
For what it's worth, it looks pretty similar, but there are some values that are irreconcilable with the expected contents. For example, the first 16bytes of your file (which we would expect to hold the Block Header for the first block) are:
01 50 08 AD 20 20 A0 FF 20 20 20 20 84 2F 20 20
Which we would expect to be the Block Code, Target Address, Byte Count and Argument. The Byte Count immediately jumps out at me - 0x20202020 is 538,976,288 bytes. Obviously that is a fairly ridiculous value as it suggests the first block of the boot stream alone has 514Mbytes of data. Actually, we typically expect the first block to have a byte count of zero...
That's where your binary file is interesting. In this Block, substituting the 0x20 for 0x00, it starts to make a lot more sense:
Block Code: 0xAD085001
Target Address: 0xFFA00000
Byte Count: 0x00000000
All of this data would then make sense for the XOR checksum value (0x08 - extracted from the Block Code of 0xAD085001).
I don't know why your Bin file has 0x20 where the data should be 0x00, but hopefully the documentation for your programmer makes that a little clearer (and perhaps the solution is a simple as using a hex editor to view the Binary Format LDR file generated by our elfloader and doing a find::replace to replace all 0x00 with 0x20?).
Sorry we cannot be of more assistance, but hopefully this helps you on your way.
I think you are right, the programmer I have reads .hex files, but the extension of this file is .bin. I think it was just for confusing. if it is a hex file (which I think it must be) then what would be the story?
I also have this problem,My boss would not afford a emulator to ADSP-21469 kit LITE.I also need a .bin file,but I do not know how to transfer the .ldr,anyone has a tool,plz help me.
Retrieving data ...