Novation ReMote 25SL, M-Audio Trigger Finger

#33

OK, here it is.
...back to the beginning in terms of how it responds to the 25L

...as you'll see if you scroll all the way down.
I've included some of the compilation log, as otherwise I'm not sure there's any proof I didn't
go back to the regular firmware.

The 25L does seem to take about a second to boot up.

The final message I got wasn't anything that wasn't in the loop that was going round, iirc.
I don't remember which command it ended on.
...but then I was having to disconnect the Ax to stop the Patcher from crashing.
If needed I can go back to that firmware and try again.

Saving preferences...
preferences path : C:\Users\Andy\Documents\axoloti\axoloti.prefs
USB device found
not accesseable : -12
USB device found
connected
Authentic Axoloti Core
Firmware version: 1.0.0.1, crc=0x59DD416C, entrypoint=0x20011000
Firmware CRC mismatch! Please flash the firmware first! Hardware firmware CRC = 59DD416C <> Software CRC = Please compile the firmware first
Start compiling firmware
"setup build dir"
"Compiling firmware..."
BDIR = C:\Users\Andy\DOCUME~1\axoloti/build
FIRMWARE = .
rm -f C:\Users\Andy\DOCUME~1\axoloti/build/xpatch.o C:\Users\Andy\DOCUME~1\axoloti/build/xpatch.elf C:\Users\Andy\DOCUME~1\axoloti/build/xpatch.bin C:\Users\Andy\DOCUME~1\axoloti/build/xpatch.d C:\Users\Andy\DOCUME~1\axoloti/build/xpatch.map C:\Users\Andy\DOCUME~1\axoloti/build/xpatch.lst C:\Users\Andy\DOCUME~1\axoloti/build/xpatch.h.gch
The system cannot find the path specified.
ECHO is off.
arm-none-eabi-gcc -c -mcpu=cortex-m4 -O2 -ggdb -fomit-frame-pointer -falign-functions=16 -mfloat-abi=hard -mfpu=fpv4-sp-d16 -fsingle-precision-constant -Wall -Wextra -Wstrict-prototypes -Wa,-alms=build/lst/crt0.lst -DCORTEX_USE_FPU=TRUE -DARM_MATH_CM4 -D__FPU_PRESENT -DTHUMB_PRESENT -mno-thumb-interwork -DTHUMB_NO_INTERWORKING -MD -MP -MF .dep/crt0.o.d -mthumb -DTHUMB -I. -IC:\PROGRA~2\Axoloti\app/CMSIS//Include -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/common/ARMCMx/CMSIS/include -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/common/ARMCMx -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx/STM32F4xx -IC:\PROGRA~2\Axoloti\app/chibios/os/kernel/include -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/include -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32F4xx -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/GPIOv2 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/I2Cv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/OTGv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/RTCv2 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/SPIv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/TIMv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/USARTv1 -I. -IC:\PROGRA~2\Axoloti\app/chibios/ext/fatfs/src -IC:\PROGRA~2\Axoloti\app/chibios/os/various -I./STM32_USB_Host_Library/Core/Inc -I./STM32_USB_Host_Library/Class/HID/Inc -I./STM32F4xx_HAL_Driver/Inc C:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx/crt0.c -o build/obj/crt0.o
ECHO is off.
arm-none-eabi-gcc -c -mcpu=cortex-m4 -O2 -ggdb -fomit-frame-pointer -falign-functions=16 -mfloat-abi=hard -mfpu=fpv4-sp-d16 -fsingle-precision-constant -Wall -Wextra -Wstrict-prototypes -Wa,-alms=build/lst/vectors.lst -DCORTEX_USE_FPU=TRUE -DARM_MATH_CM4 -D__FPU_PRESENT -DTHUMB_PRESENT -mno-thumb-interwork -DTHUMB_NO_INTERWORKING -MD -MP -MF .dep/vectors.o.d -mthumb -DTHUMB -I. -IC:\PROGRA~2\Axoloti\app/CMSIS//Include -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/common/ARMCMx/CMSIS/include -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/common/ARMCMx -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx/STM32F4xx -IC:\PROGRA~2\Axoloti\app/chibios/os/kernel/include -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/include -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32F4xx -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/GPIOv2 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/I2Cv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/OTGv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/RTCv2 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/SPIv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/TIMv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/USARTv1 -I. -IC:\PROGRA~2\Axoloti\app/chibios/ext/fatfs/src -IC:\PROGRA~2\Axoloti\app/chibios/os/various -I./STM32_USB_Host_Library/Core/Inc -I./STM32_USB_Host_Library/Class/HID/Inc -I./STM32F4xx_HAL_Driver/Inc C:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx/STM32F4xx/vectors.c -o build/obj/vectors.o
ECHO is off.
arm-none-eabi-gcc -c -mcpu=cortex-m4 -O2 -ggdb -fomit-frame-pointer -falign-functions=16 -mfloat-abi=hard -mfpu=fpv4-sp-d16 -fsingle-precision-constant -Wall -Wextra -Wstrict-prototypes -Wa,-alms=build/lst/chcore.lst -DCORTEX_USE_FPU=TRUE -DARM_MATH_CM4 -D__FPU_PRESENT -DTHUMB_PRESENT -mno-thumb-interwork -DTHUMB_NO_INTERWORKING -MD -MP -MF .dep/chcore.o.d -mthumb -DTHUMB -I. -IC:\PROGRA~2\Axoloti\app/CMSIS//Include -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/common/ARMCMx/CMSIS/include -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/common/ARMCMx -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx/STM32F4xx -IC:\PROGRA~2\Axoloti\app/chibios/os/kernel/include -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/include -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32F4xx -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/GPIOv2 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/I2Cv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/OTGv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/RTCv2 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/SPIv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/TIMv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/USARTv1 -I. -IC:\PROGRA~2\Axoloti\app/chibios/ext/fatfs/src -IC:\PROGRA~2\Axoloti\app/chibios/os/various -I./STM32_USB_Host_Library/Core/Inc -I./STM32_USB_Host_Library/Class/HID/Inc -I./STM32F4xx_HAL_Driver/Inc C:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx/chcore.c -o build/obj/chcore.o
ECHO is off.
arm-none-eabi-gcc -c -mcpu=cortex-m4 -O2 -ggdb -fomit-frame-pointer -falign-functions=16 -mfloat-abi=hard -mfpu=fpv4-sp-d16 -fsingle-precision-constant -Wall -Wextra -Wstrict-prototypes -Wa,-alms=build/lst/chcore_v7m.lst -DCORTEX_USE_FPU=TRUE -DARM_MATH_CM4 -D__FPU_PRESENT -DTHUMB_PRESENT -mno-thumb-interwork -DTHUMB_NO_INTERWORKING -MD -MP -MF .dep/chcore_v7m.o.d -mthumb -DTHUMB -I. -IC:\PROGRA~2\Axoloti\app/CMSIS//Include -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/common/ARMCMx/CMSIS/include -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/common/ARMCMx -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx/STM32F4xx -IC:\PROGRA~2\Axoloti\app/chibios/os/kernel/include -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/include -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32F4xx -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/GPIOv2 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/I2Cv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/OTGv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/RTCv2 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/SPIv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/TIMv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/USARTv1 -I. -IC:\PROGRA~2\Axoloti\app/chibios/ext/fatfs/src -IC:\PROGRA~2\Axoloti\app/chibios/os/various -I./STM32_USB_Host_Library/Core/Inc -I./STM32_USB_Host_Library/Class/HID/Inc -I./STM32F4xx_HAL_Driver/Inc C:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx/chcore_v7m.c -o build/obj/chcore_v7m.o
ECHO is off.
arm-none-eabi-gcc -c -mcpu=cortex-m4 -O2 -ggdb -fomit-frame-pointer -falign-functions=16 -mfloat-abi=hard -mfpu=fpv4-sp-d16 -fsingle-precision-constant -Wall -Wextra -Wstrict-prototypes -Wa,-alms=build/lst/nvic.lst -DCORTEX_USE_FPU=TRUE -DARM_MATH_CM4 -D__FPU_PRESENT -DTHUMB_PRESENT -mno-thumb-interwork -DTHUMB_NO_INTERWORKING -MD -MP -MF .dep/nvic.o.d -mthumb -DTHUMB -I. -IC:\PROGRA~2\Axoloti\app/CMSIS//Include -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/common/ARMCMx/CMSIS/include -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/common/ARMCMx -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx/STM32F4xx -IC:\PROGRA~2\Axoloti\app/chibios/os/kernel/include -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/include -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32F4xx -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/GPIOv2 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/I2Cv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/OTGv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/RTCv2 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/SPIv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/TIMv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/USARTv1 -I. -IC:\PROGRA~2\Axoloti\app/chibios/ext/fatfs/src -IC:\PROGRA~2\Axoloti\app/chibios/os/various -I./STM32_USB_Host_Library/Core/Inc -I./STM32_USB_Host_Library/Class/HID/Inc -I./STM32F4xx_HAL_Driver/Inc C:\PROGRA~2\Axoloti\app/chibios/os/ports/common/ARMCMx/nvic.c -o build/obj/nvic.o
ECHO is off.
arm-none-eabi-gcc -c -mcpu=cortex-m4 -O2 -ggdb -fomit-frame-pointer -falign-functions=16 -mfloat-abi=hard -mfpu=fpv4-sp-d16 -fsingle-precision-constant -Wall -Wextra -Wstrict-prototypes -Wa,-alms=build/lst/chsys.lst -DCORTEX_USE_FPU=TRUE -DARM_MATH_CM4 -D__FPU_PRESENT -DTHUMB_PRESENT -mno-thumb-interwork -DTHUMB_NO_INTERWORKING -MD -MP -MF .dep/chsys.o.d -mthumb -DTHUMB -I. -IC:\PROGRA~2\Axoloti\app/CMSIS//Include -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/common/ARMCMx/CMSIS/include -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/common/ARMCMx -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx -IC:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx/STM32F4xx -IC:\PROGRA~2\Axoloti\app/chibios/os/kernel/include -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/include -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32F4xx -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/GPIOv2 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/I2Cv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/OTGv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/RTCv2 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/SPIv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/TIMv1 -IC:\PROGRA~2\Axoloti\app/chibios/os/hal/platforms/STM32/USARTv1 -I. -IC:\PROGRA~2\Axoloti\app/chibios/ext/fatfs/src -IC:\PROGRA~2\Axoloti\app/chibios/os/various -I./STM32_USB_Host_Library/Core/Inc -I./STM32_USB_Host_Library/Class/HID/Inc -I./STM32F4xx_HAL_Driver/Inc C:\PROGRA~2\Axoloti\app/chibios/os/kernel/src/chsys.c -o build/obj/chsys.o
ECHO is off.

