disp module revision

[Dado Sutter]

Do you mean, we can only change them on LM boards if we cut those tiny "fuses" ?

Best
Dado

On Thu, Mar 26, 2009 at 07:28, Bogdan Marinescu <[hidden email]> wrote:

On Thu, Mar 26, 2009 at 4:42 AM, Jesus Alvarez <[hidden email]> wrote:

In the default configuration, four GPIO pins of the LM3S MCUs are used for
JTAG. The eLua GPIO APIs do not appear to provide a method for switching
pins from JTAG to GPIO.

This will happen when the lm3s.gpio module is implemented, and it will have a method for this. I managed to completely kill an older (8-bit) Luminary devboard by switching the JTAG pins to GPIO though :) Hope this changed in their newer CPUs.
 
Best,
Bogdan

_______________________________________________
Elua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

_______________________________________________
Elua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

[Jesus Alvarez]

> This will happen when the lm3s.gpio module is implemented, and it
> will have a method for this.

Good. This should be available to eLua applications that reach
a production stage.

> I managed to completely kill an older (8-bit) Luminary devboard
> by switching the JTAG pins to GPIO though :) Hope this changed
> in their newer CPUs.

You can still "brick" older Luminary parts by switching those
pins to GPIO and downloading firmware with a bug. I believe this
is mostly the 28-pin parts (all are 32-bit) but there may be some
in other packages. LMI implemented a fix in rev C of the silicon
for some (not all) the pins.

Later families of the Luminary MCUs (Fury, DustDevil and Tempest)
can be "unbricked" with a utility in the LMI Flash Programmer
programmer. That covers the 3 LMI MCUs supported by eLua.

Luminary marketing folks emphasize their lack of pin function
multiplexing as one of their competitive advantages against
other MCU makers. The engineer that multiplexed the JTAG signals
with 4 GPIO pins apparently was not aware of this. In my opinion,
JTAG signals should not be multiplexed as is the case with most
other MCUs based on the ARM. Even applications that appear to be
bug free may need to be debugged later on with a JTAG.

Regards,
Jesus Alvarez


_______________________________________________
Elua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

[mpthompson]

Dado Sutter wrote:
 > Oh, that may be good news :)
 > Can't wait to get back to Rio and try again with the new code.
 > Did anybody else make it run on an EK-LM3S8962 board ?
 >
 > Best
 > Dado

I took the fatfs code out of the eagle_mmc branch over to my local copy
of eLua 0.5 and integrated it with the AT91SAM7S platform that I'm
working on.  After debugging a data alignment exception it seems to pass
the smoke test and run 'hello.lua' and 'bisect.lua' as shown below from
an sd/mmc card formatted with FAT16.  To get the FatFS working I needed
to implement a periodic interval timer in 'platform.c' and port a fairly
close 'mmc.c' file from the following project:

http://www.siwawi.arubi.uni-kl.de/avr_projects/arm_projects/efsl_arm/index.html

Are there plans to merge the fatfs code from the eagle_mmc branch into
the trunk anytime soon?  I would like to add the support for the
AT91SAM7S chips once the branch is merged.

Mike

--------------------
eLua# ver
eLua version 0.5
For more information go to http://elua.berlios.de
eLua# lua /mmc/hello.lua
Press CTRL+Z to exit Lua
Hello, World!
eLua# lua /mmc/bisect.lua
Press CTRL+Z to exit Lua
0 c=1.5 a=1 b=2
1 c=1.25 a=1 b=1.5
2 c=1.375 a=1.25 b=1.5
3 c=1.3125 a=1.25 b=1.375
4 c=1.34375 a=1.3125 b=1.375
5 c=1.328125 a=1.3125 b=1.34375
6 c=1.3203125 a=1.3125 b=1.328125
7 c=1.32421875 a=1.3203125 b=1.328125
8 c=1.326171875 a=1.32421875 b=1.328125
9 c=1.3251953125 a=1.32421875 b=1.326171875
10 c=1.32470703125 a=1.32421875 b=1.3251953125
11 c=1.324951171875 a=1.32470703125 b=1.3251953125
12 c=1.3248291015625 a=1.32470703125 b=1.324951171875
13 c=1.3247680664062 a=1.32470703125 b=1.3248291015625
14 c=1.3247375488281 a=1.32470703125 b=1.3247680664062
15 c=1.3247222900391 a=1.32470703125 b=1.3247375488281
16 c=1.3247146606445 a=1.32470703125 b=1.3247222900391
17 c=1.3247184753418 a=1.3247146606445 b=1.3247222900391
18 c=1.3247165679932 a=1.3247146606445 b=1.3247184753418
19 c=1.3247175216675 a=1.3247165679932 b=1.3247184753418
20 c=1.3247179985046 a=1.3247175216675 b=1.3247184753418
after 20 steps, root is 1.3247179985046387 with error 9.5e-07, f=1.8e-7
--------------------


_______________________________________________
Elua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev