-
Thread
AT90USB162 Endpoint Interrupts funktionieren nicht
und .exe am Ende, damit es auch garantiert unportabel wird … Außerdem ist "all" nicht das erste Target, sodass ein simples "make" halt dann nicht alles baut wie sonst üblich. (end-of-rant) Ich bekomme folgende Warnungen und Fehler, wenn ich das compiliere: [pre] avr-g++ -funsigned-char -funsigned-bitfields
aus dem Github-Repo nehmen. Wenn du es schaffst, auf der Kommandozeile den $PATH zu setzen und ein "make" aufzurufen, kannst du auch das mitgelieferte Makefile benutzen. Ansonsten kannst du natürlich dein Kompilat (ELF-File) nochmal hier abladen, welches dein Compiler aus dem gleichen Code produziert
-
Thread
Rust - ist das hier um zu bleiben?
Moin, Vincent H. schrieb im Beitrag #5701324: > Man muss dem Compiler lediglich das Target als flag übermitteln. Also in > etwa so: > Hmmmm.... [c]echo "main() {}" > hello.c clang hello.c #OK, da faellt ein a.out raus. clang -target arm-none-eabi hello.c error: unable to create target: 'No available targets are compatible with this triple.'[/c] Hm, ok - also was kann denn mein clang fuer Targets? Uuupsi: https://stackoverflow.com/questions/15036909/clang-how-to-list-supported-target-architectures
-
Thread
Ambilight mit STM32F4discovery und TVP5150AM1
49:43 **** Clean-only build of configuration Debug for project Ambilight-STM32F4-GNUARM-V1.2 **** make clean make: *** No rule to make target `clean'. Stop. [/c] Oder muss ich die Kompilerflags noch selber irgendwo ergänzen? Ich dachte, dass sei u.a. der Sinn eines Projektfiles, auch die Einstellungen
the tvp 5150 is normal. no hot, im ordering 10 more tvp to find out what is the problem :D
-
Thread
for(;;){} Schleife
have no observable behavior, without having to prove that they would eventually terminate because it can assume that no thread of execution can execute forever without performing any of these observable behaviors
comma operator in the initialization or update clauses of a for statement, it is suggested that no more than three variables should be updated. More than this tends to make the expression too complex. In this case it is generally better to use separate statements outside the for loop (for
-
Thread
GPIB-RS232-Schnittstelle
. Selber compilieren hat auf den ersten Anlauf hin nicht funktioniert ("makefile:58: dependencies: No such file or directory" bzw. "make.exe: *** No rule to make target `all'. Stop.")
group__avr__eeprom.html Wegen der .bin Datei: Da es von der Struktur der Datei eher nach einer .elf Datei aussah hab ich das per avr-objcopy -O ihex -I elf32-avr object.bin test2.hex in ein .hex umgewandelt. Man sieht im Hex-Viewer keinerlei Strings, was mich ein bisschen wundert weil das Programm
-
Thread
FT800 / FT810 Library
Does it display anything now? >I can't confirm that I have better performances, but it seems to work as >good as before. Going from no output to no output would also mean it is "as good as before" :-) >I was using the default Arduino target, and changed a few pin >definitions to suit
well below 8k (approx. 3700 bytes) -Refresh rate of display 102 Hz With 20 ms data refresh rate to BT818 it stalls immediately (SPI LED is full on display freezes), 21 ms works. Tried to tweak the SPI speed to 10 Mhz or lower makes no difference
-
Thread
Transistortester AVR
connected to VCC. This may be the reason, why I had no problems without the reference! The new version of selftest No. 2 to 6 shows no more the measured voltages in row 2. The difference to expected value is now
LM4040AIZ2.5 (or LM336-Z2.5) instead of the LT1004. The voltage reference is not required, it is only used to measure the actual VCC (5V) voltage. Justin Sergio schrieb im Beitrag #2981790: > 5) Do you expect to make major revisions to the hardware every once in > awhile? There is no change planned
-
Thread
IRMP - Infrared Multi Protocol Decoder
AVRDUDE_FLAGS += -p $(AVRDUDE_MCU) #################################################### # make targets #################################################### .PHONY: all clean distclean avrdude-terminal # main rule all: $(TARGET).hex $(TARGET).elf: $(OBJECTS) $(CC) $(CFLAGS) $(LDFLAGS
irmp_get_data« irmp.h:367: Fehler: expected »=«, »,«, »;«, »asm« or »__attribute__« before »irmp_ISR« make: *** [main.elf] Fehler 1[/code]
-
Thread
Handycamera MCA-25 ansteuern - ip webcam mit mega32
`servo_pin_high' main.c:39: warning: implicit declaration of function `servo_pin_low' main.c:47:2: warning: no newline at end of file main.c:47: error: parse error at end of input make.exe: *** [main.o] Error 1
compilieren (alles nach readme eingestellt): -------------------------------------------------------- > "make.exe" all MAKE Version 5.2 Copyright (c) 1987, 2000 Borland Error makefile 335: Colon expected Error makefile 366: Too many rules for target '%.o' Error makefile 404: Command syntax error *** 3
-
Thread
ENC28J60 (Mikro-)Web-Server die Nächste
files could not be found . und wenn ich das Projekt kompilieren will kommt folgende Fehlermeldung make: *** No rule to make target `../Net/TcpApps/Gpio.c', needed by `Gpio.o'. Stop. kann mir jemand sagen was ich falsch mache !! Danke schon mal im Voraus
Funktionstüchtig! Es liegt wohl an Einstellungen in meinem AVR-Studio, aber der Server läuft! Das Make-File macht mir zwar noch zu schaffen(no rule to make taget) aber hier gibt es ja viel zu lesen :-) ) Es ist also mit sicherheit kein Hardwareproblem. Vielen vielen Dank, für die freundliche Hilfe
-
Thread
Thermomix Rezeptchips
What I found out with a Hex Editor: data size: 32bit endiness: little endian ELF Version: original version of ELF target System: systemV ? Version: 0 type: executable target architecture: ARM ... the rest is to much for my electricians brain :) need a software guy. Cu
Joachim S. schrieb im Beitrag #5217555: > Either way, I actually wonder if it doesn't make sense to simply develop > an alternative main board for the Thermomix, instead of trying to hack > the original one. The problem with that is that you would need to open up your Thermomix. I was
-
Thread
AVR für wenig Geld im LAN
bootloader.hex datei auf dem desktop 2.Öffnen des Programmer´s Notpad 3.File==>Open==>bootloader.hex 4.Make clean 5.Make all 6.Programm 7.Fehler:> "make.exe" program make.exe: *** No rule to make target `program'. Stop. > Process Exit Code: 2 > Time Taken: 00:01 Timo
datei auf dem desktop > 2.Öffnen des Programmer´s Notpad > 3.File==>Open==>bootloader.hex > 4.Make clean > 5.Make all > 6.Programm > > 7.Fehler:> "make.exe" program > make.exe: *** No rule to make target `program'. Stop. Bei der über das Pollin-Tool generierten HEX-Datei handelt es sich
-
Thread
Warum immer Eagle?
nun die wesentlichen Unterschiede in den Funktionen der beiden Programme? Was kann Eagle mehr als Target? Ich denke eine kurze, rein informative Antwort hilft dem TO auch am meisten ;-) Schonmal Vielen Dank Gruß HighTec
Combining the hours and days of development supported by your gifts will bring the project ever closer to reaching its targets. Reaching a target of... Would allow developers to... €150,000 Make Kicad usable for very complex Printed Circuit Board designs with acceptable productivity. €300,000
-
Thread
Ergebnisse einer FFT zusammen fassen
{ // the mic signal is to low for (int i = 0; i < ADC_NUMBER_OF_SAMPLES; i++) { fftData->fftInput[i] += fftData->fftInput[i] * scaleFactor; } } // make this once if (noMusic) { // music is back setupData->effectSetupData.brightness = saveMaxBrightness; noMusic = 0x0; } } else { // make
-
Thread
made from scratch Firmware für Wittig/Welec Oszilloskop W20xxA
Er findet die Datei nicht. Ist aus deinem Make ein TomCat_ram.ucl rausgefallen? Das Makefile muß analog zu Osoz umgebaut werden. Ich hatte die Make-Targets von Osoz noch etwas umgeräumt: Ein normales "make" ohne spezielles Target baut die beiden
dort tatsächlich den Heap verzeichnet, auf hinter die Variable selbst. Ich habe am Anfang meines main() nun folgendes stehen: [code] // bugfix for heap manager, _sbrk() expects this to be a variable and point to heap extern uint32_t* _nasys_uninitialized_storage_end; _nasys_uninitialized_storage_end
-
Thread
Alles Rund um den MEDION LIFE P89626 NAS
you # would want to activate "DirectWrite") it should not be a problem to # redownload the interrupted file. DirectWrite=no # Check CRC of downloaded and decoded articles (yes, no) # Normally this option should be
automatically paused # all - all par2-files must be downloaded # one - only one main par2-file must be dowloaded and other must be paused # Paused files remain in queue and can be unpaused by parchecker when needed LoadPars=one # Automatic par-verification (yes, no) # To download
-
Thread
Wechselrichter Hoymiles HM-xxxx 2,4 GhZ Nordic Protokoll?
the addresses of the devices involved, and can therefore listen for packets specifically addressed to these. But to make matters worse, it seems to me that the on-air bitrate is hardcoded to 2 MBit/s (https://github.com/BastilleResearch/nrf-research-firmware/blob/02b84d1c4e59c0fb98263c83b2e7c7f9863a3b93
clone https://github.com/nRF24/RF24.git export RF24_DRIVER=SPIDEV cd RF24 rm Makefile.inc #just to make sure there is no old stuff mkdir build && cd build cmake .. make sudo make install cd ../pyRF24 rm -r ./build/ ./dist/ ./RF24.egg-info/ ./__pycache__/ #just to make sure there is no old stuff
-
Thread
Besteht Interesse an einfacher Experimentierplatine fuer den Xmega128a1? Gesperrt
-Wall -Wstrict-prototypes -Wa,-adhlns=main.o -std=gnu99 -MMD -MP -MF .dep/main.elf.d main.o --output main.elf -Wl,-Map=main.map,--cref -lm Creating load file for Flash: main.hex avr-objcopy -O ihex -R .eeprom -R .fuse -R .lock main.elf main.hex Creating load file for EEPROM: main.eep avr-objcopy -j .eeprom --set-section-flags=.eeprom="alloc,load" \ --change-section-lma .eeprom=0 --no-change-warnings -O ihex main.elf main.eep ||
-
Thread
Erfahrungen mit Platinen von www.elecrow.com
Sebastian A. schrieb im Beitrag #4618290: > Auf was muss ich achten, und wie erstelle ich in Target passende Gerber > Dateien so das es keine Probleme bei elecrow gibt? Die haben auf der Webseite (neben einer in Eagle verwendbaren Datei für Design-Rules) einen CAM-Job den Du in den CAM-Processor
(die Fertigungsdaten waren schließlich eindeutig) kam dann nur: [code] I'm sorry for that. We make the stencil with solder paste,and if you have a special request, you need to leave your comment when you place order. I checked your files again, for these holes,we will not make it if you didn't
-
Thread
WordClock mit WS2812
at 0x00004800... (90 %) Writing at 0x00004c00... (95 %) Writing at 0x00005000... (100 %) Failed to write to target Flash [/code] Hat jemand ne Idee was das sein kann? Da ich den STM zum ersten mal verwende habe ich eine HowTo geschrieben was ich befolgt habe. Werner
Hello Frank Thank you for your interest in my post, I know it's hard to read because the translators by Google translator. I checked the configuration 24 with LED corner and did not work, so I decided to make a 18x18 matrix (without corner LEDs) and everything seems to
-
Thread
STM32F103C8T6 - Fälschung von ST bestätigt
?) Debug registers return valid non-zero info (contravenes Erratum 2.3 of genuine parts) Writing to backup registers, and then turning off the backup interface clock, seems to lock up parts of the chip: Future writes to certain registers hang forever with no exception or reset I2C peripheral won't
Debug registers return valid non-zero info (contravenes Erratum 2.3 of genuine parts) - Writing to backup registers, and then turning off the backup interface clock, seems to lock up parts of the chip: Future writes to certain registers hang forever with no exception or reset - I2C peripheral
-
Thread
Wlan2Serial Modul für 5 euro
. You can buy now for $2.00. Very hard to compete with prices that low. No one in China has made module with FCC Modular approval. Hobbyist are ordering from China and mailing into US which gets around FCC rules. For vendors based in US,
spi driver； 6、Optimize APIs related to espconn； 7、Fix some bugs to make the software more reliable； Known Issue: 1、exception of small probability occured while recving multi-client data in softap 2、restart of small probability occured
-
Thread
Wittig(welec) DSO W20xxA Open Source Firmware (Teil2) Gesperrt
[code] C:\welec\firmware>make # 2009.10.25.13:04:13 --- (Note: to make for Nios 16, try "make clean all M=16") # 2009.10.25.13:04:13 --- Compiling nios-elf-gcc -I ./inc -I ./src -I ./inc -I . ./inc -I ../../inc -I ../../../
in normal view the DSO do reset (all LED bright and after show logo screen). After this there are no track on the display and is necessary to switch OFF and ON to fix so the track are visible again. The setting seems no be lost, only the tracks appears to be a bit out of zero, all settings appear to
-
Thread
Erfahrungen mit Platinen von JLCPCB / EasyEDA
W202005230411126,since you put them in the outline layer rather than dril layer. Our engineer will make it as non-plated through slots. If you want to make them as plated through slots please kindly put them in the drill layer.
to make it as show in your file.Please kindly choose the correct designs when you place your order next time. 2.Hi Sir/Madam,the special price is only for the single board and not for the panel board
-
Thread
Linux wird nicht wirklich akzeptiert, woran liegt das ?
Name Min. HPLIP Version Chrome OS Support Driver Plug-in8 Support Level9 Print Mode Scan to PC3 PC Send Fax5 Connectivity USB Network Parallel1 Note HP Laser NS MFP 1005 3.19.6 Yes Yes Full Mono Yes No USB,Network
Nö, aber auch das ist Windows-Feeling.
-
Thread
OOP - für was in aller Welt soll denn das gut sein?
vernünftigen Design, lassen sich (imho) C++ Programme (viel!) besser verstehen als C Programme. "C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do, it blows away your whole leg." [Bjarne Stroustrup]
problems that can be usefully expressed using class hierarchies - the main weakness of OOP is that too many people try to force too many problems into a hierarchical mould. Not every program should be object-oriented. As alternatives, consider plain classes, generic programming