SKY9x Ver 3.0

[Scott Page]

Anybody (esp Brent) have an idea why my Ver 3 board sounds have a static at the start and end of them .. same sounds I'm using in the version 2 board with no issues.

[SkyNorth]

Hi Scott , do both rev 3 boards have static?

[nsf]

I have never seen this error ..maybe try a full ERASE with the jumper.. and start new
Other than that , maybe the ATtiny has lost its bootloader. , it would have to be re -programmed with a programmer.

I will try the erase and do fresh install, but if necessary how do I program it?

[SkyNorth]

You need a AVR programmer to re-load the bootloader .

[nsf]

Can you point me to one?
I have this one, I use for my other 9x with the stock board. Will it do?

[Rob Thomson]

Yes!

You may want to start reading here:

viewtopic.php?f=7&t=1938&hilit=coprocessor+flash

[Scott Page]

Hi Scott , do both rev 3 boards have static?

I have not set up the second V3 board. I suppose I could swap it out.

[nsf]

Did a full erase with the jumper, and instaled everything again, but the problem remains. Still nothing in the copro field.
I've been reading the topic Rob recommended but cant find a how to on the bootloader re-load.
Can someone point me a walkthrough and what is neeed to get it done, like software and hardware, besides the avr programer?
One thing though, is this install really necessary? Because the tx seems to be working fine.

[Rob Thomson]

Check this guide:

http://openrcforums.com/wiki/index.php/ ... tion_guide

The software install guide has info on how to flash the co-processor

Rob

[nsf]

Thanks Rob, and maybe I'm misunderstanding something but all this is new to me.
The guide you are referring has, indeed, some info on how to flash the co-processor, and that may be my problem, because I keep getting thiserror.
What I would like to know is how to do this that Brent suggested: "maybe the ATtiny has lost its bootloader. , it would have to be re -programmed with a programmer."
I suppose it's not the same thing...

[SkyNorth]

I have tried to re-create the error you are getting.
Even a blank Attiny , will accept the download , and not generate any error messages.

Can you walk me through the steps you are doing to cause this...
-Brent

[Rob Thomson]

I have tried to re-create the error you are getting.
Even a blank Attiny , will accept the download , and not generate any error messages.

Can you walk me through the steps you are doing to cause this...
-Brent

Think there are two errors being discussed.

1. Error with potential of co-processor not working.

2. Error with static on the speaker.

Rob

[SkyNorth]

As for Static , if it was the board , it should be there all the time , as the audio amp is always on.

[nsf]

I have tried to re-create the error you are getting.
Even a blank Attiny , will accept the download , and not generate any error messages.

Can you walk me through the steps you are doing to cause this...
-Brent

Thanks Brent.
Did a full erase with the jumper, as you suggested.

- Plug the usb and power the radio.
- Open SamBa
- On the flash tab, select "Boot from Flash" anc click execute.
- Then, select the firmware I want to send to the board (open9x), anc click send file
- I then go to the flash tab select "enable co-processor", and I get that error.

[ShowMaster]

This link was dialog I had in August when I was walked through my coprocessor not being programmed. If I'm not off topic here.
SM
viewtopic.php?p=27319#p27319


Sent from my iPod touch using Tapatalk.

[sycons]

Do you close, Samba in between and disconnect the board? You should

Gesendet von meinem Galaxy Nexus mit Tapatalk 2

[nsf]

Do you close, Samba in between and disconnect the board? You should

Gesendet von meinem Galaxy Nexus mit Tapatalk 2

Yes I do.

[nsf]

This link was dialog I had in August when I was walked through my coprocessor not being programmed. If I'm not off topic here.
SM
viewtopic.php?p=27319#p27319


Sent from my iPod touch using Tapatalk.

What was the problem and how did you solve it?
Don't know if what I'm about to say is correct, because don't know much about it bu it seems that I can't enable the co-processor because I get an error every time. So I don't know if it's being programmed.
I will try to post a video of the process.

[ShowMaster]

I think it's all explained in all the posts there at the end.
I did make a word file of what I did just for my notes. I'll look for it when I get home later.
SM


Sent from my iPod touch using Tapatalk.

[kaos]

Here is what works for V.B board. I think it also applies to V3 board too. You follow every step to the T , every file needs to be at the right place. this doc includes the flashing of the FW 1st time and coprocessor app.

[nsf]

Thanks guys.
Kaos, sorry for this question, but I dont want to make any mistakes.
the fisrt thing in the document you posted says "you will need to update your SAM-BA, co-processor applet". Can you point me to the directory were to instal the file?

[kaos]

that is at the bottom half of the doc, where it says:

"2. Copy the new version of the applet to the appropriate SAM-BA directory ( ???\ATMEL\sam-ba_2.11\tcl_lib\at91sam3s4-9x). You may wish to keep the existing version somewhere safe in case it is needed."

[nsf]

Thanks Kaos. Saw that later.
I think the problem is solved, at least I hope so. The copro field now shows number 5??? Or should be 4. And the clock seems to be working fine. It was the RTC battery that was causing the issue. Dont know why or if it's normal, but after removing the backup battery had no errors with samba when enabling co-processor in the flash tab.

Is it ok now?

[MikeB]

Version 5 is the most recent version of the co-processor, released after Brrent issued the Version 3 board.
The value of three pins of the tiny's connector are returned with all the other data, Port B bits 1,3 and 7. These are programmed to be inputs with a pullup resistor.

Mike.

[nsf]

Version 5 is the most recent version of the co-processor, released after Brrent issued the Version 3 board.

Mike.

Then its ok? Is everything as it should now?

The value of three pins of the tiny's connector are returned with all the other data, Port B bits 1,3 and 7. These are programmed to be inputs with a pullup resistor.

Mike.

Sorry Mike, can you translate this please?

[MikeB]

The main ARM processor obtains data from the co-processor. This data includes the RTC, and in version 5 of the co-processor code, it also includes the state of three of the pins of the co-processor that are connected to the header. At present, the main processor does not make use of this data, but, for example, 3 extra switches could be connected to the 3 pins, then the main processor could use them as extra inputs.
It is a work in progress really, so I can test the operation from pins on the header, through the co-processor to the main processor.

Mike.

[nsf]

Thanks mike. So no problem in having version 5 of the co-processor right?

[GTiDon]

My external frsky module arrived. If I want to keep the internal diy module in to use 16 channels. Which ppm connection should I move it to?

And will it be ok to add a switch to the power connector to the internal module if I want to turn it off?

Sent from my LT18i using Tapatalk 2

[Rob Thomson]

Internal would simply be hooked up to your trainer port

[bruce70]

I have the Open9x from a few weeks ago loaded in my revision 3 board, and noticed that level 1855 is now available. When I tried to burn the new version the read of the eeprom gets an error from SAM-BA after showing 98% complete. I am using SAM-BA 2.11 under Ubuntu 12.04 Linux. I have not seen this problem before. The last part of the SAM-BA window in Companion9x shows the following:

-I- Complete 98%
-I- Reading: 0x2000 bytes at 0x7E000 (buffer addr : 0x20002628)

=================================================================================
SAM-BA done with errors
=================================================================================


I had connected the transmitter to the usb port with the power off, then turned it on. The screen displays "USB".

I did find that I could read the firmware from the transmitter without errors, so I took the risk of downloading the current version (1855), and this seems to have worked fine. Since SAM-BA is unable to read the eeprom data, I have backed it up to the SD card.

Any ideas?

Bruce