Re: [Flashforth-devel] UNO lockup

[Mikael N. <mik...@fl...>]

As the problem occurs even when sufficient boot time is used,
I would still say that your problematic boards have some HW related
problem
that just happens to cause a problem with a particular code layout. 

As there are many boards that do not have a problem, the FF kernel
should be just fine. 

For example the Vcc filtering may be insufficient or some other problem.


The code version that works has the FF kernel code located in the end of
the flash.
The beginning of flash just has the interrupt vector table and then 20
Kbytes of NOP
until the kernel code begins. 

The problematic code has the FF kernel code located in the beginning of
the flash.
There possible erroneous code execution hits the kernel in a different
manner. 

BR Mikael 

On 2022-03-24 13:58, Ed wrote:

> On 2022-03-24 09:05, Mikael Nordman wrote: 
> 
>> 
> 
>> You could comment out the prompt code from QUIT and see if there is a difference. 
> 
> Tried the above edit for FF 2021-11-28 but it made no difference on the problematic 
> 
> 328 SMD boards.  Brownout fuse was set to $FC.  I waited 6 seconds between plugging 
> 
> USB cord in/out so as to not interrupt FF booting up but still it managed to corrupt 
> 
> the flash.  The terminal app was inactive so no KEY input from me. 
> 
>> The avrasm2 ff's  have more of the code in the bootloader section and I there may 
> 
>> be some logical differences also, but I have not checked further. 
> 
> FWIW the first XC8 version (dated 2021-03-29) worked ok on my problematic boards. 
> 
> It was the next release (2021-09-04) where things came unstuck.