EDITED OUT LARGE AMOUNT OF COMPILATION LOG (too much for the webpage to allow)

main.c:172:33: warning: unused parameter 'usbp' [-Wunused-parameter]
static void usbEvent(USBDriver* usbp, usbevent_t event)
^
ECHO is off.
arm-none-eabi-gcc mounter_build/obj/crt0.o mounter_build/obj/vectors.o mounter_build/obj/chcore.o mounter_build/obj/chcore_v7m.o mounter_build/obj/nvic.o mounter_build/obj/chsys.o mounter_build/obj/chdebug.o mounter_build/obj/chlists.o mounter_build/obj/chvt.o mounter_build/obj/chschd.o mounter_build/obj/chthreads.o mounter_build/obj/chdynamic.o mounter_build/obj/chregistry.o mounter_build/obj/chsem.o mounter_build/obj/chmtx.o mounter_build/obj/chcond.o mounter_build/obj/chevents.o mounter_build/obj/chmsg.o mounter_build/obj/chmboxes.o mounter_build/obj/chqueues.o mounter_build/obj/chmemcore.o mounter_build/obj/chheap.o mounter_build/obj/chmempools.o mounter_build/obj/hal.o mounter_build/obj/adc.o mounter_build/obj/can.o mounter_build/obj/ext.o mounter_build/obj/gpt.o mounter_build/obj/i2c.o mounter_build/obj/icu.o mounter_build/obj/mac.o mounter_build/obj/mmc_spi.o mounter_build/obj/mmcsd.o mounter_build/obj/pal.o mounter_build/obj/pwm.o mounter_build/obj/rtc.o mounter_build/obj/sdc.o mounter_build/obj/serial.o mounter_build/obj/serial_usb.o mounter_build/obj/spi.o mounter_build/obj/tm.o mounter_build/obj/uart.o mounter_build/obj/usb.o mounter_build/obj/stm32_dma.o mounter_build/obj/hal_lld.o mounter_build/obj/adc_lld.o mounter_build/obj/ext_lld_isr.o mounter_build/obj/can_lld.o mounter_build/obj/ext_lld.o mounter_build/obj/mac_lld.o mounter_build/obj/sdc_lld.o mounter_build/obj/pal_lld.o mounter_build/obj/i2c_lld.o mounter_build/obj/usb_lld.o mounter_build/obj/rtc_lld.o mounter_build/obj/spi_lld.o mounter_build/obj/gpt_lld.o mounter_build/obj/icu_lld.o mounter_build/obj/pwm_lld.o mounter_build/obj/serial_lld.o mounter_build/obj/uart_lld.o mounter_build/obj/board.o mounter_build/obj/shell.o mounter_build/obj/chprintf.o mounter_build/obj/memstreams.o mounter_build/obj/glcdfont.o mounter_build/obj/axoloti_control.o mounter_build/obj/axoloti_board.o mounter_build/obj/watchdog.o mounter_build/obj/usb_msd.o mounter_build/obj/main.o -mcpu=cortex-m4 -O2 -ggdb -fomit-frame-pointer -falign-functions=16 -ffunction-sections -fdata-sections -fno-common -mfloat-abi=hard -mfpu=fpv4-sp-d16 -fsingle-precision-constant -nostartfiles -L. -Wl,-Map=mounter_build/mounter.map,--cref,--no-warn-mismatch,--library-path=C:\PROGRA~2\Axoloti\app/chibios/os/ports/GCC/ARMCMx,--script=STM32F407xG.ld,--gc-sections -mno-thumb-interwork -mthumb -o mounter_build/mounter.elf
arm-none-eabi-objcopy -O ihex mounter_build/mounter.elf mounter_build/mounter.hex
arm-none-eabi-objcopy -O binary mounter_build/mounter.elf mounter_build/mounter.bin
arm-none-eabi-objdump -x --syms mounter_build/mounter.elf > mounter_build/mounter.dmp
Link to firmware CRC 0C017969
Done compiling firmware
Link to firmware CRC 0C017969
Start uploading firmware
firmware file path: C:\Users\Andy\Documents\axoloti\miditestfw2\firmware\build\axoloti.bin
firmware file size: 591,660
firmware crc: 0xC017969
block uploaded @ 0xC0000000 length 16
block uploaded @ 0xC0000010 length 32768
block uploaded @ 0xC0008010 length 32768
block uploaded @ 0xC0010010 length 32768
block uploaded @ 0xC0018010 length 32768
block uploaded @ 0xC0020010 length 32768
block uploaded @ 0xC0028010 length 32768
block uploaded @ 0xC0030010 length 32768
block uploaded @ 0xC0038010 length 32768
block uploaded @ 0xC0040010 length 32768
block uploaded @ 0xC0048010 length 32768
block uploaded @ 0xC0050010 length 32768
block uploaded @ 0xC0058010 length 32768
block uploaded @ 0xC0060010 length 32768
block uploaded @ 0xC0068010 length 32768
block uploaded @ 0xC0070010 length 32768
block uploaded @ 0xC0078010 length 32768
block uploaded @ 0xC0080010 length 32768
block uploaded @ 0xC0088010 length 32768
block uploaded @ 0xC0090010 length 1836
Done uploading firmware
Start uploading patch
bin path: C:\Users\Andy\Documents\axoloti\miditestfw2\firmware\flasher\flasher_build\flasher.bin
block uploaded @ 0x20011000 length 15188
Done uploading patch
Start flashing...
Firmware flashing in progress, do not unplug the board until the leds stop blinking! You can connect again after the leds stop blinking.
Disconnect request
flashing...
USB device found
connected
Authentic Axoloti Core
Firmware version: 1.0.0.1, crc=0x0C017969, entrypoint=0x20011000
Axoloti says: USB Device Attached

