MSPM0G3505: MSPM0G3505

renaud KLEIN

Prodigy 50 points

Part Number: MSPM0G3505
Other Parts Discussed in Thread: MSPM0G3507, , SYSCONFIG

Tool/software:

Hello,

I started the development of my product with the MCU MSPM0G3507 as the 3505 was not yet available.

All the code is now working for the MSPM0G3507.

I recently get MSPM0G3505 samples (That should be the final MCU for my product), but it looks that the code is not working on this target.

I have in mind that only the memory size change...But is it possible that there are other differences ? On the pin definition or initialization?

On the non-main memory ?

Thank you for your fast answer

Renaud

over 1 year ago

0 Zoey Wei over 1 year ago

TI__Genius 10611 points

Hi Renaud

renaud KLEIN said:
But is it possible that there are other differences ? On the pin definition or initialization?

Just memory size and pin if package is not same

Just want to make sure

1. Did you use Launchpad or yourself design board?

2. Have migrated your code from G3507 to G 3505

Regards,

Zoey

0 renaud KLEIN over 1 year ago in reply to Zoey Wei

Prodigy 50 points

Hi Zoey,

1. It's our own design already validated with the G3507

2. No. I was hopping that we can use the same hex file. Is there any procedure to migrate the code from G3507 to G3505?

THank you,

0 Zoey Wei over 1 year ago in reply to renaud KLEIN

TI__Genius 10611 points

Hi,

You can use Sysconfig to migrate

Regards,

Zoey

0 renaud KLEIN over 1 year ago in reply to Zoey Wei

Prodigy 50 points

I did that...I rebuild with the G3505 MCU.

But it looks that both output files are exactly the same.

Is this normal ?

0 Zoey Wei over 1 year ago in reply to renaud KLEIN

TI__Genius 10611 points

I think is not normal.

Have you tried to use another one? It may be due to worse soldering

Also, can you share your hardware schematic?

Regards,

Zoey

Arm-based microcontrollers

Arm-based microcontrollers forum

MSPM0G3505: MSPM0G3505