This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-08-09
Channels
- # announcements (4)
- # babashka (2)
- # beginners (8)
- # calva (2)
- # chlorine-clover (7)
- # cider (3)
- # clj-kondo (1)
- # cljs-dev (2)
- # clojure (21)
- # clojure-dev (2)
- # clojure-europe (5)
- # clojure-spec (17)
- # clojuredesign-podcast (7)
- # clojurescript (8)
- # conjure (4)
- # cursive (3)
- # datomic (1)
- # defnpodcast (5)
- # esprit (51)
- # fulcro (7)
- # jobs (1)
- # luminus (3)
- # news-and-articles (1)
- # off-topic (2)
- # other-lisps (3)
- # pathom (8)
- # portal (3)
- # re-frame (3)
- # re-ops (1)
- # shadow-cljs (26)
- # testing (15)
- # tools-deps (34)
- # xtdb (1)
@mfikes Did you ever try querying any web resources like with sockets or http gets? I can't for the life of me get it to work, even though I know the network is working as I have the networked repl
's always a possibility that the C build of the Espruino engine is borked. (For example, setTimeout
doesn
oh weird
Yeah I was about to flash normal espruino back on it and see if it works with the vanilla configuration
At some point I was planning on re-doing the C build to see if I can sort out what might be wrong with it.
Well I'd be more than happy to help
Yeah, feel free to dig into it! If you try making the C build you will see that there currently isn't anything committed to the Esprit repo for that. It is currently just loose instructions partially off in a gist that is linked from the main README
Yep, I saw that. I was going to go through it to figure out whats up.
Ok so yeah, the get works fine on the vanilla build
Cool. When the C build is done, there are things that can be enabled or disabled in the makefile. My guess is that I may have inadvertently disabled something.
Yeah I agree
Yeah NTP was broken on the esprit side, works fine on vanilla
My rough thoughts were to come up with some sort of system for patching vanilla. Maybe a set of patch files committed to the Esprit repo, or even just branching the upstream Espruino repo.
Also, I found that there were issues using the very latest Espruino repo (I can't recall what broke)
Yeah so the memory map is very different in master than that of the 3.1.2 tag
They increased factory and ota_0 and decreased storage
So, I'm not convinced we are using the 8MB of flash that we have available on the WROVER
But I'm still not 100% on how espruino is using the partition table
factory hold the interpreter, our code goes into js_code, but what are the other partitions for
ota doesn't even work on the 32 with espruino right now, so I think we can just get rid of that
Yeah, OTA is probably not a critical feature to have for messing around with this stuff.
Another thing that is annoying is that we only seem to be able to access half the RAM.
But like, we can bump the js_code space to like 4M
oh huh
because of something espruino is doing?
weird
This board only adds 4 MiB FWIW, maybe because of the same reason: https://www.tindie.com/products/seonr/tinypico/
Yeah worked fine for me
With the big boi partition table
Haven't tried to upload cljs yet, but that partition table seems to work
Their build process is very confusing, and they are using a pretty old version of the esp-idf
It was even more challenging when I first tried to use their stuff on macOS. I finally found it was much easier to just do things in a Linux VM.
Oh I can imagine