topic Re: Why ROM_LIB haven't linked or burned into .s19 file? in CodeWarrior Development Tools

Why ROM_LIB haven't linked or burned into .s19 file?

pamis — Wed, 27 Jul 2016 05:43:22 GMT

I'm working with bootloader, because of runtime library instead(eg. switch case, byte shift finally translate into _CASE_CHECKED_CODE, _BSHL...). I must separate APP and bootloader with rom library(normal library can't allocate address). Now, i create a bootloader rom library and link with app code, but there is no data in .s19 file..., help! Help! HELP!!!

snippet from project.map file:

*********************************************************************************************

SECTION-ALLOCATION SECTION

Section Name Size Type From To Segment

---------------------------------------------------------------------------------------------

.init 49 R 0xC000 0xC030 ROM_C000

.startData 10 R 0xC031 0xC03A ROM_C000

.text 24 R 0xC03B 0xC052 ROM_C000

.copy 2 R 0xC053 0xC054 ROM_C000

.stack 256 R/W 0x3800 0x38FF RAM

...

Summary of section sizes per section type:

READ_ONLY (R): 57 (dec: 87)

READ_WRITE (R/W): 100 (dec: 256)

NO_INIT (N/I): DE (dec: 222)

*********************************************************************************************

VECTOR-ALLOCATION SECTION

Address InitValue InitFunction

---------------------------------------------------------------------------------------------

0xFFFE 0xC029 _Startup

*********************************************************************************************

OBJECT-ALLOCATION SECTION

Name Module Addr hSize dSize Ref Section RLIB

---------------------------------------------------------------------------------------------

MODULE: -- rom.lib --

- PROCEDURES:

UpdateEvent_AppPFlash F577 46B 1131 1 @

MakeCrc_Tbl FA73 45 69 1 @

CalcCrc_u16_Val FAB8 32 50 0 @

- VARIABLES:

Thanks and regards

Re: Why ROM_LIB haven't linked or burned into .s19 file?

pamis — Wed, 27 Jul 2016 06:51:47 GMT

Upload my test project !

Re: Why ROM_LIB haven't linked or burned into .s19 file?

ZhangJennie — Thu, 28 Jul 2016 06:37:42 GMT

To create .lib file, you need follow the steps below.(please also refer the attached mylib project)

Create one project with wizard.(I use NE64 as target chip)
change the file name main.c as the lib name (in sample is mylib.c)
define the lib functions in mylib.c
add header file mylib.h in the project, and declare the prototype of the lib functions in it.
add “#include mylib.h” in mylib.c
delete the following files from the project: start12.c, datepage.c, *.prm, MC9S12NE64.h, MC9S12NE64.c, ansibi.lib.c
Press ALT+F7, in “Target Setting”, select “Libmaker for HC12” as Linker in the second droplist. In “Libmaker for HC12”, name your Library Filename.(the sample use mylib.lib), Click OK to close this window.
Compile again. In “bin” folder of the lib project, you could find the lib file named “mylib.lib”

import “mylib.lib” and “mylib.h” in your current project

add “#include "mylib.h"”in the main.c file

then you can use the lib functions in your current project code.

please refer this to create your lib file. Hope this helps.

Have a great day,
Jennie Zhang

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: Why ROM_LIB haven't linked or burned into .s19 file?

pamis — Sun, 31 Jul 2016 23:54:15 GMT

Thank you for your reply.

I used normal library instead of ROM library.

Thanks and regards

Re: Why ROM_LIB haven't linked or burned into .s19 file?

ZhangJennie — Mon, 01 Aug 2016 07:16:28 GMT

You are welcome!

Best Regards,

Jennie