Fork me on GitHub
#esprit
<
2020-08-09
>
kiranshila20:08:28

@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

mfikes20:08:07

No... I don't recall ever trying that

mfikes20:08:27

's always a possibility that the C build of the Espruino engine is borked. (For example, setTimeout doesn

mfikes20:08:32

't seem to work)

mfikes20:08:42

(Nor do I seem to be able to hit my return key 🙂

kiranshila20:08:12

Yeah I was about to flash normal espruino back on it and see if it works with the vanilla configuration

mfikes20:08:16

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.

mfikes20:08:35

Yeah, comparing with vanilla might be worthwhile

kiranshila20:08:12

Well I'd be more than happy to help

mfikes20:08:10

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

kiranshila20:08:13

Yep, I saw that. I was going to go through it to figure out whats up.

kiranshila20:08:59

Ok so yeah, the get works fine on the vanilla build

mfikes20:08:50

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.

kiranshila21:08:14

Yeah I agree

kiranshila21:08:53

Yeah NTP was broken on the esprit side, works fine on vanilla

mfikes21:08:23

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.

mfikes21:08:47

Also, I found that there were issues using the very latest Espruino repo (I can't recall what broke)

kiranshila21:08:12

Yeah so the memory map is very different in master than that of the 3.1.2 tag

kiranshila21:08:42

They increased factory and ota_0 and decreased storage

mfikes21:08:01

Ahh, right. That was the problem 🙂 Really challenge in fitting things in.

kiranshila22:08:14

So, I'm not convinced we are using the 8MB of flash that we have available on the WROVER

kiranshila22:08:54

But I'm still not 100% on how espruino is using the partition table

kiranshila22:08:36

factory hold the interpreter, our code goes into js_code, but what are the other partitions for

kiranshila22:08:01

ota doesn't even work on the 32 with espruino right now, so I think we can just get rid of that

mfikes22:08:13

Yeah, OTA is probably not a critical feature to have for messing around with this stuff.

mfikes22:08:31

Another thing that is annoying is that we only seem to be able to access half the RAM.

kiranshila22:08:32

But like, we can bump the js_code space to like 4M

mfikes22:08:47

We can only access 4 MiB of the 8 MiB of PSIRAM available.

kiranshila22:08:05

because of something espruino is doing?

mfikes22:08:13

I think that's a fundamental limitation of Espressif's stuff

mfikes22:08:26

(There's a post somewhere in one of their forums about it.)

mfikes22:08:20

This board only adds 4 MiB FWIW, maybe because of the same reason: https://www.tindie.com/products/seonr/tinypico/

kiranshila23:08:01

Yeah worked fine for me

kiranshila23:08:10

With the big boi partition table

mfikes23:08:44

Wow. Nice!

kiranshila23:08:10

Haven't tried to upload cljs yet, but that partition table seems to work

kiranshila23:08:34

Their build process is very confusing, and they are using a pretty old version of the esp-idf

mfikes23:08:00

You are on a Linux box, it appears...

mfikes23:08:30

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.

kiranshila23:08:44

Oh I can imagine

mfikes23:08:00

This stuff is hard enough as it is. Best to stay on the narrow path. 🙂