Activity for BDM tools
-
Pavel Pisa committed [45af53] on Code
bdm/m683xx/bdm-load: update code to build with some broader range of libbfd versions.
-
bdm/m683xx/bdm-driver: allow to build driver with new parport device model
-
bdm/m683xx/bdm-driver: update Makefile and kernel compatibility workarounds for 6.4+ kernels.
-
bdm/m683xx/bdm-load: liberty library is no longer required to build.
-
dm/m683xx/bdm-driver: adapt for access_ok difference in 5.0+ Linux kernels.
-
bdm/m683xx/bdm-driver: remove build time to follow 4.19.52 kernel reproducible requiremenst.
-
BenJZee posted a comment on a wiki page
The package m68k-bdm-1.4-pre4.zip for 68360 CPU32+ (/dev/bdmcpu320) does not work. Driver file bdm-cpu32 has ommisions and failures: a) ..pd_init does not completely initialize the BDM structure, I added/copied parts of the ..icd_init b) the error reported in 2008 is still there in write_sysreg cmd = BDM_WSREG_CMD must be cmd |= BDM_WSREG_CMD On the gdbserver side the CPU32+ is not supported See file m68k-bdm-low.c CPU-type and CPU-family are the confusion variables I made a hardcoded solution to...
-
I have a mismatch between m68k-bdm-gdbserver and GDB. I am in contact with Chris Johns but may be there are other experiences that can contribute to solve. My target hardware is M68360 CPU32+ Motorola (not Coldfire). I refer to /dev/bdmcpu320. I am using GNU gbd version 7.7 ("--host=i686-linux-gnu --target=m68k-rtems4.11") and gdbserver from m68k-bdm-1.4-pre4.tar.gz I copy Chris' words: "...there is a problem between GDB and the GDB server (m68k-bdm-gdbserver). The server is seeing a Coldfire and...
-
Pavel Pisa committed [6ca03f]
bdm/m683xx/bdm-driver: update rules for actual udev and distributions defaults.
-
Pavel Pisa committed [017c51]
bdm/m683xx/bdm-driver: archive udev rules for CPU32 driver variant.
-
bdm/m683xx/bdm-driver: ancient m683xx driver up...
-
BDM tools released /OldFiles/m68k-bdm-1.0.0.tar.gz
-
-
-
-
-
-
-
-
-
-
-
