• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 21 subscribers
  • Views 776 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

INIT.A51 on 80c390?

Kevin Radke

Is it required to include init.a51 to initialize global variables in the 22bit contiguous mode on an 80c390?

If I try and do this, I get a lot of undefined symbols:

assembling INIT.A51...
INIT.A51(59): error A45: UNDEFINED SYMBOL
INIT.A51(65): error A45: UNDEFINED SYMBOL
INIT.A51(88): error A45: UNDEFINED SYMBOL

...

My search of the list and knowledgebase didn't turn up anything specific to the 390.

It looks like the assembler is case sensitive, since I noticed I can fix most of the problems if I correct the case. I took the INIT.A51 file from the v6.22 install directory...

Parents
  • 0 in reply to Jon Ward

    I'm including it because I wasn't seeing global variables initialized correctly.

    It works fine once I fix the label name case differences and include the register definitions header file.

    All I did was add it to an existing project. Is the extended linker case sensitive by default, while the old one wasn't?

Reply
  • 0 in reply to Jon Ward

    I'm including it because I wasn't seeing global variables initialized correctly.

    It works fine once I fix the label name case differences and include the register definitions header file.

    All I did was add it to an existing project. Is the extended linker case sensitive by default, while the old one wasn't?

Children
No data