Martin Guy |
On 28 March 2012 08:47, Bogdan Marinescu <[hidden email]> wrote:
> On Wed, Mar 28, 2012 at 8:57 AM, Antti Lukats > <[hidden email]> wrote: >> well, the problem exist, we use generic STM32F4 board with @AT >> and pressing the enter each time after download is true pita > > When we had this kind problem in the past, it was > always a timer issue I've had this problem repeatedly in different circumstances since I started using elua and yes, it was always due to the use of a timer to detect CRLF/LFCR sequences. It also causes other problems, such as timer0 being reset every time a chararacter is read from stdin. There's a commit on the Mizar32 branch to remove the use of a timer in CRLF/LFCR detection while maintaining the same logic https://github.com/elua/elua/commit/a4e720596f526c3679a3323ef2004f19eaa21b91 Antti, you can test whether this is the cause of your problem by applying that to your git tree. It doesn't "git cherry-pick" cleanly any more but should be fairly simple to apply by eye M _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
Martin Guy |
On 28 March 2012 11:00, Martin Guy <[hidden email]> wrote:
> It also causes other problems, such as > timer0 being reset every time a chararacter is read from stdin. Oops, this is no longer true in the master branch as it uses the system timer these days. M _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
In reply to this post by Pito
2012/3/28 pito <[hidden email]>:
> Hi, > pls mind the other goat issue I've indicated as well: > 1. after the start of goat (xp sp3) the cpu (notebook) utilization > goes to 100% This is almost always an indication of a busy waiting loop. Best, Bogdan > 2. it does not matter whether the f4disco is connected or not (or, > whether the bt connection or bt device is started or not) > 3. when running elua via teraterm and bt the cpu utilisation is ~4% > when at elua prompt and 18% when communicating 115k heavily.. > p. > > -- > - - Reklama - - - - - - - - - - - - - - > Autonehoda v opilosti, trestní stíhání, odposlechy, lobbing, > zákulisní praktiky... Vše o kauze podnikatele Romana Janouška, > přítele bývalého pražského primátora a poslance Pavla Béma čtěte na > http://bit.ly/HaNXoc > > _______________________________________________ > 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 |
Nuccio Raciti |
In reply to this post by Pito
Il 28/03/2012 10:29, pito ha scritto:
> Hi, > pls mind the other goat issue I've indicated as well: > 1. after the start of goat (xp sp3) the cpu (notebook) utilization > goes to 100% > 2. it does not matter whether the f4disco is connected or not (or, > whether the bt connection or bt device is started or not) > 3. when running elua via teraterm and bt the cpu utilisation is ~4% > when at elua prompt and 18% when communicating 115k heavily.. > p. > > I need to investigate.. Cheers, N _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
Antti Lukats |
In reply to this post by BogdanM
Hi
yes its me.. i guess GO@ is not at all on my priority list, not yet, i did think the need for press enter was design decision then realized its bug, we can sure test something if needed on our stm32f4 gear, but i think, eh i better not think, it can be either way, the char was not sent, or not received.. either way it should be possible to get to the issue for this we are much interested in eLua USB support for stm32f4, living in the hope it comes Antti On Wed, Mar 28, 2012 at 9:47 AM, Bogdan Marinescu <[hidden email]> wrote: > Hi Antti, > > On Wed, Mar 28, 2012 at 8:57 AM, Antti Lukats > <[hidden email]> wrote: >> well, the problem exist, we use generic STM32F4 board with @AT >> and pressing the enter each time after download is true pita > > I'm sure the problem exists, I'm not denying that. What I don't get is > what could have happened in eLua itself that made this problem appear > in the first place. When we had this kind problem in the past, it was > always a timer issue (unfortunately I can't test this yet (but I'll be > able to do this after this crazy week ends here)). This is a bit weird > though, I thought that timers on STM32F4 are working fine. Can someone > please check the system timer on the F4? Maybe it's not implemented > properly. > > Best, > Bogdan > > PS. Slightly OT, are you the same Antti Lukats that wrote (or ported, > my memory is a bit fuzzy) a tokenized BASIC interpreter to 8-bit > micros a while ago? > >> >> Antti >> >> On Tue, Mar 27, 2012 at 9:38 PM, Bogdan Marinescu >> <[hidden email]> wrote: >>> On Tue, Mar 27, 2012 at 8:34 PM, Nuccio Raciti <[hidden email]> wrote: >>>> So probably the STM32F4Discovery eLua needs the "\r\n", >>> >>> That really shouldn't depend on the board. eLua has a mechanism that >>> accepts all kinds of newline terminators, so it's unlikely that the >>> problem is with this specific board. >>> >>> Best, >>> Bogdan >>> >>>> unfortunately I have not yet had time to try it, >>>> I did my work on a avr32 board... >>>> >>>> I will check. >>>> >>>> >>>> Il 27/03/2012 01:58, Pedro ha scritto: >>>> >>>>>>>>> Probably some piece of the "bt" stack removes the >>>>>>>>> "\n" character.... >>>>>>>> >>>>>>>> BT works fine with all my dev systems.. :) >>>>>>> >>>>>>> I'm having the same problem, and I'm not using bt. >>>>>>> >>>>>>> Pressing enter on the Goat terminal windows won't work either. Adding >>>>>>> a '\r' before the '\n' on line 17 of "send_and_run.lua" seems to solve >>>>>>> the issue, but I'm not sure whether this is a valid solution. >>>>>> >>>>>> Yes, it is a good solution on Windows systems, >>>>>> I will fix it for the next release >>>>>> thanks for the suggestion, >>>>> >>>>> I forgot to mention that I'm on a GNU/Linux system. >>>>> >>>>>> Cheers, >>>>>> Nuccio. >>>>> >>>>> Pedro. >>>>> _______________________________________________ >>>>> 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 >>> _______________________________________________ >>> 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 > _______________________________________________ > 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 |
Free forum by Nabble | Edit this page |