Topic : How to avoid doing a Ctrl+D to download in RLink

Forum : ARM

Original Post
Post Information Post
June 28, 2011 - 11:43am
Guest

In our project, We are facing problem to download hex file directly in STR9 bank 1 ,production because we cannot give the source code in RIDE7 to them and ask to do a Ctrl+D .

Till now I used to follow the steps below

In RLink configuration I tick both secondary box and configuration bit box and make an erase. I select the hex file and then go to debug mode by pressing Ctrl+D. I believe that this step is very critical for me to set the configuration sector

Any suggestion to set the configuration register and avoid doing a Ctrl+D to download hex file in bank1?

Presently I am using the RIDE 7 and RLink tools only.

Thanks,
Replies
Post Information Post
+1
0
-1
June 28, 2011 - 11:54am
Raisonance Support Team

Hi,

For downloading without debugging (production) we suggest you use the production tools RFlasher (GUI) or STR9_pgm (command-line) rather than Ride which is designed for debugging, not production.

RFlasher is documented in its own GettingStarted, in \doc

STR9_pgm includes its own documentation. call it in a DOS prompt without argument and it will display its doc.
This forum also includes some questions about using it from other customers, and the associated answers from us.

In your situation I recommend RFlasher because STR9_pgm requires osf files that are generated by a software from ST that is obsolete.

Note that you could also use Ride for programming a hex file, but the procedure with RFlasher is much simpler, faster and safer.

Best Regards,

Vincent
+1
0
-1
June 28, 2011 - 2:06pm
Guest

Hi,
Thanks for the reply. I tried to use the Rflasher7 to put my Bootloader in Bank 1 and Application in Bank 0 . I selected in Advanced ARM options that my boot bank will be bank0@0x00 and highest bank address 200000. I selected device STR912FW46 . I select the Program Configuration in STR9 specific options bits while I am selecting Program Secondary flash box . Still I am unable to get success.

As you suggested to use the RFlasher7 for production is really good .

My requirement is that I should be able to put Bootloader in bank1 and my application in Bank 0 using Rflasher7 . Should I do any configuration in Rflasher apart from above things?

Can you please help.

Thanks
+1
0
-1
June 28, 2011 - 3:16pm
Raisonance Support Team

Hi,

For this you must make a single hex file that contains both the bootloader and the application at their respective addresses. (0 and 200000)

It's quite easy to do if you know how hex files are written. One other way of making this file is to program the same way as you did during development (using Ride) and then read-back from the device to a file using RFlasher. Or rather STR9_pgm, which will output an osf file that can contain all the necessary data: bank0 + bank1 + configuration. And then you can use STR9_pgm in an automatized production process.

I hope it helps.

Vincent
+1
0
-1
June 29, 2011 - 8:01am
Guest

Hi,
Thank you very much for the suggestions to tackle this problem.

If I try the first option of making a single hex file for both
Bootloader and the application, using RFlasher7 , can I manually merge 2 hex files in STR9 specific options do I put it in both primary as well as secondary ?I mean, how to select primary and secondary flash bank and configuration CSx , is it the same way we do or any other additional settings?

Can I provide the production with this Rflasher prj file with a single hex fiel as above
please help.

Thanks,
+1
0
-1
June 29, 2011 - 9:41am
Raisonance Support Team

Hi,

If you use hex files, the data should be placed at the address where the CPU sees it, which depends on the configuration and project options. In your case, bank 0 is at address 0 and bank 1 is at address 200000. In hex files you cannot include the data for the configration, so this has to be stored in a RFlasher project. (.rprj)
Then indeed you will provide to your production team a set of two to four files:
1. file with data to program (.hex)
2. RFlasher project file (.rprj)
And maybe, depending on your settings:
3. RFlasher application file (.rapp)
3. RFlasher debug information file (.rapp)

If you use osf files, which is a STR9-specific format, the banks and the configuration can be included in a single file and they are directly referenced. (meaning the address is not what tells the destination region of the data. there are special constructs for that) For generating osf files, always use a software like CAPS or STR9_pgm.

Then you will provide to your production team a set of two files:
1. file with data to program (.osf)
2. script file with STR9_pgm command line (.bat or .pl or .js or ...)

I hope it helps.

Vincent