Hi Tim, I don't know the root cause of the issue you are facing, but it could be some memory misalignment. Try to use GDB to investigate where the crash is happening.
Also test using other File Systems, if you use USB MSD with FAT then your host OS will show the content of the SPI Flash. BR, Alan On 12/21/21, Tim <t...@jti.uk.com.invalid> wrote: > Hi, > > Having some grief getting USB MSD device to work, following some notes from > Alan C. Assis from around 5 years ago. > > It is an MT25Q 32Mbyte spi nor flash device, registered as /dev/mtdblock0 > and also mounted and initialised as an nxfss file system at /mnt/flash. I > can read/write to it from nsh. > > If I run MSCONN, it crashes: > > nsh> msconn > mcsonn_main: Creating block drivers > find_blockdriver: pathname="/dev/mtdblock0" > ftl_geometry: Entry > ftl_geometry: available: true mediachanged: false writeenabled: true > ftl_geometry: nsectors: 131072 sectorsize: 256 > usbmsc_exportluns: Starting SCSI worker thread > arm_dataabort: Data abort. PC: 2002f528 DFAR: e8bd8800 DFSR: 00000005 > up_assert: Assertion failed at file:armv7-a/arm_dataabort.c line: 160 task: > msco > > It seems to be somewhere in task_init and group_setuptaskfiles (duplicating > files I think), but debugging deep inside NuttX is, um, scary! > > I'm hoping I've just not configured something else it needs; and I can't > seem to find any relevant debug options to assist - USB MSC MM DEBUG seems > to cause it all to hang up at a printf statement in the msconn app. > > Any thoughts, kind people? > > Thanks, Tim. > > >
