Hippy, how did you get this lovely output?
How useful is that project? I mean how much is implemented looking at tcl source there are so many files this project in comparison looks bare bones. I switch from using tiny script to Lua because I wanted more features. But Lua can be like hunting mosquitoes with a bazooka when you just need a little bit more from your scripting language.Code:
Program Name : tclTarget Device : RP2350Target Chip : Cortex-M33Target ISA : ARMv8-MTarget Code : RP2350 ARM-S - Secure ARM ImageTarget Board : Pico 2Code Execution Type : Load and run from RAMBuild Date : Nov 22 2024Pico SDK Version : 2.0.0Build Attributes : ReleaseProgram Area Used : 20000000 to 2000B6FF 45 KB 46,848 bytesERRATA-E10 FIX : 10FFFF00 to 10FFFFFF 256 bytesBinary Info Root Entry : 20000148 to 2000015B 5 quads 20 bytesMeta Block : 2000015C to 20000177 7 quads 28 bytesCopy Table Information : 200001D0 to 200001F7 10 quads 40 bytesUSB WinUsb Descriptor : 2000A9B4 to 2000AA59 166 bytesUSB Configuration Info : 2000AAE4 to 2000AB37 Configuration 1USB Device Descriptor : 2000AB38 to 2000AB49 2E8A:0009 [1.0] USB 2.1Binary Info Pointers : 2000ACF8 to 2000AD0F 6 quads 24 bytesBinary Info Tag Name : 'RP' - Raspberry Pi Pico SDKUSB Device Information : 2E8A:0009 [1.0] Raspberry Pi Pico SDK (RP2350)
The only issue I see with the compiled lua byte code is that sometimes it's larger than the source script. I have found that at least for me when it comes to the PT52 compiling on an RP2040 or the RP2350 the output will run on either CPU at least when using the ARM processors on the 2350. I haven't tried with the RISC cores.I think we had to add about 1500 bytes to stack requirements to support the Lua compiler. This isn't running on a Pico, so more RAM to start with. And we could fairly easily generate a stripped-down program which would run on the same hardware, purely to do the compilation.
Statistics: Posted by DarkElvenAngel — Sat Nov 23, 2024 2:19 am