search

energia / Energia

Fork of Arduino for the Texas Instruments LaunchPad's
http://energia.nu
Other
794 stars 672 forks source link

Release 12 does not change FPU define switch board types #469

Closed RobertCarlRice closed 9 years ago

RobertCarlRice commented 10 years ago

Changing the board type selection from EX-TM4C1294XL to the EX-TM4C123GXL the FPU clock speed define remains set at 120 Mhz. I can work around this minor bug by requesting a serial baud rate 50% higher than what I want for the EX-TM4C123GXL.

spirilis commented 10 years ago

Is this still a problem with release 13?

spirilis commented 10 years ago

Fwiw, doing a quick sketch with board selected as TM4C1294, I see -DF_CPU=120000000L, then selecting TM4C123G ... I see -DF_CPU=80000000L.

RobertCarlRice commented 10 years ago

Hi Eric,

I wasn’t aware of DF_CPU, I see that HardwareSerial uses F_CPU which is what I intended to reference in the bug report. I haven’t tried this yet in Release 13.

Thanks, Bob Rice

On Sep 15, 2014, at 10:15 PM, Eric notifications@github.com wrote:

Fwiw, doing a quick sketch with board selected as TM4C1294, I see -DF_CPU=120000000L, then selecting TM4C123G ... I see -DF_CPU=80000000L.

— Reply to this email directly or view it on GitHub https://github.com/energia/Energia/issues/469#issuecomment-55686477.

robertinant commented 10 years ago

-DF_CPU is a GCC command line define which is then picked up in the various parts of the Energia framework. I did a quick check on both version 12 and 13 and in both cases see that the proper -DF_CPU is passed to the command line during compilation. Can you reproduce this with the ASCIITable example Sketch? I do not have these board with me right now but if you can confirm that ASCIITable shows the issue then I will do an attempt to reproduce the issue tomorrow.

RobertCarlRice commented 10 years ago

I can verify that the DF_CPU argument does change to 80000000L when I switch boards. But I still have to request a baud rate of 172800 to get 115200 from HardwareSerial.

Thanks, Bob

On Sep 16, 2014, at 1:21 PM, robertinant notifications@github.com wrote:

-DF_CPU is a GCC command line define which is then picked up in the various parts of the Energia framework. I did a quick check on both version 12 and 13 and in both cases see that the proper -DF_CPU is passed to the command line during compilation. Can you reproduce this with the ASCIITable example Sketch? I do not have these board with me right now but if you can confirm that ASCIITable shows the issue then I will do an attempt to reproduce the issue tomorrow.

— Reply to this email directly or view it on GitHub https://github.com/energia/Energia/issues/469#issuecomment-55778766.

robertinant commented 10 years ago

Ok, will try to reproduce..

robertinant commented 10 years ago

Are you using the build in serial monitor or a different terminal?

rei-vilo commented 10 years ago

Has this issue been already fixed in release = release 13 or is release 13 also concerned?

RobertCarlRice commented 10 years ago

I’ve checked the baud rate both with serial monitor and the Mac serial port.

Thanks, Bob

On Sep 16, 2014, at 1:50 PM, robertinant notifications@github.com wrote:

Are you using the build in serial monitor or a different terminal?

— Reply to this email directly or view it on GitHub https://github.com/energia/Energia/issues/469#issuecomment-55783824.

RobertCarlRice commented 10 years ago

I know that this question is somewhat unrelated to Energia but it does relate to the serial comm you may know the answer. I am still a bit fuzzy on how the serial interfaces work so please correct me where I am wrong.

The TI MSP430LPCDC 1.0.3b serial driver extension works reliable but has a annoying problem that it only recognizes a LaunchPad if the USB becomes active sometime following reboot of the Mac OS. If I reboot my system, then I have to disconnect the LaunchPad USB and reconnect it before the driver will create the serial device driver. I know this problem is correctable since the Prolific FTDI serial device driver will create serial devices upon restart.

The microchip flasher utility, AVRdude, uses the serial device driver interface to download the .hex file code and to verify it. However, the TI flashed utility, lm4flash, uses only the USB protocol. It downloads the .bin format file and is much faster but it lacks a verify only option.

However, I would prefer to bypass the TI MSP430LPCDC 1.0.3b serial driver extension entirely and communicate more with the debugger’s virtual serial port using only the USB protocol. This would be faster, eliminate the annoying restart problem, my users would not need to install the driver and my app would not need to request the entitlement to access serial ports.

Do you know if anyone is doing this on the Mac desktop?

Thanks, Bob Rice

On Sep 16, 2014, at 2:11 PM, Rei Vilo notifications@github.com wrote:

Has this issue been already fixed in release = release 13 or is release 13 also concerned?

— Reply to this email directly or view it on GitHub https://github.com/energia/Energia/issues/469#issuecomment-55787451.

robertinant commented 10 years ago

Unfortunately the you need a driver to communicate with the Serial portion of the debugger. There is no other way to get Serial data out of the LaunchPad. Just want to make sue since you mentioned Tiva in the initial issue report, the MSP430LPCDC is only for MSP430. TivaC does not need a driver.

robertinant commented 9 years ago

I have tried on all Operating system but am not able to reproduce with the current git version of Energia. We can reopen if this still remains an issue for you. Closing for now.