#34

ok, can you double check... the initial part of the logging has not changed,
so I can't understand how you would get logging last time, but not this time....

basically, like last time, I print a message out, immediately after the USB device attaches message, and then the axoloti waits for 500mS before doing anything else... so I cant see how it could crash, and display the
USB Device Attached, yet, not print the following message ... its kind of impossible, (or at a minimum extremely unlikely)

Ive double checked , I definitely uploaded the correct one
you did use the midi_dbg_only.zip , as I PM'd you ...!? (not the more general one on the other thread)

one thing, can you make sure you do NOT have the 25SL plugged in when you initially reboot the axoloti after the firmware upgrade, always attach it once the axoloti has successfully booted..

#35

ok, I got the wrong firmware, sorry. "same place".... ambiguous, but if I'd thought about it I'd have got the right one.
Will report again.

#36

Here's log with correct firmware:-

USB device found
connected
Authentic Axoloti Core
Firmware version: 1.0.0.1, crc=0x0B216928, entrypoint=0x20011000
Axoloti says: USB Device Attached
Axoloti says: TB : testing only : extended debug
Axoloti says: TB : HDA after (extended) delay
Axoloti says: TB : HDA speed 1
Axoloti says: TB : HDA pipes alloced
Axoloti says: TB : HDA pipe 1 0
Axoloti says: TB : HDA pipe 2 0
Axoloti says: TB HENUM enter
Axoloti says: TB HENUM state 0
Axoloti says: TB HE IDLE
Axoloti says: TB HE IDL -NR
Axoloti says: TB HENUM not ready yet, will retry
Axoloti says: TB HENUM enter
Axoloti says: TB HENUM state 0
Axoloti says: TB HE IDLE
Axoloti says: TB HE IDL -NR
Axoloti says: TB HENUM not ready yet, will retry
Axoloti says: TB HENUM enter
Axoloti says: TB HENUM state 0
Axoloti says: TB HE IDLE

