A5.1 and AS6 Failed to launch program UC3C-EK CAN sample 2

Go To Last Post
11 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

UC3C-EK
CAN Software Stack Example 2 - UC3C-EK

Unmodified source, works fine in AS5

Unmodified source, Fails in AS5.1 and AS6

ATMEL STUDIO 6
ASF Version 3.0.1
UC3C-EK
CAN Software Stack Example 2 - UC3C-EK

Failed to launch program:Region to be programmed lies outside flash address space.

Output General
# ProcessesService::launch() failed: Region to be programmed lies outside flash address space.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I can confirm this. Please tell me if you got a solution.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The difference between the two CAN Examples is taht in Example 2 "volatile can_msg_t mob_ram_ch0[NB_MOB_CHANNEL]" is declared with the attribute "((section (".hsb_ram_loc")));".
If you remove the attribute it works.

BUT! It should work! The address 0xA0000000 for HSB is correct! And I don't want to accept that it was possible with AVR-Studio < 5.1 though the Hardware didn't change.

What's wrong here? Why is the access to this valueable memory-section broken?

(it even doesn't work if you import the can stack from the asf into a custom project)

I can't even see a reasonable difference in the memory-section in the "old" and "new" version of the linker-sripts:

new:

MEMORY
{
  FLASH (rxai!w) : ORIGIN = 0x80000000, LENGTH = 0x00080000
  INTRAM (wxa!ri) : ORIGIN = 0x00000004, LENGTH = 0x0000FFFC
  HRAM0 (wxa!ri) : ORIGIN = 0xA0000000, LENGTH = 0x00001000
  USERPAGE_RESERVED (r) : ORIGIN = 0x80800000, LENGTH = 0x00000004
  USERPAGE : ORIGIN = 0x80800004, LENGTH = 0x000001FC
}

old:

MEMORY
{
  FLASH (rxai!w) : ORIGIN = 0x80000000, LENGTH = 0x00080000
  INTRAM (wxa!ri) : ORIGIN = 0x00000004, LENGTH = 0x0000FFFC
  HRAM0 (wxa!ri) : ORIGIN = 0xA0000000, LENGTH = 0x00001000
  USERPAGE : ORIGIN = 0x80800000, LENGTH = 0x00000200
}
Last Edited: Fri. Apr 13, 2012 - 10:33 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

jabba80 wrote:
The difference between the two CAN Examples is taht in Example 2 "volatile can_msg_t mob_ram_ch0[NB_MOB_CHANNEL]" is declared with the attribute "((section (".hsb_ram_loc")));".
If you remove the attribute it works.

BUT! It should work! The address 0xA0000000 for HSB is correct! And I don't want to accept that it was possible with AVR-Studio < 5.1 though the Hardware didn't change.

What's wrong here? Why is the access to this valueable memory-section broken?

(it even doesn't work if you import the can stack from the asf into a custom project)


I can absolutely assure you it does work without any modifification in AS5, but not in 5.1 or 6, 5 reports no errors during build loads and runs.

It fails build in AVR32 Studio with an error pointing to an LL constant but there is nothing wrong with the constant declaration.

Thanks, I will try that, fingers crossed.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

please keep me up-to-date, if you discover a way to use the hsb-memory...

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

jabba80 wrote:
please keep me up-to-date, if you discover a way to use the hsb-memory...

Don't worry, Atmel Engineers monitor this forum 24/7 to help us solve all these Atmel Studio problems, they must be busy right now and will soon respond, honest.

NOTE:
My response above is SARCASM however I welcome being proven wrong.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have logged a bug for this issue in our internal server. AVRSV-3273 is the bug id for your reference!

Regards,
Deena

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

change ".hsb_ram_loc" to ".data_hram0"

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

darkdragon wrote:
change ".hsb_ram_loc" to ".data_hram0"

That works, Thank You.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

jabram wrote:
jabba80 wrote:
please keep me up-to-date, if you discover a way to use the hsb-memory...

Don't worry, Atmel Engineers monitor this forum 24/7 to help us solve all these Atmel Studio problems, they must be busy right now and will soon respond, honest.

NOTE:
My response above is SARCASM however I welcome being proven wrong.


OK, OK, I must admit I have been proven WRONG which is welcome.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

jabram wrote:
jabram wrote:
jabba80 wrote:
please keep me up-to-date, if you discover a way to use the hsb-memory...

Don't worry, Atmel Engineers monitor this forum 24/7 to help us solve all these Atmel Studio problems, they must be busy right now and will soon respond, honest.

NOTE:
My response above is SARCASM however I welcome being proven wrong.


OK, OK, I must admit I have been proven WRONG which is welcome.

Sadly, I was wrong! I was correct in the first instance.