openrcforums

Both! The timing is still there, but only runs if you have the 4K7 pulldown on the signal.

Mike.

Edit: Minor timing improvement, hex file above reposted.

Looking OK generally. I'll do some more testing, but I have updated the hex file in the post above (I don't like leaving incorrect files on posts). This one should work.
I had the code a bit wrong, and also changed the clock in the wrong direction!.

Mike.

OK, I'm checking. I can see an error in my clock adjust code. I'm using clock/8 as the clock for timer 1, and have calculated from this as 1.2uS per count. It's not, it 1.2MHz, 0.833uS per count.

Mike.

Edit: This may affect other timings, testing now.

OK, the processor clock is too slow. Each (-ve) pulse on the debug signal should be the centre of a bit, the last falling edge should be the centre of the stop bit. The first byte is 0x7E. In your picture, the last data sample is of the stop bit, and the stop bit edge is just into the next start bit...

I'll do something this afternoon, I've been sidetracked this morning.

Mike.

That should all be OK, it's pretty much what I've been doing, except I'm using a STK500 (set to 3.3V) as the programmer. You will need to set the fuses as well, info just a few post back.

Mike.

On occasions I've noticed slightly odd menu displays when changing menus. You seem to get some of each menu displaying at the same time. Also, the STAT display of tmain is sometimes over 20mS, this is rather long. I think the problem is caused by things like chainMenu(). What happens is the 'current...

All it is saying is change all lines like:
PROGMEM char usbDescriptorString0[] = { /* language descriptor */
to:
const PROGMEM char usbDescriptorString0[] = { /* language descriptor */

Mike.

What errors are you getting?

Mike.

What is the screen resolution?

Mike.

Just tried with the throttle up, still seems OK. Are you using eepe to flash the Tx with? You need to run eepe, then in the burn menu, select "Read EEPROM to file". Then, just use the Full Editor and use the "Upload Attachement" to include the file. You may need to rename the fil...

Can you post your EEPROM image please? I know there have been problems to do with a change regarding how the stick mode is done. I don't fly helis so I need as much info as you can give. I just tried (radio in mode 2): Create a new model, apply the heli template, on the HELI menu select swash type a...

Yes, those are the 4 pads. I believe they should connect to the 4 connections on the USB cable.

Mike.

Managed to find some time! Fuses: HIGH 0xFD LOW 0x1A No self program No DWEN Brownout at 1.8V No Reset disable SPIEN on EESAVE on Watchdog enabled No CLKDIV8 int RC @ 9.6MHz, 14CK and 64mS I've commited a code update to include having the watchdog running, and also to check the OSCCAL value doesn't ...

All 4 connections are used, power is used when flashing. In any case, you MUST have at least ground D+ and D- for the USB to work. The other 2 connections may well be soldered on the other side of the board. The USB connection run along the 5-way ribbon to the main board. On the main board I think t...

If you open the case up, you can see where the USB connector connects to the back board. The USB connector is on a small PCB that is mounted at right angles to the board, and the 4 connections are soldered between them. Worth checking they haven't broken due to mechanical flexing.

Mike.

aadamson wrote:Normally an STM that has built in DFU capabilities, needs a jumper on Boot0 to do that... but let's see what they have done...

We got FrSky to set the hardware up so plugging the USB in to a powered off unit sets the Boot0 pin for bootloading.

Mike.

A bit more complicated than that! When a model (or the general settings) is changed, a copy of the model is saved, then a "rename" operation takes place to swap the newly saved 'file' with the original. However, the original file still remains taking up some space in the EEPROM. When you s...

How odd, I just tried it and I see what you mean, I'll look into it.

Mike.

Edit: I think I see the problem, fix in the next revision.

I recently did a major change to the EEPROM of er9x, including code in er9x to automatically update from "version 0" to "version 2". This option in eepe allows you to do this change as eepe defaults to "version 0" for backward compatibility. I think it is from r803 onwa...

"Connect IOBoard pin D5 to your FrSky receiver pin RX and data will start to flow."

Your first post said you connected D6 to TX on the receiver.

Mike.

HIGH 0xFD
LOW 0x3A

No self program
No DWEN
Brownout at 1.8V
No Reset disable
SPIEN on
EESAVE on
No watchdog - No code to retrigger this at present, maybe I should add it.
No CLKDIV8
int RC @ 9.6MHz, 14CK and 64mS

I'll look into the watchdog, but may be Monday before I get to it.

Mike.

I'll see what I can do, I just use AvrStudio to my STK500 programmer so I haven't used AVRDUDE for the fuses (or programming!).

Mike.

I've committed a code update, which I've tested. This includes the scaling option when pin 5 (PB0) is pulled to ground. I've also added the .hex file to save compiling it. This may be useful and the code is using sowtrare timing and a different compiler might generate slightly different code that up...

Just for info, I seem to be still using the Yagarto ARM compiler V4.6.0. I tried the V4.7.3 download and ersky9x got one to two hundred bytes larger.

Mike.

OK, this is the wrong firmware, er9x is not openTx, please post again in openTx.

Mike.

Which revision of ER9X are you using?
You appear to refer to "CF1" which is "CUSTOM FUNCTION 1".
Er9x does not have custom functions, they are in openTx.

Mike.

You need to make sure the protocol is FrSky hub, not mavlink.

Mike.

I've put some code together, I'll test it tomorrow if I get time. 18.3 / 13.3 = 1.37594 11 / 8 = 1.375 So all I need to do is scale the A2D value by 11/8 and adjust to 8 bits. It might be a fraction of 1% out, but that is better than the resistor tolerance and can be corrected by the calibration in ...

Just created:
http://code.google.com/p/x8r-analog/

The link would go between pins 4 and 6 on the ISP header, pin 4 goes to pin 5 of the 'tiny and pin 6 is ground.

Mike.