then just loops , even after 25L is unplugged...keeps looping.

I had to disconnect from Patcher to stop it...which went like this:-

Axoloti says: TB HE IDL -NR
Axoloti says: TB HENUM not ready yet, will retry
Axoloti says: TB HENUM enter
Axoloti says: TB HENUM state 0
Axoloti says: TB HE IDLE
Disconnect request

after that, reconnecting just brings back the looped messages on the Patcher.

With the trigger finger we get to "Axoloti says: TB HENUM not ready yet, will retry" as expected.

#37

Ok, so this shows us axoloti is actually not crashing...
whats happening is it going into a continuous loop, trying to setup communicate with the 25sl.

basically, what I believe is happening, is your 25SL is not responding to the descriptor requests...
its the very first descriptor request that is sent, in which the protocol is established...
and its just not getting data back.
this is 'odd' as we can see the pipes are opened correctly ( HDA pipe 1 0, HDA pipe 2 0 = USBH_OK for both pipes)

as far as i can tell, and its get pretty low level, the usb ctrlreq does have retrying logic, so its also repeatedly making the request, and getting nothing back.

the issue is, I dont think theres much further I can go...
it would be a nightmare trying to debug the USB state machines remotely (or even locally :wink:) and even if I did, all we would likely find, is the message is sent but we just dont get the URB_DONE response. but that wouldn't tell us why!

