@robotiko one disadvantage of setting SPI mode to dio: board need manual reset after flashing. But we get 2 more pins.
@laurentppol yes.. in fact you get gpio10 without reset
I cannot drive gpio9
supposed to be amica boards
two different suppliers.. but same issue
@sle118 I didnt knwo you were working on jpg
what is great !
:D
but you mentioned that got a GDB working?
debugging?
@raburton cool, I need to retry building again
or you could probably submit your fixes, and I can change the travis to build examples as a part of test process.
@kireevco i already pushed the changes, they are in develop
@riban-bw thanks, had a quick look but will have a better look as soon as I get chance...
@kireevco you can just build the samples by name now, i.e.
make Basic_rBoot
and your
make test works as before, it will build sming, spiffy and a couple of samples
and
make recurse-samples does all the samples, as before
although i was tempted to rename that target to something simpler, maybe just 'samples' (and get rid of the internal 'samples' target that only does 3 of them), but I'll leave that up to you
just added an extra slash that was needed in the path, was ont he end of my path but not on the one on the build system so needed one in the script to be sure
travis is working fine for linux now, but osx doesn't build, looks like a problem with the find command on osx
i'll leave that one to you
Hi
What do I need on windows UDK, esp-alt-sdk and ming ?
@raburton I have been reading the robot readme.text file as rendered by doxygen in HTML. It corrupts code elements such as the cinfig structure because it sees it as plain text, no formatting. Also, much if the info is not particularly relevant to Sming. I wonder if we need a different version for Sming. This is common for all contributed libraries too where we may want an overview / howto document for each.
Or maybe we constrain doxygen to creating only API docs and put overview / how-to elsewhere. I'll get the API doc framework configured so we can see how it feels.
@alonewolfx2 @robotiko :
I just included SPI class into Sming_RTOS.
Can you test this on your nice hardware peripherals ?
I just included SPI class into Sming_RTOS.
Can you test this on your nice hardware peripherals ?
@hreintke terrific
@all :
And of course anyone else who can do so and would help in getting the future of Sming working correctly :smile:
And of course anyone else who can do so and would help in getting the future of Sming working correctly :smile:
I currently have no set up example with spi HW.. @alonewolfx2 if you have one of your SPI displays ready for test.. will be easier.
mine seem to be just i2c
@all anyone can tell me teh difference between i2c lib and wire lib in Sming?
are the same?
@riban-bw I was interested more from an rBoot upstream pov than Sming, i think the included third party libraries/ tools that are just included probably shouldn't be documented as part of Sming (except in a how to use them from sming sense), primarily doxygen just our own code
so all the sming apis and stuff would be documented, but not modifying components we pull from upstream sources, as it makes them harder to update
but once i've had a proper look at the rBoot stuff you've done i'll hopefully take that upstream
@raburton thank you! find command is different in osx, it's a bsd-one, 2 options here: install gnu-findutils or update Makefile to support bsd syntax
if it can be made compatible somehow that would be less build effort than installing a the gnu find package every time it builds
but i don't have a box to play with so i can't help you much with that, but I'm sure it must be possible
@hreintke you around?
hey guys...I just got a new mac and trying to get everything set up to continue Sming development. What is the recommended way to install the SDK these days? Is the alt-sdk working and stable?
you can install linux on a mac right? I mean it's just the same hardware as a normal pc but more expensive ;-)
but seriously , doesn't look like the osx quick start has been updated, pretty sure the alt sdk is the prefered option now
in theory just install that, then git clone sming
cool, thanks Richard
@kireevco how about
find ../samples -maxdepth 1 -mindepth 1 -type d -not -name ".*" | sed -e 's/..\/samples\///'
does osx have a compatible sed as standard?
I cloned sming rtos. was able to build sming. upon comipling basicRboot I got this error
C:\tools\Sming_RTOS_POC\samples\Basic_rBoot>make
OC out/build/libmain2.a
make -C /C/tools/sming/Sming/rboot
make[1]: Entering directory `/C/tools/sming/Sming/rboot'
CC rboot-stage2a.c
LD /c/tools/Sming_RTOS_POC/samples/Basic_rBoot/out/build/rboot-stage2a.elf
E2 /c/tools/Sming_RTOS_POC/samples/Basic_rBoot/out/build/rboot-hex2a.h
CC rboot.c
LD /c/tools/Sming_RTOS_POC/samples/Basic_rBoot/out/build/rboot.elf
E2 /c/tools/Sming_RTOS_POC/samples/Basic_rBoot/out/firmware/rboot.bin
make[1]: Leaving directory `/C/tools/sming/Sming/rboot'
C+ app/application.cpp
In file included from app/application.cpp:1:0:
include/user_config.h:26:33: fatal error: c_types_compatible.h: No such file or directory
compilation terminated.
make: *** [out/build/app/application.o] Error 1SMING_HOME ?= c:\tools\Sming\Sming
ESP_HOME ?= c:\Espressif\ESP8266_SDK
what went wrong
interesting, that file doesn't exist in sming rtos
but it's included from user_config.h, so why don't we all see this error?
why is it not getting used for the rest of us, but it is for you???
dunno
hmm, except if it put rubbish in that file it does throw an error, so it is getting used
but not throwing an error of failing to find the file
@raburton osx doesn't comply with gnu
so is there a sed?
you have to minimize shell usage in make files :)
or install gnu tools
@crosofg actually looks like this file is now in rtos, maybe it was recently added
brew install gnu-sed --with-default-names
brew install findutils --with-default-names
for these tools specifically ^
maybe we don't need to compile the samples on all platforms?
but that's not something people will need
@raburton what's the problem with my make iteration?
i thought the find command wasn't working on osx?
SAMPLES := $(shell find ../samples -maxdepth 1 -mindepth 1 -type d -not -name ".*" -printf '%P\n')
without sed
ah, wait
I have gnu find
build fails on osx
damn.
no -printf on osx find command
I forgot I have gnu sed, that's why it worked on my laptop
it can probably be as easy as
ls
ls ../samples
lol, probably
:)
just one column.. forgot the flag
ls -1 ../samples
@crosofg maybe @hreintke put the file back in, pretty sure i took it out before, but the samples seem to reference it so it looks deliberate that it went back in
no recurse needed
@crosofg got to go out now, i suggest temporarily just comment out the include line and i'll look at it
cool
do to a rename i can;t see the history for the file anymore
@crosofg silly question
@raburton SmingHub/Sming#535
you are usign these path with rtos ?
SMING_HOME ?= c:\tools\Sming\Sming
ESP_HOME ?= c:\Espressif\ESP8266_SDK
you shoudl poitn them to the rigth rtos sdk and sming version
yeah .. rtos has a different sdk. completely forgot
:D
will check
I had similar issues with the rtos rboot
look in the includes..
if you are in windows world and installed with choco
@raburton could you please review my PR ?
you might also have a route in path that will be shown there
and I'll merge it?
@crosofg try to build the sming RTOS itself
and the other examples
I have uploaded a PoC API (a few functions and classes documented) to http://http://riban-bw.github.io/Sming/api. Take a look and let me know what you think. There is a modules section which groups functions. I'm going out now so won't add more docs for at least a couple of hours.
When we are (fairly) happy with the proposal, we need someone (preferably original author) to review documentation.
@riban-bw .. the main page is weird.. but the modules is GREAT
The main page is the github readme.md.
yep and they don't get on well
The images are not showing on the main page. I haven't looked to see how to resolve that.
idea.. similar the modules..
examples
samples..
Also, we may wish to have something different as the main page. Something that identifies it as the API and maybe some navigational help.
is where everybody starts and never knwo what is each example for
I have constrained the API to just the core sming for now to see how it looks and works. Later can add examples and libraries.
Maybe libraries - as RAB mentioned earlier, we should avoid having to (re)document upstream code.
yep
I do agree on that
is easier to document on the code..
But if we can include the 3rd party libs and encourage upstream to document then good. RF24 is the only lib to be documented currently.
Modules is a bit of a mess. The global functions like digitalWrite work quite well but the classes may prove difficult for novices to navigate.
I wanted to see what it looks like with a few modules documented so did half a dozen of the key core ones. From this we should be able to see if this will work and what changes may improve it. Then see if those changes can be applied before documenting everything wrong!!!!
I'll see what you all say.
It might be possible to automate the api doc creation with Travis-CI. I'm not particularly familiar with Travis-CI.
@robotiko I didn't say I got GDB working. I merely pointed at an example of GDB and wondered if anyone had done it
@sle118 ok :D
we were waiting for your fixes :D
ok
it doesnt compile
at least under windows
Anyone working on porting U8GLIB ?
you can read the comments in the PR
@sle118 I think @alonewolfx2 was workign on it
Turns out my JPG port would work pretty well, except that the adafruit Oled library doesn't play nice with my oled controllers
every 2nd line is lost while drawing
and this has been fixed in U8GLIB through Init sequence update
we were waiting for your fixes :D -- I wish I had debug too!
@all hi people yesterday @alon24 post here about his new lib https://github.com/alon24/InfoScreens
Wow!! Timing could not be more perfect! I was looking for a solution like this to build a small SqueezeBox remote control box and I guess I have no more good reasons not to do it now!
@sle118 I have been playing with InfoScreens and is really nice lib
@raburton :
I am around now, but think you are out already
I am around now, but think you are out already
@sle118 so use it , and give me feedback
@sle118 with which screen do you want to use it? @alonewolfx2 is maybe working on ili9341 adaptation or another one
@rabutron @robotiko can you guys check SmingHub/Sming#535 ? it's breaking osx build
@alon24 I am going to use it with a ssd1306
however, I need to figure out why every 2nd line of display is skipped
(this is a Chinese oled)
I am thinking that the issue has to do with init sequenced
sequence
Where to read what is the difference between SPI and HSPI on NodeMCU (ESP12E)?
@crosofg :
Do you still have the issue with the c_types_compatible ?
I think I can remove the file and the references to it. Will do tomorrow (CET), test as far I can and commit to my repo
Do you still have the issue with the c_types_compatible ?
I think I can remove the file and the references to it. Will do tomorrow (CET), test as far I can and commit to my repo
@hreintke env variables? I have noticed, that if I have vars set for RTOS (BIN_HOME, SDK_BASE) programs for no nos don't compile. Maybe this is similar?
how to insert "unset xx" to a Makefile?
@laurentppol : you cloned the rtos sming and espressif rtos sdk and have set the env variables accordingly ?
@laurentppol : what do you mean with "unset xx"
@hreintke yes, but if You set vars for BOTH SDK/Sming, "plain Sming" does not compile. I had to use "unset" before compiling
so the question about unset in Makefile
you can't have variables for both at the same time. They use the same with different values
no, not the same, Sming uses "SMING_HOME" and "ESP_HOME", RTOS uses SMING_HOME, BIN_HOME, SDK_BASE
and Sming gets confused if SDK_BASE/BIN_HOME is set
SMING_HOME can't be the same for both, ESP_HOME can,
ok for SMING_HOME
is there a method to set it in Makefile, not in .bashrc?
on Linux
BTW, 2 weeks for porting "4 sensors thermometer / DS /AVR" to ESP, looks OK or no?
sure, don't set env vars in linux, only use makefile settings.
how in makefile?
simply add "ESP_HOME = xxx" in Makefile-user.mk?
yes
makefile-user has included examples
thx, I'll try
ok, I am out now.