Moderators: Mathias, Mug UK, moondog/.tSCc., [ProToS], Galvez, Moderator Team
vido wrote:Hey,
did you try also any other CF?
Did you try and other NVRAM settings?
Are you using n.AES?
vido wrote:Ok. Then n.AES is not the problem. Reflashin FireTOS is good idea. And if it wont help also mybe reflashing BAS. But you have to be carefull with that. At least I had big problems with that.
vido wrote:Ok. Then n.AES is not the problem. Reflashin FireTOS is good idea. And if it wont help also mybe reflashing BAS. But you have to be carefull with that. At least I had big problems with that.
SweYC wrote:As nothing really helped, on end i reflashed BAS as well, version from firebee.org 0.9.3... It fixed things permanently... no reset, boot or any problems at all... As it wont boot anymore. I was carefull, as u can be with flash tool. Press ok an pray
Janez
mfro wrote:SweYC wrote:As nothing really helped, on end i reflashed BAS as well, version from firebee.org 0.9.3... It fixed things permanently... no reset, boot or any problems at all... As it wont boot anymore. I was carefull, as u can be with flash tool. Press ok an pray
Janez
If you have problems with FireTOS, it usually doesn't help to flash a newer BaS(_gcc). You just run the risk of bricking your machine if something goes wrong during the flash process.
First aid is to connect a terminal to your serial port and post the output. BaS_gcc spits out lots of diagnostic messages there during boot up. Please post them, they may help to identify the problem.
Please realize that BaS is the very first code that runs when you switch on the machine. If you manage to break it somehow, chances are it won't boot anymore. Your last option would then be a BDM cable (hard to get by these days, unfortunately) which allows direct flashing from another machine.
vido wrote:I have TBLCF now and I will lend it to Swe. I just never used it till now. We will have to figure out how
Users browsing this forum: No registered users and 1 guest