Its probably worth pointing out, that control requests, and the whole setup phase we are dealing with here, is the same for every USB device... its not like interfaces/endpoints which vary, this part of the process is identical for every device... so its very odd that the 25SL is failing here... at this point, it should be the same as every other device.

so, I think its something physical/electrical... something that is different from when you having it working with a PC.

are you running this using an external power supply? ( I should have asked this earlier :frowning: )
I notice the 25SL has an (optional) power supply, that is 600mA... now its probably overrated, but that would be too much current to draw from the axoloti directly via the usb host port.... but even so, it could be its trying to draw too much current or something similar. ... perhaps the 25SL is not initialising itself due to lack of power?

... so definitely if your not running it on external power, that is the next thing to try.

#38

OK.
I think I put forward that idea earlier, but my quick test didn't reproduce the problem.
I wasn't sure that the usb function of the 25L would work at all when switched to the psu.
...but yes it works.
External psu attached.
...and we have success!

many thanks for persisting.

If you'd like to try out a way to prevent the lock up of the usb port in this case I'm happy to do further tests for you.

#39

Are you getting the Remote 25 SL to work on the USB host port with an external PSU on the 25 SL? I can't get mine to work at all, except over MIDI...

#40

Yes, Remote 25 SL works fine.
...but you need to push the power switch over to the DC position, and attach the external psu first
...only then can you connect to the Ax

