- Posts: 170
Can Any help me with my F7
- djtrance
- Topic Author
- Offline
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
You want something like this:
GUI_CreateBarGraph(&gui->elem[i].bar, x, y, w, h, -10000, 10000,
type == ELEM_VTRIM ? TRIM_VERTICAL : TRIM_INVHORIZONTAL, trim_cb, (void *)(long)(src-1));
trim_cb() gets the value. 'src-1' is the trim index. I think 0=throttle, 1=ele, 2 = rudder, 3= ail though it probably depends on stick mode.
Please Log in or Create an account to join the conversation.
- djtrance
- Topic Author
- Offline
- Posts: 170
+ Compiling 'target/common/devo/petit_io.c'
target/common/devo/petit_io.c: In function 'disk_erasep':
target/common/devo/petit_io.c:107:32: error: 'pos' undeclared (first use in this
function)
drive[_drive_num].EraseSector(pos + drive[_drive_num].SECTOR_OFFSET) * 0x1000)
;
^
target/common/devo/petit_io.c:107:32: note: each undeclared identifier is report
ed only once for each function it appears in
target/common/devo/petit_io.c:107:79: error: expected ';' before ')' token
drive[_drive_num].EraseSector(pos + drive[_drive_num].SECTOR_OFFSET) * 0x1000)
;
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
Please Log in or Create an account to join the conversation.
- djtrance
- Topic Author
- Offline
- Posts: 170
Please Log in or Create an account to join the conversation.
- djtrance
- Topic Author
- Offline
- Posts: 170
in the second picture you can see the description.
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
djtance, you will want to turn that off.
in the devof7 target_defs.h, set:
#define SPIFLASH_SECTORS 512
#define USE_DEVOFS 0
and remove:
#define SPIFLASH_AAI_AF 1
I did run into a rather large annoyance. The bootloader does not seem to give full write access to the flash chip. In order to install the filesystem, I needed to build a custom image to copy raw data to the flash. That makes updating the filesystem really annoying. I have some ideas about working around it that I'll need to play with..
Please Log in or Create an account to join the conversation.
- djtrance
- Topic Author
- Offline
- Posts: 170
Please Log in or Create an account to join the conversation.
- djtrance
- Topic Author
- Offline
- Posts: 170
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
It doesn't make any sense, since my devo8 works just fine with the same settings.
Please Log in or Create an account to join the conversation.
- djtrance
- Topic Author
- Offline
- Posts: 170
Please Log in or Create an account to join the conversation.
- djtrance
- Topic Author
- Offline
- Posts: 170
Please Log in or Create an account to join the conversation.
- djtrance
- Topic Author
- Offline
- Posts: 170
How I say before, I'm moving to mac all of my environment. When I use the same code for example:
make TARGET=devo10, all is good, but if I do
make TARGET=emu_devo10 the console return a lot of problem... do you know what happened?
I'm ussing mac because with windows I have a lot if problem with mercurial. (source tree)
and my virtual machine for some reason is not working well, I must fix it, but I would like to work on mac, must be very similar to linux I guess.
./std.h:5:9: warning: 'strncpy' macro redefined
#define strncpy "BAD_FUNC" //Do not allow any use of strncpy (use strlcpy instead)
^
/usr/include/secure/_string.h:118:9: note: previous definition is here
#define strncpy(dest, src, len) \
^
In file included from target/emu_devo8/channels.c:15:
In file included from ./common.h:29:
./std.h:62:13: warning: 'sprintf' macro redefined
#define sprintf tfp_sprintf
^
/usr/include/secure/_stdio.h:46:9: note: previous definition is here
#define sprintf(str, ...) \
^
In file included from target/emu_devo8/channels.c:15:
In file included from ./common.h:29:
./std.h:63:13: warning: 'snprintf' macro redefined
#define snprintf tfp_snprintf
^
/usr/include/secure/_stdio.h:56:9: note: previous definition is here
#define snprintf(str, len, ...) \
^
In file included from target/emu_devo8/channels.c:15:
./common.h:189:8: error: expected parameter declarator
size_t strlcpy(char* dst, const char* src, size_t bufsize);
^
/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
__builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
^
/usr/include/secure/_common.h:39:62: note: expanded from macro '__darwin_obsz'
#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
^
/usr/include/secure/_common.h:30:32: note: expanded from macro '_USE_FORTIFY_LEVEL'
# define _USE_FORTIFY_LEVEL 2
^
In file included from target/emu_devo8/channels.c:15:
./common.h:189:8: error: expected ')'
/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
__builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
^
/usr/include/secure/_common.h:39:62: note: expanded from macro '__darwin_obsz'
#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
^
/usr/include/secure/_common.h:30:32: note: expanded from macro '_USE_FORTIFY_LEVEL'
# define _USE_FORTIFY_LEVEL 2
^
./common.h:189:8: note: to match this '('
/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'
__builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))
^
/usr/include/secure/_common.h:39:53: note: expanded from macro '__darwin_obsz'
#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)
^
In file included from target/emu_devo8/channels.c:15:
./common.h:189:8: warning: type specifier missing, defaults to 'int' [-Wimplicit-int]
size_t strlcpy(char* dst, const char* src, size_t bufsize);
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
I haven't seen it before. Looks like the Mac env has defined macros for all of our string handling routines. I am not an expert on Macs, so I don't know whatit will take to fix it.
From what you posted, you need to go into std.h and add this before the 'BAD_FUNC' thing:
#ifdef strncpy
#undef strncpy
#define USE_OWN_PRINTF 0
#endif
But you'll need to try it and see if that is sufficient
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
Please Log in or Create an account to join the conversation.
- djtrance
- Topic Author
- Offline
- Posts: 170
I will do a special function for the mix curve, I will use a center dot and normal dot to do this. I hope this must work.
Please Log in or Create an account to join the conversation.
- djtrance
- Topic Author
- Offline
- Posts: 170
Please Log in or Create an account to join the conversation.
- djtrance
- Topic Author
- Offline
- Posts: 170
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
As far as the horizontal trims go, positive should be to the left. If it isn't, then likely the trims are reversed in tx_buttons.c
If the trims don't disappear when entering the menu, there may be something wrong with the LCD_Clear() function.
Please Log in or Create an account to join the conversation.
- Home
- Forum
- Development
- Development
- Can Any help me with my F7