( if you try to run the 25L on power from the Ax you'll render the Ax unable to detect any usb device, it'll need a re-boot)

#41

Aha, that power/connection sequence works. Thank you! :slight_smile:

I found that it also works when the SL is powered up and connected first, and then the axo is powered up.

These sequences might indicate that it's not the power source as such that's the issue (axo runs fine when powering the SL over its USB host port), but rather that the SL has to be initialized before the USB connection is made.

#42

I confirm this procedure works also on the Remote 25 LE.
Axoloti powered from USB, Remote 25 LE powered with 9 AA Batteries, switch set to DC power/Battery. The sequence is fundamental, otherwise it does not work.

#43

My Remote 25LE died accidentally (ehm water + big fall).

But fortunately ebay is great and I got a 12 years old Remote 25SL (mk1) for 40GBP. It works fantastically with the Axoloti following the procedure above. It is nice to have many parameters on the display. Great old controller indeed, probably one of the best for the Axoloti?

#44

I bought a used Novation Zero SL MK2 recently and came to this thread because it was showing the same symptoms.
Using an external PSU fixes the issue indeed, thanks!

#45

Hi, Just a question about Novation Zero Sl MK2. Does it possible to control the leds via Axoloti? I can do it with a Nanokontrol 2 and does it allow to use it as a sequencer, for example. I´m thinking in trying with a novation remote zero.
Also I wanted to ask u if you thinhk there is enough space inside this controller to put the axoloti board inside.

Thanks in advance!

#46

You can control the LEDs via midi when the Ableton preset is selected.

That is the simple avenue. Additionally, there is a sysex-way of controlling the Zero which is needed if you want to control text-display. When I tried that sysex mode, I noticed that I lose that "touch-sense" feature which updates the text-content after you touched a different group of controls.

I have not opened it up and I did not intend to, so I don't know whether the axoloti would fit. It's actually a neat idea, I think only that I would be too lazy to try myself.

#47

Thanks a lot! I will post my sequencer proyect soon on this forum, so you could see what I´m trying.

#48

Sysex programmer's guide PDF

This URL is from another forum. I think that document is also available somewhere on focusrite/novation's site.

It describes how to write your own "Automap" mode. It would require receiving and responding to sysex coming from the unit however, so some things cannot be achieved when using the Axoliti with the current firmware.
Still, being able to display custom text on the display seems potentially useful and it does work for me.

The third, hidden port is not visible to the Axoloti.

#49

Very curious to hear your progress on this as I have both a Remote SL 61 and a Remote SL zero and would love to be able to control at least the Leds/buttons or at most update the screen with the axoloti. have just downloaded your sysex objects and will have a look, is your help patch just designed to put the remote sl into Ableton automap mode?

#50

Unfortunately no progress was made due to work and focus.
I do plan to change the code drastically, it only reflects my state of exploration then.
I do not remember clearly, if I left code specific to the Zero SL in the help patch then it might be a mistake.
You don't need any sysex for controlling the Button LED's when using the Ableton mode.

#51

I'll have to have a look at how to do that. Thanks for letting me know it's possible.

Is it by use of CC then, and can the screen be updated that way too, anything at all would be great

#52